Wordpress LScache Plugin: Advanced Settings page wouldnt save on a 2nd WP installation
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hello, I have 2 WordPress sites on a server being powered by LiteSpeed (LiteSpeed server 5.1.13 and LiteSpeed Cache For WordPress Management Cache Plugin Version: 1.0.14.1) I have successfully saved my advanced settings settings with their corresponding unique login Cookie and Cache Tag Prefix settings for my installation: 1. /mydirectory/public_html/shop However, on trying to do the same for my wp installation at 2. /mydirectory/public_html the plugin does not save. On clicking the save changes button to save my settings, the Advanced Settings page at /wp-admin/admin.php?page=lscache-settings, changes to the following url: /wp-admin/undefined&tab=1&tab=3&tab=4 Can someone explain why the LS plugin is behaving this way in the case of my 2nd wp installation? (By the way, the /mydirectory/public_html actually is my main wp installation.) On my WHM side, both /mydirectory/public_html and /mydirectory/public_html/shop have enabled Cache Status under LiteSpeed Cache For WordPress Management -> Manage Cache Installations. Would appreciate a prompt response as both wp installations of mine, are in production. Thanks. This topic was modified 5 years, 8 months ago by nceebob. Hi @nceebob Can you try this temporary fix: remove litespeed-cache/admin/js/litespeed-cache-admin.js line 51 $( form ).attr( action , new_url) based on https://wordpress.org/support/topic/admin-404-error/ Hello, 1. Have delete line 51, $( form ).attr( action , new_url) , at : /mydirectory/public_html/wp-content/plugins/litespeed-cache/admin/js/litespeed-cache-admin.js 2. save the file in (1) 3. Emptied Entire Cache (/wp-admin/admin.php?page=lscache-dash -> Manage) 4. Gone to Advance Settings tab (/wp-admin/admin.php?page=lscache-settings ? Advanced Settings) 5. Inserted values for login Cookie and Cache Tag Prefix and when 6. I press the save changes button, the settings do not save. I still get a 404 page: /wp-admin/undefined&tab=4 Hi @nceebob, Can you also disable line 47 $( input[name=_wp_http_referer] ).val(new_url) ? You can remove it or disable it by adding // before it. Do you mind paste your LiteSpeed Cache Report here? so that we can know which plugins you installed, which can give a great help for us to reproduce your issue. It is in Litespeed Cache -> Environment Report Sure: Server Variables SERVER_SOFTWARE = LiteSpeed DOCUMENT_ROOT = /home/mydirectory/public_html X-LSCACHE = 1 LSCache Plugin Options version = 1.0.14.1 enabled = 1 radio_select = 1 purge_upgrade = 1 cache_commenters = 1 cache_login = 1 cache_favicon = 1 cache_resources = 1 mobileview_enabled = mobileview_rules = login_cookie = tag_prefix = check_advancedcache = 1 debug = 0 admin_ips = 127.0.0.1 test_ips = public_ttl = 172800 front_page_ttl = 43200 feed_ttl = 0 403_ttl = 3600 404_ttl = 3600 500_ttl = 3600 nocache_vars = nocache_path = purge_by_post = A.F.H.M.PT.T excludes_uri = excludes_cat = excludes_tag = nocache_cookies = nocache_useragents = Wordpress Specific Extras wordpress version = 4.7.3 locale = en_US active theme = Fuse active plugins = Array ( [0] => addthis/addthis_social_widget.php [1] => akismet/akismet.php [2] => amp/amp.php [3] => contact-form-7/wp-contact-form-7.php [4] => content-egg/content-egg.php [5] => cookie-law-info/cookie-law-info.php [6] => datafeedr/datafeedr.php [7] => db-cache-reloaded-fix/db-cache-reloaded.php [8] => force-regenerate-thumbnails/force-regenerate-thumbnails.php [9] => imagify/imagify.php [10] => krp_posts_featured_image/krp_posts_featured_image.php [11] => litespeed-cache/litespeed-cache.php [12] => nxs-snap-pro-upgrade/nxs-snap-pro-upgrade.php [13] => p3-profiler/p3-profiler.php [14] => photo-gallery/photo-gallery.php [15] => pixelgrade-shortcodes/plugin.php [16] => qqworld-collector/qqworld-collector.php [17] => regenerate-thumbnails/regenerate-thumbnails.php [18] => scheduled-post-guardian/scheduled-post-guardian.php [19] => social-networks-auto-poster-facebook-twitter-g/NextScripts_SNAP.php [20] => social-warfare-pro/social-warfare-pro.php [21] => social-warfare/social-warfare.php [22] => wpfront-user-role-editor-personal-pro/wpfront-user-role-editor.php [23] => wpfront-user-role-editor/wpfront-user-role-editor.php [24] => yieldkit/yieldkit.php ) /home/mydirectory/public_html/.htaccess contents: # BEGIN WordPress RewriteEngine On RewriteBase / RewriteRule ^index .php$ - [L] RewriteCond % REQUEST_FILENAME !-f RewriteCond % REQUEST_FILENAME !-d RewriteRule . /index.php [L] # END WordPress RewriteEngine on ###LSCACHE START PLUGIN - Do not edit the contents of this block!### RewriteEngine on CacheLookup Public on ###LSCACHE START RESOURCE### RewriteRule wp-content/. /[^/] (loader|fonts| .css| .js) .php - [E=cache-control:max-age=3600] ###LSCACHE END RESOURCE### ###LSCACHE START FAVICON### RewriteRule favicon .ico$ - [E=cache-control:max-age=86400] ###LSCACHE END FAVICON### ###LSCACHE END PLUGIN - Do not edit the contents of this block!### RewriteEngine on ###LSCACHE START RESOURCE### RewriteRule wp-content/. /(loader|fonts) .php - [E=cache-control:max-age=3600] ###LSCACHE END RESOURCE### ###LSCACHE START FAVICON### RewriteRule favicon .ico$ - [E=cache-control:max-age=86400] ###LSCACHE END FAVICON### Expand Hi @nceebob, its an issue with social-warfare. If you follow my previous reply in this post it will be fixed. You still get that error because your js is cached by your browser. You need to refresh your page, or directly visit http://yourdomain.com/wp-content/plugins/litespeed-cache/admin/js/litespeed-cache-admin.js?ver=1.0.14.1 to make this js file refresh. Thanks for the feedback. The issue appears to to be rather a combination of browser cache-ing ( I was using Chrome, and now changed to Firefox) and the line 51 on /wp-content/plugins/litespeed-cache/admin/js/litespeed-cache-admin.js when active. Having switch to Firefox and commenting out the line 51 in the above LS javascript file, I am now able to save my LS plugins Advanced Settings with the click of the save changes successfully. Have altered no settings at all in my social-warfare plugins settings. Do you still suppose that could pose issues with LS by and by? @nceebob Its a compatibility issue for LS. We fixed it in next lswpcache release. Okay. Thanks.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference