• We recently attempted to updat a site from v7.2.0 to v7.3.0. It resulted in a fatal PHP error. While we were able to recover the site by rolling back to v7.2.0, we can’t seem to do any further updates.

    The PHP error message is as follows:

    Declaration of mtekk\adminKit\setting\setting_string_nosave::maybe_update_from_form_input($input) must be compatible with mtekk\adminKit\setting\setting_base::maybe_update_from_form_input($input, $bool_ignore_missing = false) in?/home/stagingcctscprst/public_html/wp-content/plugins/breadcrumb-navxt-wpml/includes/adminKit/setting/class-mtekk_adminkit_setting_string_nosave.php?on line?59

    We are running PHP 7.4.33, WordPress v6.4.3, and the site in question also has the WPML extension (v1.5.7) installed as well.

    Any assistance into this matter would be appreciated.

    Thanks,
    Ian

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author John Havlik

    (@mtekk)

    Based on the error, double check that you are actually using the latest version of the extension (the error should not show up with version 1.5.7 of the extension).

    Thread Starter Ian Chapman

    (@ianchapman)

    My apologies – I had a typo in my original post. The site is actually using v1.5.6 (not .7) of the WPML extension.

    However, we are unable to upgrade to v1.5.7, despite having just recently renewed our license. We thought perhaps that might be because we needed to update the main NavXT plugin first (and that is what caused the fatal PHP error).

    The plugins page says: “There is a new version of Breadcrumb NavXT WPML Extensions available.?View version 1.5.7 details.?Automatic update is unavailable for this plugin.”

    The settings page shows that the license is valid. We even removed it and then re-licensed it just in case, and it still shows it is valid. But it doesn’t give us the option to upgrade the WPML extension from v1.5.6 to v1.5.7.

    Thanks,
    Ian

    • This reply was modified 9 months, 2 weeks ago by Yui. Reason: unlink
    Plugin Author John Havlik

    (@mtekk)

    For support with the extension plugins, you should open a support ticket on the site the extension was purchased from. In general, you want to update the extensions before updating the core plugin. Also, you probably want to remove that link you have in your reply.

    Thread Starter Ian Chapman

    (@ianchapman)

    OK, I’ll reach out to meek support to ask why the WPML extension plugin isn’t allowing an update to happen.

    Thanks for the warning about the link, however, I missed the hour time limit for editing the post. Ugh.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Error after updating to v7.3.0’ is closed to new replies.