bobdobbs

Yes, I still get the same Notice.

I also still get multiple http requests for js.

The issue might be theme specific. But this is the case, then it’s not because I’m doing anything with the_content.

I’m not making any use of any hooks connected to the_content.

Pasted here is my Page.php: https://pastebin.com/e3bvQqV4

As you can see, there are no extraneous ‘p’ tags wrapping aroung the_content.

If EM is injecting content using the Page template and hooking into the_content, then it appears that EM is injecting broken markup.

Hey Marcus.

No, the issue isn’t resolved yet. As far as I can tell, the wpautop function is enabled by default in wordpress, in the absence of an override. In other words, it’s an important part of how wordpress words.

The documentation for the function gives a way to disable the feature across the whole site.

This causes behaviour that is undesirable generally: when ‘p’ tags aren’t generated by the wysiwyg editor, they must be edited by hand. This violates users expecations of how wordpress is supposed to work.

Of course a developer can work around this by manually adding p tags. But this solution isn’t really acceptable for non-developer users of wordpress.

This behaviour would also be unnacceptable for sites with existing content: all of a sudden, the ‘p’ tags would be stripped away, breaking design and possibly readability.

I imagine that the plugin might have been designed for sites without pre-existing content.

My next attack at this problem will be to figure out your suggested approach: disabling wpautop for pages that just have markup output by the plugin.

Of course this isn’t entirely unproblematic either, because some pages on the site that I’m building might have content produced by the wysiwyg editor and output from em. But it’ll be a start.

Hey Marcus.

This does indeed work.

However, it also breaks the rest of my site. Content in posts are no longer wrapped in ‘p’ tags.

Hi Phil.

Thank you. This solution works for me.

Hey Marcus.

No, the open p tag isn’t present if I switch the theme.

This obviously means that the broken code is coming from somewhere in my own theme.

Which template is used? Page.php?

bump

More information:

The tag specifically gets injected after </div=”em-wrapper”>,
and before the custom code that I’ve entered in the ‘formatting’ section.

Following is a screenshot showing where the tag gets injected:
https://imgur.com/BHNEuEt

Note: the screenshot shows a closing tag. That closing tag isn’t in the actual source code. However, it’s created by chrome as an error-correction response to the broken markup.

Hi Phil

Iv’e been developing a custom theme locally, but I’ve put it up for you to see. The events page can be seen here:

https://temporaryurl.scripteen.com/bx

If the loose tag is coming from the theme, which file should I be looking at?

This worked. Thanks.

I’ve discovered something:
This issue only happens when I’m using google chrome.

I discovered a js error displaying in the console when I hit the button to submit the selected image.

This error does not occour if I’m using another browser.

I suspect that a browser extension is somehow causing the problem.

Activated 2012: problem still exists.

Then I deactivated all the plugins: problem still exists.

I’m using a custom theme that I am in the process of creating.

I’ve created the loop myself. Here is the code:

https://pastie.org/6632233

I couldn’t get your foreach loop to work.

ST2 kept flagging an error in the syntax, and I couldn’t figure out which line it was on.

I don’t have a strong understanding of how widgets work, but also I’m creating a custom theme that I want to look a certain way. I’m not giving the site owner the option to control the appearance, so I’m not using widgets.

Also, the site won’t have a sidebar.