• Resolved jjwr11

    (@jjwr11)


    After updating to verion 4.2.9 from version 4.1.29 the website does not work and I get this error on the nginx logs:

    2021/07/28 13:58:18 [error] 1071#1071: *19307583 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught TypeError: Argument 1 passed to Redux_Field::output() must be of the type string, null given, called in /home/www/wp-content/plugins/redux-framework/redux-core/inc/classes/class-redux-output.php on line 156 and defined in /home/www/wp-content/plugins/redux-framework/redux-core/inc/classes/class-redux-field.php:237
    Stack trace:
    #0 /home/www/wp-content/plugins/redux-framework/redux-core/inc/classes/class-redux-output.php(156): Redux_Field->output(NULL)
    #1 /home/www/wp-includes/class-wp-hook.php(303): Redux_Output->enqueue(”)
    #2 /home/www/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array)
    #3 /home/www/wp-includes/plugin.php(470): WP_Hook->do_action(Array)
    #4 /home/www/wp-includes/script-loader.php(2083): do_action(‘wp_enqueue_scri…’)
    #5 /home/www/wp-includes/class-wp-hook.php(303): wp_enqueue_scripts(”)
    #6 /hom” while reading response header from upstream, client: 47.62.70.170, server: www, request: “GET /es/descarga/ HTTP/1.1”, upstream: “fastcgi://unix:/run/php/php7.2-fpm.sock:”, host: “www”, referrer: “https://www/es/”
    2021/07/28 13:58:21 [error] 1071#1071: *19307583 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught TypeError: Argument 1 passed to Redux_Field::output() must be of the type string, null given, called in /home/www/wp-content/plugins/redux-framework/redux-core/inc/classes/class-redux-output.php on line 156 and defined in /home/www/wp-content/plugins/redux-framework/redux-core/inc/classes/class-redux-field.php:237

    After restoring to the version 4.1.29 the website works again.

Viewing 8 replies - 1 through 8 (of 8 total)
  • You don’t have to go that far back. I resorted to version 4.2.7 and the error message was gone. So, presumably it’s something that was introduced/changed in 4.2.8

    Got the same error on 4.2.9 update and site went down with critical error message. Had to rollback to 4.2.7, thanks for the tip @cambofrizz!

    Plugin Author Kev Provance

    (@kprovance)

    Please download this update, version 4.2.10, from our repo (https://github.com/reduxframework/redux-framework/archive/refs/heads/master.zip).

    Do not rename the zip. It should say redux-framework-master.zip

    Upload that ZIP via the Add Plugins in screen. It will install Redux into a separate folder (meaning, you won’t lose the version you are running now, in case it’s a rollback).

    Once installed, deactivate your current version of Redux. Then activate the 4.2.10 version. Please check and see if your issue has been resolved. Please report back any errors if they occur. Also, if it works out, also report that.

    Thanks!

    – Kev

    But what is the exact solution for this issue?

    Plugin Author Kev Provance

    (@kprovance)

    Please download this update, version 4.2.10, from our repo (https://github.com/reduxframework/redux-framework/archive/refs/heads/master.zip).

    Do not rename the zip. It should say redux-framework-master.zip

    Upload that ZIP via the Add Plugins in screen. It will install Redux into a separate folder (meaning, you won’t lose the version you are running now, in case it’s a rollback).

    Once installed, deactivate your current version of Redux. Then activate the 4.2.10 version. Please check and see if your issue has been resolved. Please report back any errors if they occur. Also, if it works out, also report that.

    Thanks!

    – Kev

    Appreciate the 4.2.10 update Kev, worked a treat.

    Plugin Author Kev Provance

    (@kprovance)

    @lukergc, awesome! Thank you much for the feedback!

    Plugin Author Kev Provance

    (@kprovance)

    Redux Version 4.2.10 has been officially deployed. If you should experience further issues, please post a new ticket as I may not see replies to old ones.

    Thanks!

    – Kev

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Error on 4.2.9 update’ is closed to new replies.