Error on update

  • Resolved d79

    (@d79)


    2 years, 7 months ago

    Updating the plugin on a couple of websites (from version 4.3.2 to 4.4.1) gave the same error on both:

    An error of type E_COMPILE_ERROR was caused in line 1448 of the file <path>/wp-content/plugins/wp-security-audit-log/wp-security-audit-log.php.
    Error message: require_once(): Failed opening required ‘classes/Upgrade/Upgrade_43000_To_44400.php’

    I don’t know why, because the file exists (maybe require_once didn’t like the relative path rather than the absolute one? idk).

    What I’d like to know is: since it definitely skipped all the updating actions related to that file, is there a safe way to redo those actions once?

    I was thinking of executing the following code once:

    $wsal = WpSecurityAuditLog::get_instance();
require_once '<path>/classes/Upgrade/Upgrade_43000_To_44400.php';
$upgrader = new WSAL_Upgrade_43000_To_44400( $wsal );
$upgrader->run();

    Would it work or can it cause other issues?

    Thank you in advance.

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

    (@robert681)

    Hello @d79

    Thank you for your message and for using our plugin.

    I am sorry to read about your issue. The problem why the updates are failing is because in version 4.4.0 we have changed the database schema. So before upgrading to version 4.4.0 you need to first upgrade to version 4.3.6, since you are using an old version (4.3.2).

    To fix the problem, please follow the below procedure:

    1) Deactivate the plugin install
    2) Download update 4.3.6
    3) Install and activate version 4.3.6
    4) When that is successfully activated, upgrade to 4.4.1, the latest version.

    That should do the trick. Can you please follow the above and keep us posted about the status / fix?

    Looking forward to hearing from you.

    I believe you need to revert to 4.3.6 and update to 4.4.0 before trying 4.4.1 again – see my answer on this other post.

    Just encountered the same issue. Updated in the sequence as @hvianna posted,
    first to 4.3.6, then to 4.4.0 (4.4.0+ like 4.4.1 wouldn’t work), thanks!

    @robert681: It would be great if the migration logic from 4.3.6 could be added to future releases, so that a direct update to latest release works without extra steps.
    Also the required version step and the latest release (where migration hadn’t worked when updating to it directly) both differ in a minor release version, so breaking compatibility issues shouldn’t occur.

    • This reply was modified 2 years, 6 months ago by strarsis.
    Thread Starter d79

    (@d79)

    Hello @robert681,

    I’m sorry for the late reply.

    I can confirm what @hvianna has already pointed out: you need to go first from 4.3.6 to 4.4.0, and then update to 4.4.1.

    It would be nice if in the future this kind of updates would work regardless of the versions jump.

    Thank you for your help.

    Plugin Support robertabela

    (@robert681)

    Hello @d79

    Thank you for the update.

    As such you should be able to upgrade from 4.3.6 to any 4.4.x + builds. We’ve tested this extensively and I can confirm functionality. However, there are a few users (like you) who are encountering an issue upgrading, so we will run a few more tests and review the code again. If there are any issues, we’ll include them in the next update.

    Thank you very much for the update.

    Hello @robert681,

    I had the same issue. For the first time, I updated from 4.4.1 to 4.4.2. After, I needed to go to the 4.3.6 version and update it to 4.4.0, 4.4.1, and 4.4.2.

    And the error stopped in my terminal.

    I hope to have contributed.

    Plugin Support robertabela

    (@robert681)

    Hello @d79

    Can you please confirm if you managed to update successfully or not? If not, please try update 4.4.2 and let me know if that works.

    Looking forward to hearing from you.

    • This reply was modified 2 years, 4 months ago by robertabela.
Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Error on update’ is closed to new replies.