• Resolved VAR

    (@varrie29)


    Hi there,

    So I have this Woocommerce site where the shop filter (FacetWP) and currency switcher (Woocommerce Price Based on Country) instantly broke upon plugin activation, so I disabled htaccess for root, wp-admin and plugin to solve it straightaway.

    I did not check further which other plugins actually broke its functionality, and I am not sure which htaccess might be causing it. I thought it was probably all related to the plugin htaccess but I also saw some skip rules and query rules being set in root htaccess too, so that got me confused.

    Apart from the plugins that provide frontend features for the site, I also have these critical plugins that may be somehow hard to confirm if working:
    – Plugin that processes PayPal payments (not sure if I should exempt the URL query parameter or the plugin folder)
    – WP All Import which updates (and creates) product listings automatically at a certain schedule.
    – eBay lister plugin which auto-updates sales on the website and on eBay and lists + syncs product details
    – Media offloader which syncs (and sometimes uploads/downloads) media file between WordPress and DO Spaces/Wasabi

    There are several more plugins but I think can be checked in the front end if working. So my question is how can I test this one? Do i need to add all plugins I have to both root and plugin htaccess as skip rules/exception?

    I actually had a product XML feed that got inaccessible because of the Uploads folder htaccess but the 403 error was not logged. Instead, it was a generic Litespeed 403 error message so I actually spent some time thinking it was on the server configuration.

    Thank you for your answer!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author AITpro

    (@aitpro)

    Do you have the BPS or BPS Pro plugin? If BPS is blocking something a 403 error will be logged in the BPS Security Log. The only case where a 403 error would not be logged is if JavaScript is doing something at the Browser level. Post any 403 errors that are related to plugins that are being blocked or not working correctly. So I can take a look at them. Note: The BPS Security Log logs all 403 errors whether or not BPS is actually blocking something. If something else like ModSecurity is blocking something then BPS will log the 403 error for that.

    BPS and BPS Pro have built troubleshooting capability that allows you to turn on|off individual features for troubleshooting.

    BPS troubleshooting steps > https://forum.ait-pro.com/forums/topic/read-me-first-free/#bps-free-general-troubleshooting
    BPS Pro troubleshooting steps > https://forum.ait-pro.com/forums/topic/read-me-first-free/#bps-free-general-troubleshooting

    Thread Starter VAR

    (@varrie29)

    I have the Pro.

    Okay so it seems like I need to exhaust and test everything, which functionalities broke or not when I enable htaccess root/wp-admin/plugin. So that means adding exceptions to plugin htaccess and skip rules in root htaccess?

    Also regarding the 403, I actually tested it several times, and nothing was logged in the Security log except for login attempts by bots. I believe there was even a quick summary of the logged errors so there was no 403 there. I wouldn’t have known about it if Facebook did not email about the product XML feed not being accessible.

    Also, does using BPS completely lock the root htaccess? I mean, if I change some settings in Litespeed (that translates to addition or removal of some htaccess rules), does that get reflected in the root htaccess as well?

    Thanks!

    Plugin Author AITpro

    (@aitpro)

    Since you have Pro then contact me directly via my contact form and I will login to your site and figure out what needs to done > https://www.ait-pro.com/contact/.

    Locking the root htaccess file is optional. You can lock or unlock the root htaccess file on the htaccess File Editor page.

    Thread Starter VAR

    (@varrie29)

    Okay great! I will raise the questions there! Thanks.

    Plugin Author AITpro

    (@aitpro)

    Closing this thread.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Setup Help!’ is closed to new replies.