Entire Site Offline due to Anywhere Elementor

Unfortunately, I discovered another of our 15 sites that uses AE also offline: restoresgf.com When I rename the AE folder, the site comes back online, but THIS time it’s costing us an entire page of content.

I could probably rebuild that page with other tools, but the only way to get to the content housed with the Anywhere plugin is to have the plugin activated. As soon as I do that, the site generates a critical error. I need to at least be able to see the content within the AE plugin so I can copy/paste it into other page widgets or in some way rebuild the pieces of our sites that were using AE.

Thankfully only three of our fifteen WordPress sites have AE installed. Oddly, the third one is still online. I looked at other plugins common to the three sites and found only one – Kadence Slider – that was used on BOTH the offline sites. Despite that plugin not being updated recently, I tried deactivating that one instead of AE, but to no avail.

The only other difference I saw in the site that was still online was that it was still using a slightly older version of Elementor. I tried rolling Elementor back to this same, older version on restoresgf.com, then activating AE. But it immediately goes into the critical error mode. Help!

Wow – 24 hrs. no reply. Kind of a critical issue when a website is taken completely offline.

Hi @cakins

Our plugin is active on thousands of websites and working without any issue.
So what you are facing is not because any common bug from our plugin.

As you mentioned about the critical error, can you check your error log or ask your host about the detailed error message about it.
Please ask your host why they think that this issue was due to our plugin and provide us that info.

You can also reach us here with more details https://www.elementoraddons.com/contact-us/

Hi,

I have the same error too. I updated Anywhere Elementor to the latest version, and it took down my site. Renamed the plugin, and the site was back up. Installed a fresh copy from the directory, and the site went down even before activating it. Renamed that, and the site was back up.

In either of these cases, I have debug log enabled, but no error was logged or displayed.

BUT – there’s a PHP error log as below:
[29-Oct-2021 07:26:16 UTC] PHP Fatal error: Cannot use Elementor\Plugin as Plugin because the name is already in use in /wp-content/plugins/anywhere-elementor/includes/shortcode.php on line 5

Does this help?

Anywhere Elementor version 1.2.4
Elementor version 3.4.6

Sax.

Hi @saxatwork

Our latest version is 2 months old and just these 2 two reported incidents so far. It seems like it is related to some specific environment.

Can you reach us here as we might need some additional info related to your setup?
https://www.elementoraddons.com/contact-us/

Ok, if this helps anyone, I updated to PHP >7, and that worked. It’s possible that most of us having issues are still on version 5.6 or below. Try pointing your domains to a PHP version higher than 7 through your cPanel, and that should work.

@anandau14 sorry, didn’t see your reply, but I was able to sort it out on my domain ?? please see my reply above

In our case, it turned out to be a PHP version issue. Our hosting provider had somehow downgraded our PHP environment. About the same time Anywhere Elementor threw errors on three sites other oddities cropped up across very low trafficked sites that had had NO changes to them. Plugins wouldn’t update, the Elementor editor wouldn’t load, etc. Just out of the blue.

I contacted the host again, and they discovered the PHP issue – something they should have done a couple weeks earlier when I first reported it. While it did LOOK like a plugin issue with Anywhere Elementor since turning that plugin off would immediately bring our sites back online, it was really a larger issue.

Once PHP was put back to the newer version ALL of the issues went away.

@cakins, @saxatwork

Thanks for the additional info. We will make sure to display a proper warning instead of such a throwing such fatal error.