Fatal Error version 5.3.4.1

  • Resolved gdubow

    (@gdubow)


    1 year, 1 month ago

    Hello,

    We are experiencing a fatal error when updating to latest version of the free plugin version. The site crashes and we are unable to recover. Only way to fix is by removing plugin via SFTP or restoring previous backup.

    • WordPress version : 6.7.2
    • WP Activity Log plugin version 5.3.4.1
    • PHP version 8.2
    • Other installed plugins or themes WPML, Elementor

    Fatal error:

    operator not supported for strings in /nas/content/live/site-name/wp-content/plugins/wp-security-audit-log/classes/Migration/class-migration.php:1112#012Stack trace:#012#0 /nas/content/live/site-name/wp-content/plugins/wp-security-audit-log/classes/Migration/class-abstract-migration.php(189): WSAL\Utils\Migration::migrate_up_to_5340()#012#1 /nas/content/live/site-name/wp-includes/class-wp-hook.php(324): WSAL\Utils\Abstract_Migration::migrate('')#012#2 /nas/content/live/site-name/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)#012#3 /nas/content/live/site-name/wp-includes/plugin.php(517): WP_Hook->do_action(Array)#012#4 /nas/content/live/site-name/wp-settings.php(704): do_action('init')#012#5 /nas/content/live/site-name/wp-config.php(139): require_once('/nas/content/li…')#012#6 /nas/content/live/site-name/wp-load.php(50): require_once('/nas/content/li…')#012#7 /nas/content/live/site-name/wp-admin/admin.php(34): require_once('/nas/content/li…')#012#8 /nas/content/live/site-name/wp-admin/plugins.php(10): require_once('/nas/content/li…')#012#9 {main}#012 thrown in /nas/content/live/site-name/wp-content/plugins/wp-security-audit-log/classes/Migration/class-migration.php on line 1112

    An error of type E_ERROR was caused in line 1112 of the file /nas/content/live/site-name/wp-content/plugins/wp-security-audit-log/classes/Migration/class-migration.php. Error message: Uncaught Error: [] operator not supported for strings in /nas/content/live/site-name/wp-content/plugins/wp-security-audit-log/classes/Migration/class-migration.php:1112
    Stack trace: 0 /nas/content/live/site-name/wp-content/plugins/wp-security-audit-log/classes/Migration/class-abstract-migration.php(189): WSAL\Utils\Migration::migrate_up_to_5340() 1 /nas/content/live/site-name/wp-includes/class-wp-hook.php(324): WSAL\Utils\Abstract_Migration::migrate('') 2 /nas/content/live/site-name/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) 3 /nas/content/live/site-name/wp-includes/plugin.php(517): WP_Hook->do_action(Array) 4 /nas/content/live/site-name/wp-settings.php(704): do_action('init') 5 /nas/content/live/site-name/wp-config.php(139): require_once('/nas/content/li…') 6 /nas/content/live/site-name/wp-load.php(50): require_once('/nas/content/li…') 7 /nas/content/live/site-name/wp-admin/admin.php(34): require_once('/nas/content/li…') 8 /nas/content/live/site-name/wp-admin/plugin-install.php(16): require_once('/nas/content/li…') 9 {main}

    Any ideas on how to prevent this so we can safely update?

    Thank you,

    Graham

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

    (@lucianwpwhite)

    1 year, 1 month ago

    Hello @gdubow !

    I am really sorry to hear about this experience!

    We have had a handful of users experiencing this, and the good news is that we do have a patched build that will solve this one. This fix will be included in the upcoming official plugin release, so make sure you update to that when it will be available.

    You can find the patch here, labeled as “Operator not supported for Strings error”. To install it:

    1. Download the patched build from the link above – “Operator not supported for Strings error”
    2. On the Plugins page -> Upload new
    3. Replace the old build with this one
    4. Activate the plugin and everything should be ok.

    Let me know how it goes! I am confident this should do the trick.

    Thread Starter gdubow

    (@gdubow)

    1 year, 1 month ago

    Hi @lucianwpwhite thanks for the information on the patch. Can you please clarify the exact steps to upload the patched version?

    Should we deactivate and delete the existing plugin first? Next, upload the patched version and activate?

    When the official version comes out, do we need to deactivate and remove the patched version? Any ideas when the new one will come out?

    Do you recommend we just wait for official release?

    Thanks,

    Graham

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    1 year, 1 month ago

    Hi Graham,

    Thanks for your follow-up!

    Sorry if my previous message was a bit light on details. Here are the exact steps to install the patched version:

    1. Go to Plugins → Add New in your WordPress dashboard.
    2. Click Upload Plugin, select the patch .zip file, and upload it.
    3. When prompted, click “Replace current with uploaded” — this will safely overwrite the existing version without needing to deactivate or delete anything manually.

    The patched version will be officially included in the next plugin update. Once that update is released, you can update as usual via the dashboard — no special steps required.

    We’re in the final stages of testing and development, so the release should be out very soon, though I can’t confirm an exact ETA just yet.

    Should you have any other questions, feel free to reach out!

    Thread Starter gdubow

    (@gdubow)

    1 year, 1 month ago

    Hi @lucianwpwhite thanks very much for the additional details!

    Do you recommend we just wait until the latest official release is out? We can just stay on the same stable version for now without using the patched update?

    • This reply was modified 1 year, 1 month ago by gdubow.
    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    1 year, 1 month ago

    Hello again @gdubow,

    Glad to hear the details were helpful!

    Whether you apply the patch or wait for the next official release is entirely up to you. That said, I would recommend using the patched build — it has already been confirmed to resolve the issue and also includes a few additional bug fixes and enhancements beyond the previous version (5.3.4).

    That said, it’s safe to use in production, and once the official release is out, you’ll be able to update as usual.

    Let us know if you need anything else in the meantime!

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    1 year ago

    Hello @gdubow

    We have just released update 5.4.0 which includes a fix for this. You can safely update your plugin to the latest version now and check how things are going this time. Please let us know if there are any further issues!

    I do appreciate your patience while we were working on this, and also for bringing this into our attention!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Fatal Error version 5.3.4.1’ is closed to new replies.