• Resolved dersien

    (@dersien)


    The latest update breaks my site and I have to delete this plugin for me to access my WordPress admin page normally.

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    I’m terribly sorry for this and this really wasn’t supposed to happen. Were you getting any errors in your PHP log?

    i confirm critical error after last update.denied access to admin panel

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Hi @panosbee,

    What was the error? Could you share the error message here from your PHP logs?

    Parse error: syntax error, unexpected ‘)’ in /home/proclica/demo.proclic.al/wp-content/plugins/host-webfonts-local/includes/class-ajax.php on line 147

    me as well

    PHP-Version 7.2.22

    Typ E_PARSE Line 147 in /wp-content/plugins/host-webfonts-local/includes/class-ajax.php syntax error, unexpected ‘)’

    Same here. Multisite of online store.

    PHP Parse error: syntax error, unexpected ‘)’ in /var/www/html/wp-content/plugins/host-webfonts-local/includes/class-ajax.php on line 147

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Hi everyone, could you try v4.1.2?

    I noticed one thing that could cause issues in some (a LOT, apparently) configurations. So I changed it.

    Hopefully that’ll resolve the issue.

    Let me know if it works!

    Removing the comma after “false” in line 146 of class-ajax.php fixed the problem for me.

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Hi!

    Yes, that’s exactly what I did in v4.1.2!

    I never knew a trailing comma in parameters could throw a critical error in some configurations. Years ago, it was even advised!

    I guess I learned something today… ??

    its oki now, thanks

    v4.1.2 works, thanks!

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Happy to know that resolved your issues. v4.1.3 contains some more UX improvements.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Critical Error after Updates’ is closed to new replies.