Bug: Plugin is clearing widget content

Hi Besim, thank you for the issue report.

That is weird indeed. L&L does not have any features related to widgets, so it’s hard to imagine how the issue could be caused by the plugin. I’ll try to recreate the issue on my local test site, and see what I can find.

Does the issue disappear if you deactivate the plugin?

Hi Eliot,

No, the behavior of the HTML widget is normal when the plugin is disabled.

Hi Eliot,

I have now been able to isolate the problem somewhat by disabling all plugins on a test basis and testing them individually.

The problem occurs when I enable Advanced Custom Fields Pro. The problem occurs when the plugin is active individually or with all others. If I deactivate it, the HTML widget works without problems.

One more thing about the HTML widget, the behavior is as follows:

I open a HTML widget in the widget editor (or in the customizer) and instead of the code being displayed highlighted, it only appears very briefly and then the HTML editor is empty. And interestingly also locked, i.e. no HTML code can be inserted.

When I reload the editor page normally, the code appears again for a fraction of a second. So it seems to be a display problem in connection with ACF Pro.

If there is anything else I should test, please let me know.

Greetings,
Besim

Since I’m still watching the problem here: can I help with more information? Please do not hold back with such requests.

Regards,
Besim

Hi Besim, apologies for how long this ticket has sat without a follow-up, I’ll see if I can take over for Eliot here and get this figured out. I’ve gone ahead and installed ACF Pro and L&L on a local multisite installation and when I add the “Custom HTML” block to the widget area of my main site it all works as expected. I’d love to try to figure out why this is happening for you so here are a few additional questions that might surface some info that’ll help us find the culprit:

1. Does this happen with all HTML widgets regardless of what’s contained in them? In other words, if you create an HTML widget with markup that contains a single tag, does that still make things disappear?
2. Does this happen on all sites in your multisite or only certain ones (maybe only the main site or a subsite)
3. You mention that this occurs in a multisite environment. Are you able to replicate this on a non-multisite WordPress installation? Depending on where you’re working, this might be too tedious to test, but I thought I’d ask in case you’re able to clarify that
4. Does this happen regardless of the theme that’s activated? If you’re unable to check this, what theme are you using?

While I’m at it, I thought I’d mention that you might find the Loops & Logic forum to be a better place to get product support in the future. It’s a much more active community than this support in the WordPress plugin repository.

Hi Ben, thanks for your reply!

I’m going through your questions:

To 1: Yes, all html widgets are affected, if i have activated both of the plugins.

To 2: Yes, too.

To 3: Yes, I can reproduce this effect on a complete another, very simple non-multisite wordpress on my server.

To 4: Yes.

Offer: I can provide you access to one of my small wordpress installations with this problem. Drop me a mail on besim at karadeniz dot de.

Regards,
Besim

Thanks for the thorough clarification! I’ve sent you an email.

Hi Besim, it seems that the behaviour you’re noticing is a compatibility issue caused by the Custom HTML widget in Customizer loading a library called HTML Lint, which is used for validating syntax in the code editor. The Tangible Template field type (which L&L registers as a custom ACF field) loads its own HTML Lint, but a different version. Where this seems to be causing a problem is that ACF apparently loads all field types’ JS/CSS files on Customizer screens, even when the field type is not used.

We’ve identified a solution that will resolve this in an upcoming update. The next release of L&L will likely focus on a restructuring of the plugin to pave the way for our eventual third-party integration add-on for L&L, but I expect that the version after that will include a fix to this issue. Thanks for providing so much feedback to help us get to the bottom of this!

Looks similar to my issue, as you noticed @bentangible

My temporarily fix:
https://discourse.tangible.one/t/l-l-codemirror-conflict-with-max-mega-menu-plugin/693/3?u=avanti

• This reply was modified 2 years, 4 months ago by studioavanti.

Hi again @besimk, it’s been a long time coming but I’m happy to report that the latest 3.0.0 release of the plugin includes a fix to this customizer widget issue you identified.

Thanks! Tested and working.