• Resolved q1LLa

    (@vov7512)


    Hi. I have a website that no one has worked on for a long time. After some kind of update to the Elementor plugin – I don’t remember exactly, some pages stopped working and gave an error. I have attached all the logs below. Please help me solve the problem.

    Logs – https://pastebin.com/rVJTfWfq
    Elementor info – https://pastebin.com/Bkc1TibR

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • Alain

    (@alainelementor)

    Hello @vov7512!
    Thank you for contacting us.

    I was reading your previous conversation, and I understand it.

    In this case, It might be a conflict with your theme or plugins.
    Please follow these steps, and let me know if it solved your issue:

    • Deactivate all of your plugins except Elementor. If this solves the problem, gradually activate your plugins one by one, until you spot the problematic plugin.
    • Switch your WordPress theme to WordPress TwentySixteen (or other default WordPress theme) temporarily – and see if it solves your error.
    • Also, I noticed your server is running PHP 7.4. Please try updating to 8.0 or 8.1.

    I hope this can help you.
    Regards,

    Thread Starter q1LLa

    (@vov7512)

    I have already tried deactivating all plugins. As soon as I turn on the Elementor plugin, an error immediately appears. I also tried the standard themes and the Hello Elementor theme. Switching to php version 8.0 or 8.1 or 8.2 does not give any results.

    Thread Starter q1LLa

    (@vov7512)

    Hello? @alainelementor!

    What other options are there to solve the problem?

    Plugin Support Milos

    (@miloss84)

    Hi there,

    To address these concerns, I recommend taking the following actions:

    1. Update or Reinstall WordPress: This is often an effective initial step to resolve any underlying issues. Updating or reinstalling WordPress can help address any compatibility issues or bugs that may be affecting your site’s functionality.
    2. Check for Custom Code Conflicts: If updating or reinstalling WordPress doesn’t resolve the issue, it’s possible that there may be custom code on your site conflicting with the new version. Review any customizations or third-party plugins to identify and resolve any conflicts.
    3. Review Site Layout: Take a moment to assess whether your site layout is created with sections or containers. If you’re using sections and experiencing issues, consider deactivating the flexbox container from our experiments. This can help alleviate any layout-related conflicts and improve stability.

    Also, this could happen due to our Elementor performance experiments you can try to deactivate them. To deactivate them you can go to Elementor > settings > features

    Performance features currently in the experimental stage are:.

    • Improved Asset Loading – Should improve page speed by only loading the functionalities needed by that page. This experiment reduces the amount of code loaded by default, which translates to significantly faster page load times and better page speed scores.
    • Improved CSS Loading – An experiment that only loads the CSS of widgets on a page once, in order to prevent multiple requests to the server. With this experiment, CSS files are loaded as inline style tags.
    • Inline Font Icons – This experiment renders icons as SVGs without loading the Font-Awesome and eicons libraries. Since SVGs are vector-based images which are rendered using the browser’s engine, they do not increase server requests which improves performance
    Thread Starter q1LLa

    (@vov7512)

    I have the latest version of wordpress. The latest version of the woodmart theme. I don’t think the mistake is because of this. This happened on some kind of elementor plugin update.

    Here are more logs, maybe this will help solve my problem: https://pastebin.com/zf6CRPr5

    Thread Starter q1LLa

    (@vov7512)

    The main thing that I noticed. Pages with feedback forms do not work (all widgets are standard everywhere).

    Plugin Support Milos

    (@miloss84)

    HI there,

    In addressing the compatibility issue between Elementor and your Woodomart theme on your website, I recommend considering a rollback to a previous version of Elementor. By reverting to a version that aligns seamlessly with your theme’s requirements, we can ensure optimal functionality and a smooth user experience.

    To facilitate this process, I suggest utilizing Elementor’s rollback feature, which provides a straightforward method for returning to a previous version. You can find detailed instructions on how to execute this rollback by visiting the following link: [Insert hyperlink to the Elementor rollback guide – https://elementor.com/help/rolling-back-to-a-previous-version-of-elementor/].

    Should you encounter any challenges or require further assistance during this process, please don’t hesitate to reach out. Our team is here to support you every step of the way.

    Thank you for your attention to this matter, and we look forward to resolving the compatibility issue promptly.

    Best regards,

    Thread Starter q1LLa

    (@vov7512)

    @Milos I rolled back the version to 3.18.0. It doesn’t help.

    Plugin Support Milos

    (@miloss84)

    Hi again,

    If the rollback feature did not help you therefore, we highly recommend that you report this issue to the support team for the Woodmart theme, so they may further troubleshoot and provide any recommendation (or possible fix) to resolve this issue.

    Should they need any help from us, they can open an issue on our Github account and our developers will be happy to assist. https://github.com/elementor/elementor/issues

    For reference: What do we Support?

    Kind regards,

    Plugin Support vipul78

    (@vipulelementor)

    We shall be closing the ticket due to inactivity. You can open another topic here if your issue persists or if you have any other query.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Fatal error: Uncaught Error: Call to a member function get_default_args()’ is closed to new replies.