frizzel

It’s on a local install at the moment.

However, I noticed a difference between the 2 methods.
When your plug-in does the minifying there’s a line (without any tags): ob_start_detected
That comes from All-In-One SEO Pack:

if ( $this->ob_start_detected ) {
			echo 'ob_start_detected ';
		}

When I just make that echo line empty, there are no errors in the minifying.
I’m now only puzzled why your plug-in triggers this, and the other doesn’t.

@philip Ah yes, I see what you mean by the plugin targeting wp_content which indeed wouldn’t work with Elementor. I understand what you are doing in supplied code. However, the section blocks I wanted to not load have varying content. So, I decided to save them as Elementor templates and then conditionally call them in the post type template used.

Thank you for your help and suggestions.

??? The shortcode tags I mentioned ARE designed to not just ‘hide’ but instead ‘not load’ content in between. What you are saying is that Elementor does not support this (at least the [/close] tag). That’s a big difference, and to be honest quite an unsatisfactory answer.

But, as a suggestion: why not have the Elementor option of hiding a section make it ‘do not load this section’ instead of ‘display:none’? I mean, if you want to hide it, you obviously don’t want to load it.

• This reply was modified 7 years, 3 months ago by frizzel.

That should indeed fix this.
Thank you.

I perfectly understand chocolat.js is not included in the theme anymore. That’s not the point. It goes wrong with the deregister scripts.

If in the file includes/panel/scripts.php I comment
wp_deregister_script( 'magnific-popup' );
Mapplic scripts load, but with wrong css.
If I also comment
wp_deregister_style( 'magnific-popup' );
everything is fine.

I was about to post about your suggestion as I saw it in the theme’s log.
Yes, I’ve done that already.
It does not resolve the issue.
Can you please now look into that file I mentioned every time and resolve the issue there?
Thank you.

I already tried that, but made no difference.

However, I had an outdated version of OceanWP theme. Updated that to latest version (1.4.6). Also, again updated Ocean Extra to latest version (1.3.7).
Same result: scripts and styles of Mapplic would not load, whether Lightbox JS enabled or disabled.

Only when I replaced the latest version with the 1.3.4 version of the file includes/panel/scripts.php Mapplic scripts and styles would load. So it’s clearly in there with the call to the new script.

Although I have disabled the Lightbox script, it seems the conflict is indeed caused by the change from chocolat.js.

I have tested 1.3.5, but with the includes/panel/scripts.php from 1.3.4 and then Mapplic scripts do load.

By the way, shouldn’t that change in the lightbox script be in the changelog?

Yes, I have disabled the Lightbox script.

By the way, it’s not as I assumed from 1.3.6 that causes the problem, but from version 1.3.5

Wow, very quick reply, thank you.

OK, I’ll wait and see what you come up with in a next release.

In the meantime, just to let you know, I thoroughly enjoy working with your plug-in (and I think you deserve more downloads).

Plus, your add-ons (especially the front end editing) are very nice, too.

Not sure, but I was not thinking of an extended discussion (because that’s in the ‘Messages’ already). More like: now the reported bug or task is in a field “Description” which I suppose is fine. But then be able to reply in a separate text box which would have a description like “Reply” or “Solution” or “Fixed” (maybe even a choice? but that’s probably going a bit too far).

I perfectly understand software is not bug free, thank you very much.
But this is about the AMOUNT of fixes since launch of v3.0.
And that is far above what I consider ‘normal’. Which tells me – and I repeat – you have NOT thoroughly tested before public release.
If you don’t agree with that, you are either in denial or just arrogant.

Hi @woodyhayday,

Thanks for the quick replies. Really appreciate that.

What I’ll do is remove WordFence and try to install your plug-in again, probably tomorrow (it’s quite late here now).

Regarding 2. (de-activation): No, the plug-in was in the list, however, clicking on “de-activate” just did nothing.

But, as said, will try to install again and post the results here.

Hi @woodyhayday,

Thanks for your reply. To answer your questions:
1. PHP 7.0
2. No, just a normal website.
3. Yes, WordFence (and maybe I should remove that and replace with Sucuri, as some other hosting provider has advised me).
4. SiteGround
5. Uhm, not yet, maybe later.

Thanks.

Finally figured it out: ‘layers=m’. Would be nice to have that clearly in the documentation, though. (Or have I just missed that somewhere?)