Pierre-Henri Lavigne

Good day to you @normdist,

First thank you for your kind words. That’s awesome when a user can fully appreciate the product. ??

I released a new version 3.14.2 earlier this morning and wrote a quick post here :
https://www.markup-markdown.com/wordpress-tutorials/working-with-code-fences-blocks/
You should find the information you are looking for ??

I added the urls to the “AutoPlugs” as expected as well. My bad, the setup was almost done actually, only made a few tweaks to output the correct HTML links on the backend ??. Hope this is more usable now.

Please note that this isn’t a recommend list at all, but a list of bridges / compatibility layers / proxies – I don’t know how to call them – added for plugins that can’t be used straighforward with the markup markdown plugin. I haven’t tested and can’t test every plugin one by one, just an organic growth depending from the user requests.

Feel free to test on your own and tell me if it’s working for you. Best regards,

• This reply was modified 5 days, 17 hours ago by Pierre-Henri Lavigne. Reason: typo
• This reply was modified 5 days, 17 hours ago by Pierre-Henri Lavigne.

Hello @mightyx3n,

Could you please give a try with the latest release 3.14.2 – or the one from last week 3.14.1. Markdown used in excerpts or contents inside a “Loop block” should be rendered on the frontend. The preview does not work on the edit screen for now.

Please note that it’s not 100% accurate. Outside of the markdown editor, more filters / hooks are triggered and I can’t guarantee the rendering. And for example, it can be tricky, especially with excerpts. If you don’t specify properly an excerpt (automatic text generated from content, use of headlines, etc…), the rendering may be altered. I can’t do much about it on my side.

Hope this could work for you. Kind Regards

@mightyx3n ,

To confirm are you talking about the block from the Gutenberg editor called “Query Loop” or something like that ? The type of block to display a list of post ?

Indeed after a quick test, filters are not triggered by default. Please allow me a few days, I’m gonna look at that as soon as I can.

Thank you for your patience

Hello @saonian ,

And thank you for sharing your issue. I don’t use much the footnotes, it’s working like that :
https://www.markdownguide.org/extended-syntax/#footnotes

I tried to test on my side but I couldn’t reproduce your issue. The numbering is automatic.
For example :

Test note alpha [^alpha] is not beta [^beta]
....
[^alpha]: lorem
[^beta]: Lipsum

And will render something like :
https://mega.nz/file/EkUjDZLR#aMUH1y4r1cmBspOzb8WCC9DbWF4kQsqaW6HCNzoqAEk

Could you give a try please with letters or number with letters to check if it can be used as a workaround ?

Kind Regards

• This reply was modified 1 week, 5 days ago by Pierre-Henri Lavigne.

Hey @mightyx3n , the latest version 3.14.0 should fix your issue. Please give it a try.

I’m gonna mark the discussion as closed for now, feel free to reopen it if need be.

Greetings

• This reply was modified 1 week, 5 days ago by Pierre-Henri Lavigne.

Greetings @ugotta and sorry for the late reply,

I tried various setup with the latest Markup Markdown + O2 but I couldn’ reproduce the error.

Here is an exemple :
– https://mega.nz/file/kgVnHZ4L#eS_7e8A-4salZ46j2sw_lfcKm_bEa-BFgC73ZFOselk
– https://mega.nz/file/E59DCZjB#lMLH__lAWziZ2VI51JE0QVfy-5V2GeKPkQPjcxQuqz0

Setup :
– https://mega.nz/file/IgUS2KxI#9yBFKyV6jjZe_4gL9P7MproEgH_RZNISJabTN7M5XNI
– https://mega.nz/file/l5N3XQaC#lD6P7wyO-X8gjdXlCt-maYah_I98jkcZGATkZhmINR4

Can you guide me on how to reproduce your issue please ?
Is this from a specific screen like a post or comment ?

Any detail appreciate

Thank you so much @w3techie for this wonderful review !

Happy and glad you like it ??
I wish you a wonderful adventure in the markdown land ??

@mightyx3n Indeed that’s a bug ??

I’m gonna need a few days to investigate and fix it. Meanwhile if your are not using the feature, you could try disabling it from the screen options inside the settings screen :
https://mega.nz/file/wwNS1bZB#s_V-mbscczRwZPrQIMwSBe2PJDOY8Plg6t5EOULMHxI

Kind regards,

@ugotta Wow great job mate ! ! !

It’s really helpful to me, I’m gonna check before the next update if I can fix it. Probably something to do with my regular expressions actually…?? I greatly appreciate the feedback and congratulations to you for patching it on your side. ??I know it is sometimes slow and unpleasant, that’s open source as free in beer ??????

Good job, and thank you in advance for your patience, I will keep you posted ??

@mightyx3n Indeed it was broken??

I guess I got it, classic theme / editor was active during my test on my localhost. It looks like the “description” field from the Code Snipet add / edit screen requires Gutenberg or is using a few hooks I disabled by default.

I released version 3.13.0 earlier today. If you go to the settings page :

/wp-admin/options-general.php?page=markup-markdown-admin

You should be able to activate what I call an “Autoplug” as described in the following screenshot :
https://mega.nz/file/E0ExFS6K#1aQ5IpkmWvT_LGKF8gKYgnFhocETWrPFzWj0iTmxQ24

If you don’t see the label “CodeSnippets” in the list, just press once the blue button “Update” to resave and fresh the list. Check the box and save again your preferences, Code Snippets should work now.

I’m gonna mark this issue as resolved, please have a wonderful markdown day.

• This reply was modified 1 month, 2 weeks ago by Pierre-Henri Lavigne.

@mightyx3n Could you please elaborate a little more, and give me more information please ?

I only made a quick test with Code Snippets 3.6.7, Markup Markdown 3.12.0 by inserting one of the default snippet (the current date) inside the body of a post and a custom post, and everything worked as expected. The current year was shown.

I haven’t heard from you for a while @heavylogic so I’m gonna mark this ticket as solved.
Feel free to open a new one if need be. Kind regards,

@deringo Please give a try with the latest version. As explained above, a bridge layer has been added and basic features should work properly. I’m gonna mark this discussion as resolved, fee free to start a new one if need be.

Kind regards,

@aboutm2
I haven’t heard from you for a while so I’m gonna marked this ticket as solved.
Feel free to open a new one need be.

Best Regards

@ugotta Sorry for the late reply. Well maybe in your case Markup Mardown is not the ideal candidate. It doesn’t make sense at all for me to provide a shortcode as I disable / force the editor on the backend… ??

To answer to your question about a technical point of view, I haven’t tested it yet but you could try using the global helper and register your shortcode like this :

<?php
add_shortcode( 'markdown', function( $attrs, $content = '' ) {
  return mmd()->markdown2html( $content );
});
?>

That should work. ??On the opposide if you just need a standalone version, I published on my GitHub account a ready-to-use example:
https://github.com/peter-power-594/markdown-shortcode/

Other coders from the community have been using this approach for decades, you provide a shortcode like [markdown]…[/markdown] bundled with a standalone library for example a markdown parser via a plugin – or custom helpers inside your child theme depending from your requirements.

I haven’t found the target repo on Github anymore, it is a well-known technic. ??With the widely use of PHP’s Composer or Javascript’s Babel / Webpack tools, different approaches are preferred nowadays due to dependencies’nightmare but that is still a valid way to do if you can include by hand the required dependencies without pain. ??

Feel free to give it a try when you can and tell me what works for you.

Have a wonderful day, and kind regards