Fatal Error

  • Resolved kmarvalova

    (@kmarvalova)


    3 years, 2 months ago

    When I update and activate your plugin (1.4.3), I get the following fatal error: 

    Uncaught Error: Call to undefined function Richardevcom\Apsfc\pll_current_language() in /var/www/clients/client4/web26/web/wp-content/plugins/add-polylang-support-for-customizer/includes/class-apsfc.php:136 Stack trace: #0 /var/www/clients/client4/web26/web/wp-content/plugins/add-polylang-support-for-customizer/includes/class-apsfc.php(250): Richardevcom\Apsfc\Apsfc->get_custom_customizer_option() #1 /var/www/clients/client4/web26/web/wp-includes/class-wp-hook.php(305): Richardevcom\Apsfc\Apsfc->on_option_theme_mods_get(Array) #2 /var/www/clients/client4/web26/web/wp-includes/plugin.php(189): WP_Hook->apply_filters(Array, Array) #3 /var/www/clients/client4/web26/web/wp-includes/option.php(225): apply_filters('option_theme_mo...', Array, 'theme_mods_mate...') #4 /var/www/clients/client4/web26/web/wp-includes/theme.php(974): get_option('theme_mods_mate...') #5 /var/www/clients/client4/web26/web/wp-includes/theme.php(1004): get_theme_mods() #6 /var/www/clients/client4/web26/web/wp-content/plugins/materialis-comp in /var/www/clients/client4/web26/web/wp-content/plugins/add-polylang-support-for-customizer/includes/class-apsfc.php on line 136

Notice: is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/xxxx/domains/xxxx.com/public_html/wp-includes/functions.php on line 5663

Notice: is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/xxxx/domains/xxxx.com/public_html/wp-includes/functions.php on line 5663

    `
    This error has been here before, but it’s been marked as resolved, so I’m opening it up again.

    • This topic was modified 3 years, 2 months ago by kmarvalova.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author richardevcom

    (@richardevcom)

    Hi there.

    Sorry for late reply. We have noted this bug and will debug it ASAP.
    Thank you for your reply.

    Meanwhile feel free to join our live support server here: Frontbee Discord server and I might be able to assist you directly.

    Thread Starter kmarvalova

    (@kmarvalova)

    Hi, thanks a lot for the response. Any news on this?

    Plugin Author richardevcom

    (@richardevcom)

    So far we could trigger this bug only in older versions, not in the new one.
    Could you please provide more detailed info on versions, plugins and theme you’re using? Read this to see what to share.

    Thread Starter kmarvalova

    (@kmarvalova)

    The error happened when updating to 1.4.3 of your plugin (currently at 1.4.3 but deactivated), WordPress version is 5.8.1, the theme is a child theme of Materialis Pro.

    Plugins: Advanced Custom Fields; Advanced Editor Tools; All in One SEO; All-in-One WP Migration; Breadcrumb NavXT; Classic Editor; Materialis Companion; Media from FTP; Page scroll to id; Pods; Polylang (3.1.1); Really Simple SSL; Show Current Template; Smush; Velvet Blues Update URLs; Wordfence Security; WP Sitemap Page.

    Thanks!

    Plugin Author richardevcom

    (@richardevcom)

    We could not reproduce the same issue on neither version of Polylang plugin. If it is possible we have discord server where you might possibly present the issue with screen share and we might be able to get on debugging it asap?

    • This reply was modified 3 years, 1 month ago by richardevcom.
    Plugin Author richardevcom

    (@richardevcom)

    UPDATE: @kmarvalova we double checked and since we couldn’t reproduce the same issue, please delete plugin, clear cache and reinstall the newest version from WordPress plugin library (Plugins > Add new).

    For now it seems, that previous plugin version had the issue and updating to new one will solve it.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Fatal Error’ is closed to new replies.