Customizer issues.

  • Resolved doubleweb

    (@doubleweb)


    8 years, 9 months ago

    Hello,

    We are using an widget system to customize various elements for an website.
    Once we installed WP Security Audit Log (latest version at the moment: 1.6.1) we noticed that is WP Customizer has stopped working corectly. To make sure this is not related with our custom themes, we switched back to “Twenty Fifteen”. Default widgets are behaving the same in WP Customized.

    Analyzing the logs, the following notice is coming in the Customizer response: "Notice: Undefined index: sidebar in wp-content\plugins\wp-security-audit-log\classes\Sensors\Widgets.php"
    It looks like this class is expecting a “sidebar” element, in the request, but wordpress doesn’t sent this information in customizer.
    I belive that checking if that array element is set, will solve this issue.

    Can you please test and if you confirm this issue can you please add a fix for it?

    Thanks!

    https://wordpress.org/plugins/wp-security-audit-log/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author WPWhiteSecurity

    (@wpwhitesecurity)

    8 years, 9 months ago

    Hello,

    Unfortunately we cannot reproduce the issue so it might be something else. Though we are soon (nexst week) releasing a new version of the plugin and the widgets sensor has been rewritten.

    So would it be ok if you wait till the release and test again? Alternatively contact us on plugins@wpwhitesecurity.com and we can give you a pre-release version of the plugin.

    Looking forward to hearing from you.

    Thread Starter doubleweb

    (@doubleweb)

    8 years, 9 months ago

    Hello,

    I installed today the latest version of this plugin: 2.0.0 and resumed the QA.
    One thing that I missed to share with you in my previous message was that debugger is turned on in wordpress configuration:

    define('WP_DEBUG', true);

    So basically in order to reproduce it, turn on debugger, and try to change any widget from customizer.

    Thanks

    Plugin Author WPWhiteSecurity

    (@wpwhitesecurity)

    8 years, 9 months ago

    Hello,

    This problem is particular to your setup which might be caused by a conflict or something similar. Since we are already in touch via email I will reply to you via email and continue working on this ticket via email.

    We can update the ticket at the end.

    Plugin Author WPWhiteSecurity

    (@wpwhitesecurity)

    8 years, 8 months ago

    Hello Doubleweb,

    Thank you for reporting this issue and helping us troubleshoot it via email. As discussed over email the issue at the moment is that there is no sensor for the customizer, hence the plugin tries to capture the change yet is unable to identify the source of the change, which in return generates an error.

    For the upcoming version we will be handling the error to ensure people can still use the customizer and in the future updates we will release a sensor for the customizer.

    Thank you for your cooperation and do not hesitate to get in touch should you have any further queries.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Customizer issues.’ is closed to new replies.