Fatal error: undefined method on upgrade

  • Resolved james.nash

    (@jamesnash)


    11 years, 4 months ago

    When we updated to the most recent version of the plugin we received this fatal error.

    Fatal error: Call to undefined method WSAL_Settings::IsSandboxPageEnabled() in [redacted]\wp-content\plugins\wp-security-audit-log\classes\Views\Sandbox.php on line 28

    We are new to the plugin. The last version being our first installation. We did not purchase any of the paid add on plugins, at least not yet.

    We are behind a load balancer. We use this code to inform other less flexible plugins:

    $_SERVER[‘REMOTE_ADDR’] = preg_replace(‘/^([^,]+).*$/’, ‘\1’, $_SERVER[‘HTTP_X_FORWARDED_FOR’]);

    Not sure this is a factor in the error but it may have an impact.

    James

    https://ww.wp.xz.cn/plugins/wp-security-audit-log/

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

    (@robert681)

    11 years, 4 months ago

    HI James,

    Thank you for showing interest in our plugin. Sorry to see you are encountering an error.

    In the last version we removed the sandbox and it seems you had the sandbox enabled from the developers tools, can you please confirm? If that is so you can manually disable the sandbox, so it is not called and such error is not generated by removing the option value “s” from the option wsal-dev-options in the wp_options table.

    If you would like to use the sandbox let us know and we can give it to you as a separate stand alone file.

    As regards having the plugin behind a proxy that is not an issue, WP Security Audit Log can even read the source IPs even when installed behind a reverse proxy or web application firewall. You can read more about this feature in New WP Security Audit Log Supports Reverse Proxies and WordPress Firewalls.

    While I trust the above answers your query and helps you solve the issue please let me know should you have any further queries or should the issue persist.

    Thread Starter james.nash

    (@jamesnash)

    11 years, 4 months ago

    Robert,

    Thanks for your quick response.

    I’m afraid that did not solve the problem. The Sandbox checkbox was not set in the admin area. We were running with default values.

    The value of wsal-dev-options is an empty string.

    James

    Plugin Support robertabela

    (@robert681)

    11 years, 4 months ago

    HI James,

    Thank you for the update. Ok let me recap a bit so we can reproduce your issue:

    1. Are you able to activate the plugin or when you try you get such error?

    2. When exactly this error is being generated?

    3. Or the plugin is working fine and you only see this error in the debug.log?

    As soon as we have all this information we will look into the issue and definitely come up with a solution.

    Looking forward to hearing from you.

    Thread Starter james.nash

    (@jamesnash)

    11 years, 4 months ago

    Robert,

    Sorry, I should have been more complete in my explanation.

    The error shows on activation. The admin pages returns an empty page except for the error.

    It’s not just a plugin conflict because I’ve disable all the other plugins and I still get the error.

    The behavior of the front end changes depending on whether other plugins are activated. If no other plugins are activated then the front end behaves as expected. When I activate the other plugins, I get a blank page on the front end.

    So there may be a plugin conflict at work but it’s not the only issue.

    It’s difficult to isolate which of the other plugins is the problem because access to the admin is not available.

    I hope that helps.

    Thanks for the follow up.

    James

    Plugin Support robertabela

    (@robert681)

    11 years, 4 months ago

    HI James,

    Thank you, we are looking into this issue and will get back to you.

    WPWhiteSecurity

    (@wpwhitesecurity)

    11 years, 4 months ago

    HI James,

    We fixed the issue and will be releasing an update of the plugin with some new features later on this week or next week.

    If you would like to test it out drop us an email on [email protected] and we can give you an interim build which have been tested and all, i.e. it is a stable build.

    Looking forward to hearing from you.

    Thread Starter james.nash

    (@jamesnash)

    11 years, 4 months ago

    We are currently about to deploy so we are going to push what’s tested and stable.

    We’ll get your new version in the next deployment though.

    Thanks for addressing the issue.

    James

    WPWhiteSecurity

    (@wpwhitesecurity)

    11 years, 4 months ago

    HI James,

    We just released version 1.3.3 that addresses this issue. Let me know how it all goes and thank you for supporting this plugin.

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

The topic ‘Fatal error: undefined method on upgrade’ is closed to new replies.