evasivesoftware

Hi Charles,

Have you tried updating to version 1.1.0?
Is this issue still occuring?

If so, can you please provide us a link to your website

We’re writing shortcode support for our next major release.

This type of ignore functionality will be included in the engine.

Definitely agree here.

It’s got to do with the JS libraries used to convert markdown to html, and then html back to markdown.

We’ve flagged this for fix in future releases.

Hi there,

We’re currently working on this functionality for next major release.

Thanks

Hey Benny,

Thanks for bringing this to our attention.

Yep please send a pull request through on GitHub and we’ll apply a patch.

https://github.com/evasivesoftware/PrettyPress

Thanks

This will be fixed for version 1.0.7

Hey Jay,

Thanks for the feedback – we’ve been tied down with regular work the last couple of weeks but should be able to fix some more bugs this coming week.

Hey Ed,

Great find, thanks for pointing this out!
We’ve added it to our fix list for next release.

Thanks again!

Depends on how that plugin is written, but I’d assume it would not.

Markdown is used by launching the PrettyPress composition screen, and pressing the “Markdown” tab.

PrettyPress uses marked.js (https://github.com/chjj/marked), and
to-markdown (https://github.com/domchristie/to-markdown) for markdown management / conversion.

Marking as resolved.

Hi Richard,

Thanks for the bug info – we’ll definitely take a look into it.

We’re planning to support custom fields in the next major release.

Hi UaMV,

Thanks for the kind words.

Yes we’ve scheduled further support for custom post types and hopefully custom fields for a later release, hopefully early next year after holiday celebrations.

Thanks again.

Hi Li-An,

We’ve just released 0.3 tonight.
Upgrade the plugin, and let us know how you go. The latest revision should be fixed of raw text / html bugs.

Thanks for your help and feedback!

Current version, only with WYSIWYG.

Next release (0.3) will support HTML view also.

Thanks.

We’ve found the issue: You need to load the post screen with the visual WYSIWYG editor and keep it active – we’ll fix this bug for next release.