Pierre-Henri Lavigne

Good day to you @aboutm2

Sorry for the late reply and thank you very much for trying the plugin, I greatly appreciate. ?? It’s always nice to get feedback from real testing. ?? I haven’t got the chance to give a try with BuddyPress, to be honnest I even don’t know the differences between BuddyPress and bbpress ??

I’m still currently busy fixing a few features, if you can wait a few more days, at least one week, and I’ll try to dig inside to check what would be possible ?? I’ll reply here again when I got updates

Thank you in advance for your understanding, best regards

Peter

@ugotta Awesome, I guess I finally got it ?? Thank you very much for your explanations, that helps a lot.

Indeed, for your specific case, the option I added might give you worse results than before.
Currently, mixing options as you described produces the opposite effect… ??

And I guess I should stop using the words backend and frontend on my side as well as it is confusing. I was talking about the WYSIWYG on the WordPress edit screen. I almost never work on the frontend in short ??

With Markup Markdown (v3.7.5 released earlier this morning – or the 3.7.3) please enable all the headlines (From H1 to H6) and don’t check the “preserve space option”. That should set you back to the default markdown behavior. Then if you escape the # character with a backslash \ that should preserve the format and avoid triggering markdown’s headline feature. Something like this :

\# level 1
_\# level 2
__\# level 3
\# last level 1

I don’t know at the time of writing if this will trigger the order numbering with o2 as I never used it before. I’m gonna give it a try when I can, that won’t be until next week-end… Please give me a few days. Maybe we just need a few filters on the backend or the frontend to plug the plugins together. ??

About the last part I did a few tuning in the past to make the plugin compatible with acf_form (Advanced Custom Fields) that runs on the frontend. Last time I check with Frontend Admin by DynamicApps, it was working with custom fields only. There was a bug when MarkupMarkdown was enabled with the native form and post content as every field is kind of wrap in its own overlay (different name, etc…). Can’t promise at all if that will be fixable.

Keep in touch

• This reply was modified 5 months, 3 weeks ago by Pierre-Henri Lavigne. Reason: Typo
• This reply was modified 5 months, 3 weeks ago by Pierre-Henri Lavigne.

@ugotta Thank you for getting back to me and taking the time to test each release. I appreciate.

Indeed valuable feedback provided:

The 3.6 was actually a patch to the backend PHP parser. That would apply the fix to existing data as well as new ones.

The 3.7 is actually a patch to the frontend WYSIWYG editor. That would only apply the fix to newly created data.

In that case would it be possible for you to give it a try with the latest version 3.7.3 when you can please ?
I added a tiny patch with an option to “preserve spaces at the beginning of the line”.
That could solve your issue with the last case:
_#This should not be a heading

For sure I can’t cover every existing editor, if that can potentially help other devs with a more “exotic setup”, why not giving a try. The option is disabled by default so existing users won’t be disturbed anyway ??

Kind regards,

Peter

• This reply was modified 6 months ago by Pierre-Henri Lavigne. Reason: Typo

Greetings @ugotta

And thank you for your patience. Well I can’t guarantee you 100% for sure that I can block the headings, but at least through the WYSIWYG I did my best to prevent authors to use specific heading levels through pasting, shortcuts, buttons or similar keyboard inputs.

After upgrading to 3.7.0, you will find new options at the top of the settings page :
/wp-admin/options-general.php?page=markup-markdown-admin

Feel free to give it a try when you can and tell me if that could work for you

Best Regards,

No problems @ugotta ??
I can’t promise you I’m gonna be that fast every time, it was a good timing.

Unfortunately there is no way to block a specific level title at the moment… ??
As I got the same issue as well I’m gonna look in to it as soon as I can.

Keep you in touch, thank you for your patience ???♂?

• This reply was modified 6 months, 2 weeks ago by Pierre-Henri Lavigne. Reason: Typo

No problems at all, thank you @ugotta for the explanations, I got it.

