Wordpress LScache Plugin: Drop Query String Multisite Setup
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi Support I run multisite woocommerce store with a subdirectory setup. The drop query string settings can only be done under the network admin, drop query string settings is not available under the primary site and subsites. So under network admin, I enter the following query string to be dropped, pa_attribute_color When I click save settings, the field would not save. So I went ahead to add the following code under htaccess CacheKeyModify -qs:pa_attribute_color Save the htaccess file. And go back to litespeed cache settings under network admin. The value pa_attribute_color is not showing under the drop query string field. Whats odd is when you click save settings, the value CacheKeyModify -qs:pa_attribute_color is no longer availbale under htacess. So how do I drop query string correctly? Thank you an example of the link with query string would look like this: http://www.abc.com/product1/?attribute_pa_color=red actually the code I input is this: CacheKeyModify -qs:attribute_pa_color Hi, but does this /?attribute_pa_color=red query actually reflect something ? because if you drop it , then https://ww.domain.com/?attribute_pa_color=red https://ww.domain.com/?attribute_pa_color=black https://ww.domain.com/?attribute_pa_color=green https://ww.domain.com/?attribute_pa_color=yellow these URL will return same page. Did it give you any warning or error message when you save it ? is htaccess file writable for PHP process ? Best regards, my store sells apparel so each products will have different color and sizes. The query string is only used to preselect the attributes under the page without clicking them. Regardless what the query string values are, it will always return to the same page. There is no warning when I click save under the settings page. htaccess file is also writable as I have included many custom codes previously. The real reason why I want to drop the query string is to prevent the plugin from caching different copies of cache for a single page. For example: link 1: http://www.domain.com/productA//?atttribute_pa_size=xlarge link 2: http://www.domain.com/productA//?atttribute_pa_size=large link 3: http://www.domain.com/productA//?atttribute_pa_size=medium link 4: http://www.domain.com/productA//?atttribute_pa_size=small link 5: http://www.domain.com/productA//?atttribute_pa_size=xsmall If a person clicks into link 1, a cache copy will be created. Subsequent customers who click into link 1 will be served with a cache copy. But as for link 2, 3, 4, and so on, no cache copies are created. So back to the question, how do you drop query string correctly? Hi, if that is your goal , you should NOT drop query string , it will force all the ?atti=xxx into same page like your link 1-5 , it display 5 different size, but when you dropped query , it will give you same size on all of them The real reason why I want to drop the query string is to prevent the plugin from caching different copies of cache for a single page. in this context , you should go to Cache -> Exclude -> Do not cache URI , add atttribute_pa_size to that field, then purge all Best regards, if i add attribute_pa_size to do not cache url, kind of lose the entire purpose of using this caching plugin. Its a woocommerce store, not a blog, all product pages will not be cache. Is the drop query string bugged? Why isnt it working? Hi, yes , but I dont know if you understand what I said about the consequence about drop the query string , it will essentially makes all of your atttribute_pa_size query return SAME page , regardless the size in query string you can manually write that line into your .htaccess , e.g. CacheKeyModify -qs:test and also please provide the report number , you can get it in toolbox -> report -> click send to LiteSpeed Best regards, Hi, Im going to mark this topic Resolved , due to lack of activity. If you still need help, please feel free to re-open it. When re-open it, please also change the topic status to not solved Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference