Plugin just stopped working on all WordPress.

Hi wmosquini,

I had to remove the PHP + HTML widget from this plugin because of a security flaw in the way the plugin worked previously.

Please consider switching to the new widget screen (using Gutenberg) to use the PHP Everywhere block. As a way to make your site work again immediately, you can down-grade to an older version of the plugin from here: https://de.www.ads-software.com/plugins/php-everywhere/advanced/

I do not recommend this though because of security reasons.

See this thread for more details: https://www.ads-software.com/support/topic/help-my-php-code-does-not-work-anymore/

Best regards and sorry for the trouble

Alex

Alexander, I understand the reasons, but there is no point in you forcing this.

That is, for your solution, either I use Gutemberg or I lose the functionality of the plugin. This is unacceptable for you to force this.
The correct thing is for the plugin to work in versions tabs, or at least give the option to choose.

They simply broke several projects here at the company, for the plugin developers it’s normal… I understand.

Hello,

Instead of fixing a flaw in the widget functionality, the latest version of “PHP Everywhere” just kills this functionality entirely. This is akin to throwing away an entire car, just because it has a flat tire or a broken part. So, I share @wmosquini ’s disbelief at the solution chosen by the plug-in author (whom I thank nevertheless for his hard work over the years). Part of the plug-in author’s justification seems to be that all WordPress sites have now moved to Gutenberg. But this isn’t the case for my site. I don’t know if there are stats somewhere on the number of WordPress sites that have stayed away from Gutenberg, but the “Classic Widgets” plug-in has 700,000+ users, and the alternative “Disable Gutenberg” plug-in 600,000+ users. So, we are already at a total of 1,300,000+ users. And this is without counting all the artisanal ways described in the WordPress documentation for “Restoring the classic Widgets Editor”.

@kubussumatra ,

I fully agree with what you said.

I’m still using the classic widget in WordPress and I know several other developers who still remain in this version, so I don’t understand the reason to “end” the plugin for this version.

Another living proof that the classic version is heavily used is the classic editor, which has over 5 million installs… but I think that’s just numbers.

I understand that safety is first, but I don’t believe that WordPress forced someone to disable support for the widget and classic editor, if that were the case, they wouldn’t have plugins to re-enable this mode.

For me it was an extremely hasty change, it impacted on several sites because the plugin simply stopped working and damn any kind of impact (positive or negative), a straight shot in the foot.

For me it was a very significant impact, now I will have to look for another plugin solution in PHP, unfortunately.

Hi folks,

I used this plugin also on many WordPress sites and was happy with it. Funnily in the last days I thought about a donation for it ?? But then this happened ??

I had two choices:
1. Switching to another plugin – hopefully with no security leaks…
2. Creating some micro-plugins for these cases and every client.

Finally I decided, to switch to the Plugin “Code Widget” from Solution Box. Currently without any known security leaks, hopefully also in future ?? It can also be used as a widget.

Regards,
Bernd

@barinformatik ,

After the update, I started testing the “Code Widget” plugin on a new project I’m working on.
At first it meets my demands for Widgets, especially with the classic version.

For internal pages, I’ve been using the “Insert PHP Code Snippet” plugin (xyzscripts.com) for some time now, as it allows me to create a global shortcode and use it anywhere on the site.

Why not add an “at your own risk” check box option to turn on the shortcode and widget for the classic editor.