E_ERROR after upgrade

  • Resolved WrdprsKN

    (@wrdprskn)


    5 years, 1 month ago

    Hello,

    After recently updating WP Security Audit Log from version 3.5 to version 3.5.1, we get the following error on the WordPress admin dashboard:

    Fatal error: Call to undefined method WSAL_Views_FrontendSetupWizard::GetWeight() in /wp-content/plugins/wp-security-audit-log/classes/ViewManager.php on line 180

    The error isn’t always there, but it shows up for some users at certain times. Also, we got an automatic WordPress e-mail saying that WordPress detected a fatal error. This is the error that it listed:

    An error of type E_ERROR was caused in line 180 of the file /wp-content/plugins/wp-security-audit-log/classes/ViewManager.php. Error message: Call to undefined method WSAL_Views_FrontendSetupWizard::GetWeight()

    What could be causing this issue, and how can it be fixed? I have been using WP Security Audit Log for quite a while and really like it, but I will have to disable it if it continues to cause fatal errors.

    We are using WordPress 5.2.4. I actually just upgraded WordPress from 5.2.1 to 5.2.4 also, so I’m not sure whether it’s the WordPress upgrade or the WP Security Audit Log upgrade that caused the issue. However, it needs to be fixed either way.

    Thank you very much for your help.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support robertabela

    (@robert681)

    Sorry to hear you are having such an issue @wrdprskn

    It seems that some of the files were not updated during the update process since in version 3.5.1 we completely removed the reference to the FrontendSetupWizard

    Can you please:

    1) Deactivate the plugin.
    2) Download the plugin from the WordPress repository.
    3) Extract the files.
    4) Upload them to /wp-content/plugins/wp-security-audit-log/ overwriting all the old files.

    Please let us know if this does the trick for you.

    konexys

    (@konexys)

    Hello,

    We also had this problem on all WordPress with this plugin installed, altought we were already using the last version for a while.

    What we’ve noticed is that updating or installing other plugins causes WP Security Audit Log incompatibility. Usually this is fixed by replacing all files (it did the trick this time again), or by uninstalling and installing after the other plugins are installed/updated.

    Best regards,
    David Duarte

    Plugin Support robertabela

    (@robert681)

    Thank you for your message @konexys

    It is indeed a confirmation that the updates did not run properly. Unfortunately it is not something we have control on. Should there be anything else we can help you with, please do not hesitate to ask.

    Thank you for using our plugin.

    Plugin Support robertabela

    (@robert681)

    Hello @konexys and @wrdprskn

    This issue was occurring because the plugin was trying to load a view which does not exist. This typically happens when something goes wrong with the updating process.

    To cater for this we have released update 3.5.1.1 which prevents wrong classes from being added.

    Please update to 3.5.1.1. Thank you for reporting this issue and let us know should you require any further assistance. Thank you for using our plugin.

    konexys

    (@konexys)

    Hello @robert681,

    We updated all plugin installations, and everything seems to be alright.
    Thank you very much.

    Regards,
    David Duarte

    Plugin Support robertabela

    (@robert681)

    Glad to hear all is working fine now @konexys

    May I ask you to please rate our plugin? The reviews really help us. Thank you very much and do not hesitate to get in touch should you have any other questions.

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

Tags