upgrade to 4.1.3.1 broke plugin and restrict acccess

  • Resolved danielspain

    (@danielspain)


    4 years, 3 months ago

    Upgraded from 4.1.2 to 4.1.3 and can’t access wpsal anymore, the plugin says that i dont have permissions to view the log(and i’m the site admin). Tried the upgrade to 4.1.3.1 released hours later and still the same problem occurs. Tried to delete the plugin, and the 3 tables wp_wsal_metadata,wp_wsal_occurences, wp_wsal_options and install 4.1.3.1 fresh: Same problem, not enough permissions to view the log or change wsal-settings.
    I’ve deleted everything and reverted to 4.1.2…
    I’ve tested with both wp 5.4.2 and wp 5.5.
    Is there a nre fix coming?
    Thanks in advance

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

    (@robert681)

    Hello @danielspain

    Thank you for using our plugin and sorry to read about your problem. Most probably this is happening because an old permissions setting is still in the wp_potions table.

    Can you please send us an export of the wp_options table at [email protected]?

    Thank you.

    Thread Starter danielspain

    (@danielspain)

    Sent!

    Thread Starter danielspain

    (@danielspain)

    Solved, thanks!!!

    Plugin Support robertabela

    (@robert681)

    You’re welcome @danielspain

    Leaving a note for others who might encounter the same issue:

    To fix this issue, delete the setting wsal_restrict-plugin-settings from the wp_options table. This is a setting used in version pre 4.1.3 and unfortunately in some cases the plugin is unable to delete it during the upgrade process.

    Will you be fixing this in an update to 4.1.3.1? Not many WordPress users will know how to edit their database table to accomplish this.

    FYI: Here is the error message I am seeing in the Dashboard…

    WordPress database error: [Table 'mrgwater-wp-eAWTZHDk.wp_235f16480d_wsal_options' doesn't exist]
SELECT * FROM wp_235f16480d_wsal_options WHERE option_name = 'wsal-version'

    Following that error, there are other WordPress errors complaining that headers have already been sent. (Presumably by the database error from your plugin.)

    Hope that helps you figure out how to fix this.

    • This reply was modified 4 years, 3 months ago by oakleystudio. Reason: Additional info

    I’m not seeing the “wsal_restrict-plugin-settings” option in our wp_options table, but we are getting these errors as well.

    [Aug 12, 11:48:56] WordPress database error Table ‘village_hill_community.wp_wsal_options’ doesn’t exist for query SELECT * FROM wp_wsal_options WHERE option_name = ‘wsal-version’ made by require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), WP_Hook->do_action, WP_Hook->apply_filters, WpSecurityAuditLog->init, WpSecurityAuditLog->GetOldVersion, WpSecurityAuditLog->GetGlobalOption, WSAL_Models_Option->GetOptionValue, WSAL_Adapters_MySQL_Option->GetNamedOption, WSAL_Adapters_MySQL_ActiveRecord->Load

    I will try deleting the plugin and re-installing it.

    Plugin Support robertabela

    (@robert681)

    @oakleystudio and @larrydaniele

    The errors you are seeing are unrelated to the issue originally reported in this support thread. Please open your own thread.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘upgrade to 4.1.3.1 broke plugin and restrict acccess’ is closed to new replies.