Support » Plugin: Custom Login Page Customizer » PHP 8 – fatal error

  • Resolved Joachim B.

    (@jba1969)


    Login Customizer generates a fatal error when a wordpress site with php 8.0.13 is restored from backup (checked with different backup solutions):

    Fatal error: Uncaught Error:
    Attempt to assign property “plugins” on bool in /Users/nicholas/Sites/restored/wp-content/plugins/login-customizer/freemius/start.php on line 74( ! )

    Error: Attempt to assign property “plugins” on bool in /Users/nicholas/Sites/restored/wp-content/plugins/login-customizer/freemius/start.php on line 74Call Stack#TimeMemoryFunctionLocation10.0001357944{main}( )…/index.php:020.0001358256require( ‘/Users/nicholas/Sites/restored/wp-blog-header.php )…/index.php:1730.0002358896require_once( ‘/Users/nicholas/Sites/restored/wp-load.php )…/wp-blog-header.php:1340.0003368960require_once( ‘/Users/nicholas/Sites/restored/wp-config.php )…/wp-load.php:5050.0004373752require_once( ‘/Users/nicholas/Sites/restored/wp-settings.php )…/wp-config.php:12360.125917582336include_once( ‘/Users/nicholas/Sites/restored/wp-content/plugins/login-customizer/login-customizer.php )…/wp-settings.php:40970.126017582336LoginCustomizer\lc_fs( )…/login-customizer.php:5380.126317624024require_once( ‘/Users/nicholas/Sites/restored/wp-content/plugins/login-customizer/freemius/start.php )…/login-customizer.php:32

    • This topic was modified 3 months, 2 weeks ago by Joachim B..
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Abdul Wahab

    (@abdulwahab610)

    Hey, @jba1969

    Login Customizer is tested with PHP 8.0.13. This specific error is coming into your environment. Can you please contact us at our support forum? So we can debug the issue and fix it for you.

    Looking forward.

    Thread Starter Joachim B.

    (@jba1969)

    There is nothing to “fix” on my website yet.
    I dont let foreign people working or even fixing on my website.

    Instead of first checking your own product you try to make other software bad.
    Makes no sense at all to me.

    If you mean your plugin is tested, does NOT indicate the same environment etc.

    Make the fix in your software and then provide a new release with the fix.
    All other ways are not professional.

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