I setup the Parsedown PHP Library stable 1.7.4 for now, there is no such feature.
The current beta 1.8 has implemented a strict mode that matchs your needs.
A quick patch on my local… And it’s working great.

If you can wait a few more days, I’m gonna add it to the next release. ??

• This reply was modified 6 months, 3 weeks ago by Pierre-Henri Lavigne.

@asfarfordev I haven’t heard from you for a while, so I’m gonna mark this topic as solved.
Feel free to open a new one if need be. Thank you for your understanding.

Thank you for your message @ugotta

My apologizes as it’s not clearly written at the moment in the documentation, the extended syntax of markdown is currently used with the PHP library. There is no automatic ids generation with the headlines.

Depending on your needs, it can be achieved manually by following the syntax as explained here :
https://www.markdownguide.org/extended-syntax/#heading-ids

Typically :
[Link to Heading one](#myid)
...
# Headine one {#myid}

Hope this helps.

Hi @asfarfordev,

Sorry for the late reply I’ve been busy. I released 3.5.0 a few days ago that should bring to you the missing RTL feature. Please upgrade if you can and give a new try ?? If the edit screen is setup as right to left, then the RTL mode is automatically activated with the markdown editor. In case you need to reverse, from the settings screen (Settings -> Markup Markdown) you can add a LTR or RTL button to your toolbar for your writers to be able to toggle manually the direction.

About your custom post type issue, I couldn’t reproduce the bug on my side.
I published a quick tutorial here :
https://www.markup-markdown.com/wordpress-tutorials/setting-custom-post-type/
In short the markdown editor is only activated with public post types. In case your CPT are private, you can easily force to trigger the activation with the plugin CPT UI by adding markup_markdown value in the Custom "Supports" field as described on the following screenshot:

If you are a more experienced developer, of course another solution would be to use a snippet with a different priority in your child’s theme or plugin like this one :

add_action('init', function() {
  add_post_type_support('your_cpt_slug', 'markup_markdown');
}, 11);

Hope this helps. Kind regards,

• This reply was modified 9 months, 3 weeks ago by Pierre-Henri Lavigne. Reason: Typo

Thank you for your feedbacks @asfarfordev, I’m already working on improving support for multi-site. ???♂?

About your custom post type, could you tell me how you created them please ? By default only public available post types are automatically converted to markdown, from what I understand there might be an issue with hook priorities if post types are created via plugins.

For the right to left language direction, it looks possible I’m making an upgrade. If you can wait a few more days I’ll do my best to publish a new release next week. ??

Thank you for your patience

• This reply was modified 10 months ago by Pierre-Henri Lavigne. Reason: Typo

@mbouclas I haven’t heard of you for a while, so I suppose it’s working as expected. I’m gonna mark this task as solved ?? Feel free to write a new topic if need be.

@mastababa ok indeed the buttom from the toolbar had a “table” classname. ?? I’ve just released version 3.4.2, including the “mmd” namespace for the buttons classname that should avoid such issues in the future.

Kinds Regards

@mbouclas I released version 3.4.1 that should bring the missing parts for the REST API to output description’s field as plain HTML ?? Test on my local with a custom post type and custom tags / cats plus a dummy woocommerce product. ??

@mastababa How do you do ? Good news I’ve just released version 3.4.0 that should solve your issues ?? I hope so ??

In case it wouldn’t work, could you share with me more information please ?
Backend, frontend, version, theme if possible, etc… any information that could help me reproduce your issue on my local.

I appreciate your time and your patience ??

• This reply was modified 10 months, 3 weeks ago by Pierre-Henri Lavigne. Reason: Typo

@mbouclas Can’t promise when I can do it, the description filters do not seem to work with the REST API. Post content, page content, custom post type content are OK on my local but category / tag description filters do not seem to be applied wit the Rest API by default… Gonna have to take a look.
Please allow me a few day to investigate ???♂?