ugotta

The previous answer was missed, maybe I wrote it wrong. It should be:
_#_This should not be a heading

I will now summarize:
#This should not be a heading
_#This should not be a heading
_#_This should not be a heading

The new setting option ‘Preserve spaces’ had the opposite effect, as I didn’t describe it well at the beginning.

The usage of the Ordered List in the O2 editor I am using is as follows:
# level 1
_# level 2
__# level 3
# last level 1

The usage of the Inline Auto Tag in the O2 editor I am using is as follows:
#tag-a #tag-b #tag-c

When using O2 with MM, the last ‘# last level 1’ must be retained, otherwise the content will be truncated and not displayed. Therefore, I mentioned earlier whether it is possible to disable the first level title to avoid this issue, but it did not work until version 3.73. This rare need can be ignored.

Therefore, I suggest that in the MM settings options, the Headline can be divided into two modes to adapt to different user habits:

• non-strict mode
• Strict mode: There must be no spaces at the beginning of the line; There must be a space after ‘#’

Also, I will provide you with the O2 plugin address and theme for testing purposes:
https://github.com/Automattic/o2
https://github.com/tomjn/p2020

If we no longer consider the O2 plugin, it would be great if MM could be used together with another front-end editor plugin:
https://www.ads-software.com/plugins/acf-frontend-form-element/

Thank you for your patient inquiry and resolution.

Version 3.7 test result:

# this is a heading → normal
#This should not be a heading → Resolved in V3.6
_#This should not be a heading, there is a space at the beginning of the line → unsolved in V3.7

Toggle specific heading levels also has no effect.

I forgot to tell you that I am using some front-end editors (o2, Frontend Admin by DynamiApps) that led to the above requirements. If these modifications conflict with MMD, you can skip my submission. I’ll mark it as resolved first.

Thank you for your hard work…

Thank you for the prompt repair.
There is another issue where there is a space at the beginning of the line:

# This_is_a_heading
 # This_should_not_be_a_heading

Perhaps too strict grammar may not be applicable, you can skip this.

Else:
Is there a way to block the use of # Heading level 1. Only block first-level title.

Sorry for not making it clear, just pay attention to the following:

# This_is_a_heading
#This_should_not_be_a_heading

When there is no space separating the symbol (#), it is also converted into a heading title. Can the Makdown conversion rule improve this situation.

Theme:
github.com/tomjn/p2020

Plugin:
github.com/Automattic/o2
github.com/Nikschavan/p2-mentions
\inc\mentions.php
$content = preg_replace( “/@$name\b(?!\))/i”, $replacement, $content );

Yeah, just a refresh button, or Or the other way around:

template=images page_limit=1 img_size=full order=rand image_link=refresh Fancybox=false

template=one-folder page_limit=10 img_size=full order=rand Fancybox=true

In addition, you can consider supporting WP native album short code [Gallery], global Settings, Maybe it will attract a large number of users

Try Exclude URLs:
#^/?$#

I wrote a large paragraph of my idea, but then deleted it and gave a direct reference to the front-end editor. Maybe you are familiar with it: github.com / Automattic / o2

Its features needless to say, the automatic title and tow post-format are my favorite. I’ve made some modifications, which are only used under specific query to adapt to the theme and language:

1. Remove the “inline tags” function at the end of the article, but retain the “inline tags” function;

2. Modify the length of automatic title：Aside, quote, status…;

3. Modify the support for non English tags. The source code is slug. I manually change it to name. It seems that there is no problem;

There are still some things that I can’t do, such as:

4. Button mode to select all the article post-format: I combine with automatic post tagger to realize automatic selection of article post-format. For example, if there is a gallery in the article, the article form of the album will be automatically selected. At the same time, it can also automatically classify and automatically add tags;

5. Drop down method to select category: when in a category, the editor will automatically select the current category;

6. Drop down or customize multiple groups of buttons: This is very important and necessary;

7. Preview and edit should be separated: it is faster to modify;

The above ideas and suggestions for the front-end editor are for your reference only. Your editor is very modern. It might be better to combine them.

I’m not a coder. Reading code basically depends on guessing. I’ll try GitHub.

Next, if you want your plug-ins to have revenue immediately, or become a plug-in with a 100000 class installation in the future, I will propose requirements separately.

Version 2.0.1, when editing published articles:

Feature images still produce duplicate images;

FE cannot retrieve the image in the article, and the image address is lost;

The article picture caption text still cannot be saved;

Always show a “null” tag；

After modifying the same article many times, “you do not have permission to edit this post” appears. After a period of time, it returned to normal.

Several suggestions:

Feature images can be uploaded directly or selected from the media library.

You can type in a new tag, not just select an existing one.

At least class trigger can choose no cookie.

The image issue only occurs in “N seconds after page load”. After sliding the web page, the image will still be loaded automatically, but the experience is not very good. For example, when showing an album with eight pictures, I have to enable lazy loading images.

I now set “0 seconds after page load” to avoid it. This itself is not WPPP’s problem, you can leave it alone…… However, if you provide an up and down animation method to trigger lazy loading images.

Click triggered popups ignore cookies or different cookies. Maybe it would be better to make it optional. I’m very entangled with this right now. I have to create two identical popups to achieve the same goal.

Thanks for the quick fix

By the way, I would like to make some suggestions:

1. It can adjust the size of the setting box (resize:horizontal)
2. Seconds in cookies

It’s just been tested on the local server again.
Disable all other plugins, change the theme, set different conditions, the isuue obviously still exists.
Maybe the version we downloaded is not the same as yours.

It has also been tested on different browsers. The new version is only occasionally normal. After a while, you can’t click overlay to close it.
Roll back to 2.0.3.3 again