• Resolved mesmer7

    (@mesmer7)


    I went to look at my widgets last night.Just look at them, I had no intention of changing anything. But WordPress 5.8’s new widget block editor couldn’t locate the WOOF widget. The widget disappeared from my site and in the middle of trying to restore it the server blocked my access.

    According to my host’s tech support, they found this in the logs

    csf.deny: 69.14.###.### # lfd: (mod_security) mod_security (id:212740) triggered by 69.14.###.### (US/United States/d14-69-236-154.try.wideopenwest.com): 5 in the last 3600 secs - Sat Jul 31 03:42:14 2021

    (I obscured my ISP address)

    My hosts said the IP was blocked when ModSecurity WAF triggered a block due to a pattern that is usually used for XSS attacks by hackers or attackers. It could be a false positive alert as well sometimes. The related logs for the trigger is as below.

    Request:    GET /wp-content/plugins/woocommerce-products-filter/ext/by_text/css/by_text.css?ver=1.2.5.3
    Action Description: Access denied with code 403 (phase 2).
    Justification:  Test 'REQUEST_URI|ARGS_POST|ARGS_NAMES|REQUEST_COOKIES|REQUEST_COOKIES_NAMES|XML:/*|!ARGS:/body/|!ARGS:/content/|!ARGS:/description/|!ARGS:Post|!ARGS:desc|!ARGS:emailglobalheader|!ARGS:html_message|!ARGS:text|!REQUEST_COOKIES:/__utm/|!REQUEST_COOKIES:/_pk_ref/|!ARGS_POST:format|!ARGS:emailglobalheader' against '@rx image\/svg\+xml|text\/(?:css|html|(?:x-)?(?:(?:ecma|java|vb)script|scriptlet)).|.application\/x-shockwave-flash' is true.

    This has never happened before. And I had to install The Classic Widget Editor plugin in order to restore the WOOF widget to my shop page. So I’m attributing it to an incompatibility with WordPress 5.8’s new new widget block editor.

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

    (@mediawebster)

    Hello

    I don’t know for what reason, but some antiviruses don’t like the word text in the file name. And this issue is not related to WordPress update

    You can rename this file – plugins/woocommerce-products-filter/ext/by_text/css/by_text.css to plugins/woocommerce-products-filter/ext/by_text/css/by_t_filter.css

    and change code( https://share.stackovergo.com/image/i20210802144322.png ) in – \wp-content\plugins\woocommerce-products-filter\ext\by_text\index.php

    Thread Starter mesmer7

    (@mesmer7)

    I don’t understand how that response is relevant to the problem.

    Plugin Support mediawebster

    (@mediawebster)

    Hello

    This refers to the error that you inserted into the message

    This error message may have caused a problem with the blocks

    To prevent this from happening again on the widget editing page.

    Try in file – wp-content\plugins\woocommerce-products-filter-free\index.php change this code – https://share.stackovergo.com/image/i20210803164054.png

    		if (!isset($_REQUEST['legacy-widget-preview'])) {
    			add_shortcode('woof', array($this, 'woof_shortcode'));
    			add_shortcode('woof_btn', array($this, 'show_btn'));
    		}
    Thread Starter mesmer7

    (@mesmer7)

    Nope. That did not solve the issue. The block widget editor still displays “Legacy Widget. Widget is missing”. And I can’t find the WOOF widget at all.

    I tested this in a local install, not my live site. My development environment is limited to PHP 7.08. I’ve tried to upgrade it a few times, but could never get PHP 7.3 to run on my laptop.

    FYI: the latest WOOF upgrade didn’t solve the issue either.

    • This reply was modified 3 years, 3 months ago by mesmer7.
    Thread Starter mesmer7

    (@mesmer7)

    Oh, wait a minute. Maybe the problem is WooSidebars. I forgot that I embedded the Woof Product Filter widget in a WooSidebar. Now I see that plugin hasn’t been updated in almost a year.

    Plugin Support mediawebster

    (@mediawebster)

    Hello
    Ok! Please update the plugin and do a test

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Incompatibility with WordPress 5.8 new widget block editor.’ is closed to new replies.