• Had to roll back 3.26.2 to 3.26.1 due to site crashing when running database updater. These recent issues with 3.26.0 are unacceptable and I am frustrated beyond words and evaluating alternatives.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Nemanja

    (@nemanjat)

    Hi @johnriedl

    Thank you for contacting Elementor Support. We aplogize for any inconvience caused by the database updater.

    Are you experiencing a critical error after running the updater? Can you check the server error logs and share the relevant records with the stack trace?

    Thank you!

    Thread Starter johnriedl

    (@johnriedl)

    The “solution” was to revert to 3.25.11 and Pro 3.25.5 and TURN OFF Elementor updates. Version 3.26.x is broken and does not work on our sites. You can blame all the other plugins, but our sites worked fine until Elementor updated to version 3.26.0 and our sites work as intended NOT USING version 3.26.x. Extensive troubleshooting and wasting my time isn’t necessary – it is CLEAR what isn’t working.

    Plugin Support Milos

    (@miloss84)

    Hi there,

    Thanks for reaching out to us, and I’m sorry to hear about the issues you’re encountering.

    Please note that there are conflicts with some plugins after the update, and these are being investigated to determine if the issue is related to Elementor or if the third-party plugins need to release an update on their end to stay compatible with the latest Elementor update and development deprecations.

    To troubleshoot this, please try the following steps:

    1. Deactivate Third-Party Plugins:
      • Deactivate all third-party plugins except Elementor and Elementor Pro.
      • Update Elementor and Elementor Pro to the latest versions.
    2. Check for Plugin Updates:
      • Some plugins have already issued fixes for compatibility issues. Keep an eye out for plugin updates and update them accordingly.
    3. Reference Guide:

    If the issue persists after following these steps, please let us know so we can further investigate.

    Kind regards

    Thread Starter johnriedl

    (@johnriedl)

    No, other plug-ins are NOT at fault here. Elementor cannot hold every other Plug-in hostage and claim everything else is incompatible when those other plug-ins worked before the Elementor update. Elementor needs to work within the WordPress ecosystem and not attempt to dictate how other plug-ins may or may not function. Elementor doesn’t own the ecosystem. Stop pushing the blame on every other plug-in, stop delaying support, stop asking the same redundant questions and fix your own compatibility issues. Otherwise, Elementor is no longer a viable option in this space and users should look elsewhere for alternatives. When we have issues, it is typically due to Elementor, not other plug-ins. That’s the real problem here.

    @johnriedl I agree 100%, but my previous comment has been deleted. It’s obvious that not only do they blame everyone else and fail to fix their bugs, but they also don’t accept constructive criticism.

    Any fix to this issue?

    Plugin Support Nemanja

    (@nemanjat)

    Hi @johnriedl

    Thank you for taking the time to share your feedback. I completely understand your frustration and sincerely apologize for the inconvenience you’ve experienced. It’s never our intention to shift blame or delay providing solutions.

    Elementor is designed to work seamlessly within the WordPress ecosystem, and compatibility with other plugins is always a top priority for us. When issues arise, it’s important for us to investigate thoroughly and ensure we address the root cause. In some cases, conflicts can occur, and identifying those conflicts is crucial to providing an effective resolution.

    To help expedite the troubleshooting process, I kindly ask for the server error logs again. These logs are essential for us to identify what’s happening behind the scenes and pinpoint the exact issue. If you’re able to provide them, please share them as a screenshot or include the entire stack trace in tools like: https://gist.github.com/

    Looking forward to your response.
    Kind regards!

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.