madeglobal

Obviously it’s just an admin thing, but it’s highly annoying to have the huge banner at the top of every admin page which can’t be removed.

Any update on when this will be fixed?

Does anyone know what the latest version of pro is??? I have Version 3.1.31 of pro plugin, but I see that the non-pro version is Version 4.1.0. So frustrating!

I note these version for Twig:
Brizy uses Twig version 1.42.5,
Responsive-Menu uses Twig version 1.42.2
Responsive-Menu-Pro uses Twig version 1.33.0

I also note that the fatal error we’re seeing is caused between Brizy and Responsive-Menu-Pro.

I’ll add a “me too” to this problem in the hopes it gives the plugin owner some reason to fix it. My solution, for now, is to disable this plugin. Obviously, that’s not a long term solution…

I’m getting this since the latest WordPress update (5.6) – what did you do to resolve it?

Unless the code for WPEC gets updated, I think we’re going to have to call it a dead plugin. There are multiple incompatibilities throughout the code.

It’s incredibly sad to have come to the end of the road with this great plugin, but our shop just won’t work at all and though we could go through and fix the individual issues, they of course have the potential to be overwritten and broken again by a subsequent update of the plugin.

Anyone fancy taking on this plugin and making it PHP7.2+ compatible?

Sadly, if it needs videos to explain things like moving paragraphs and adding images, this new editor has missed the point completely, in my opinion.
I’m sure it’ll get there. But judging from what I’ve seen and have now used, it’s not close yet. Moving it to the core would be hugely detrimental to the reputation of WordPress for new users and experienced ones alike.
Keep working on it. Maybe it’ll all come good in the end.

Thanks – seems to be the issue.

None the less, a solution would be really good!

And I agree. NGG loads all its bloat on every page, regardless of what is on that page.

Still seeing PHP warnings such as these on our site.

Declaration of M_Ajax::define() should be compatible with C_Base_Module::define($id = ‘pope-modul…’, $name = ‘Pope Modul…’, $description = ”, $version = ”, $uri = ”, $author = ”, $author_uri = ”, $context = false)

Any luck on this? It happens occasionally for us too… ??

Same with me. Posting so that I get to see the server fix, hope it’s an easy one!

Using ftp or your terminal, navigate to the directory /wp-content/plugins/wp-hide-post/public/css and rename the only file in there (which has the wrong name) to wp-hide-post-public.css and you’ve “fixed” it. Though why the plugin needs to load an empty css file every page, I really don’t know ??