Heading no space after signs (#) issue
-
# Heading one
==><h1>Heading one</h1>There is no space after that number signs (
#):
#a-inline-tag-link
Still converted to<h1>a-inline-tag-link</h1>Is this a bug or is it a compatible syntax. This will break the automatic #taglink
-
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. ??
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 ???♂?
@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 headingFor 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
@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 1I 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
@ugotta Thank you for your patience, I got something working ??
When you can please upgrade to 3.8.1 I’ve just released. If you disabled at least H1 from the panel options, you should be able to use the ‘#’ sharp sign as you described above for tags & ordered list. You don’t need to use the space option anymore. ?? A bit of a surprise for me, writing with sharp is actually convenient.
Sharing the source code helpt me a lot, the magic looks like in the following file:
\wp-content\plugins\o2\modules\checklists\load.phpHere is the specification for the list :
var $task_item_regex = "/^([ ]{0,3})([xo#*-])(\s+)(.*)/";As you wrote earlier, single space are used to indent the unordered / ordered list, and other components are limited so let’s say it’s kind of a sweety minimal custom markdown setup ?? From the wordpress admin edit screen you should be able to edit the O2 posts without disturbing the source code on the frontend editor.
Just a few things to keep in mind:
- You have to to uncheck H1 heading levels for the feature to work otherwise it wouldn’t be possible to separate headline/tag/list properly. And uncheck the space option as well.
- After digging a bit, the standard backslash is used as the escaped char for markdown as well. I used a few CSS and Javascript tricks to visually display
\#in the backend editor as#. There can be a few glitches if you try to select the text with the mouse for example but it’s working well. - EasyMDE is using 1 tab or 4 spaces to indent the list by default, so I updated the preview feature and tuned a bit the input/output so it can work with 1 space directly in the editor. I didn’t do extensive testing but that seems to work and should cover your case at least.
- Writing an ordered list with the sharp sign is not a conventional markdown standard, data are saved as it is in the database with the escaped sharp sign and rendered without the \ via a PHP filter. That should protect you in case you switch to an alternative markdown editor.
I really need to move on other features / fixes. For DynamicApps I will try to check it later, can’t tell you a precise timeline. I appreciate your understanding and hope that helpt
Kind Regards,
Peter
- You must be logged in to reply to this topic.
