Backend Problems after plugin update

[ruuddebree]

Can somebody inform me what has happened with Elementor and/of flywheel local between a plugin update from 3.14.1 to 3.15.2 This in combination with an update Pro from 3.14.1 to 3.15.1. When making a backup with Updraftplus after this update the whole backend of the editor does not work anymore. Pages cannot be opened, fonts and video links do not work.

Besides it is very strange that when downgrading Elementor from 3.15.2 to 3.14.1 everything is working fine again. But that is a work around and no Solution.

---

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

I tried everything Elementor to has advised for editor troubleshooting but nothing works. —

System Details

• Local Version:

• Operating System (OS) and OS version:
  Mac M1 and also Macbook Monterey. On both devices the same Problems.
  Backup as well with All in One and Updraft plus.

---

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)

---

Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

[Nick-B]

Hi @ruuddebree

So you have reached out to Elementor support but nothing they have provided works? Generally speaking, we’re unable to offer much support in regard to fixing plugins and themes as those are handled by their own developers. There shouldn’t be anything from our end that would cause a break in functionality to Elementor. If you’re finding that things are just not opening or are timing out, you could try adjusting some resources or other PHP settings. Running through our performance optimization guide might give some ideas as well.

Troubleshoot: Performance Issues

[ruuddebree]

This is the Diagnostic log. Are there Instruction files or video’s to fix this ?

[afragen]

Xdebug: [Step Debug] Could not connect to debugging client - flooding logs

The log level here is only for debugging xDebug itself, not for debugging PHP. adding the single line to the php.ini.hbs file does work. {{#if xdebugEnabled}} xdebug.mode=debug,develop xdebug.log_level=0 {{else}} xdebug.mode=off {{/if}} xdebug.client_port=9003 xdebug.start_with_request=yes xdebug.discover_client_host=yes It would be a nice addition and pretty simple to do.

[ruuddebree]

I made the Changes, but still the same Problem. On my hosting site all plugins are working Fine, but as soon as I made a backup and import it in local there are loading problems with the elementor editor backend.

[afragen]

Sorry @ruuddebree, I was responding on how to eliminate the xDebug errors, or at least hide them.

Seems like you might have a larger problem with Elementor.

FWIW the xDebug errors you reference above aren’t related to any plugin conflicts. I suggest you set define('WP_DEBUG', true); in wp-config.php. At least then you should have a stacktrace of any errors.