Fatal error caused wp_lazy_loading_enabled filter

  • Resolved Mirko

    (@mirkodii)


    2 years, 11 months ago

    Hi,
    we use your plugin together with Swift Performance plugin. Since the last updates these two plugins lead to the following fatal error (php logfile output):
    [03-May-2021 10:54:22 UTC] PHP Fatal error: Uncaught ArgumentCountError: Too few arguments to function Swift_Performance_Asset_Manager::{closure}(), 1 passed in /www/htdocs/xxxxxxx/xxxx.de/wp-includes/class-wp-hook.php on line 292 and exactly 2 expected in /www/htdocs/xxxxxxx/xxxx.de/wp-content/plugins/swift-performance/modules/asset-manager/asset-manager.php:121

    This is the answer of Swift:
    “If you get the following error, probably it is a plugin conflict. There is a plugin which is using improperly the wp_lazy_loading_enabled filter.
    You should deactivate your plugins one by one to find which one cause the issue. If you fount it, you can contact to the plugin author to fix the issue.”

    Would you please check and provide a fix?

    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • Miha

    (@mplusb)

    2 years, 11 months ago

    Hi @mirkodii,

    Thank you for reaching out and explaining!
    I investigated and indeed there seems to be an incompatibility between the 2.
    I went ahead and opened a ticket regarding this so our dev team can fix in our next update.
    You can follow the progress here: https://github.com/WPChill/strong-testimonials/issues/254

    At the moment we do not have a solution to offer, but we will investigate so it can be fixed next week when we plan to release our update.
    We sincerely apologize for the trouble!

    Warmly,
    Mihaela

    Miha

    (@mplusb)

    2 years, 11 months ago

    This topic will be marked as resolved as we have an open ticket on GitHub regarding this. Please keep in mind that the ‘resolved’ status is only for this support thread, not the issue on GitHub.

    Thread Starter Mirko

    (@mirkodii)

    2 years, 11 months ago

    Hi again,
    in your initial reply you mentioned “we will investigate so it can be fixed next week when we plan to release our update”.

    Till now, the issue is still open on GitHub and more than 3 weeks have passed. Could you please provide a reliable fixing timeline. Otherwise we have to consider to swap plugins.

    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatal error caused wp_lazy_loading_enabled filter’ is closed to new replies.