ikarusdi

ok thanks

Ok, thanks for your support.

Yes it sounds strange, in my thought (just my guess) the error happened because I login and purge the sub-site by super admin account (I have to do that to styling the sub-site pages and interface because the sub-site admin (actually not admin, but custom user role is assigned) is prohibited to do such actions).

For your requests:
1. yes it is OFF I never change it (main site).
2. I won’t do that for now because i’m afraid will get another problems, because it is live website to users. Will applied it in future.

After deep investigation over and over again,

The problem is caused after purging over sub-site account, this action will ruin the website (design/style/interface) setting of the main site and sub-site that already applied (in this case: the top bar (all pages) setting changed and the homepage css/js not applied).

I can solve this problem after deep testing by accessing super admin > Toolbox and clicking button of the Empty Entire Cache: Clears all cache entries related to this site, including other web applications. This action should only be used if things are cached incorrectly.

By this method the homepage shows as should be (the error message on console gone) BUT some interface style/structure I already applied before (damage) can’t be restored. I have to styling it again on the theme setting.

So just BE CAREFUL by purging over sub-site on multi-site.

all ready applied and still no luck, and this case only happen to homepage.

just curious, why under wp-content/litespeed there is no cssjs folder and css/js and files in it?

• This reply was modified 4 years, 8 months ago by ikarusdi.
• This reply was modified 4 years, 8 months ago by ikarusdi.

All ready check and apply the https:// since the beginning of investigation as well as in general setting, wp-config, wp_options, and wp_sitemeta, but the problem is persist.

All ready cleaning up the LSCACHE code in .httacess, delete the folder litespeed under wp-content, cleaning up everything the database setting of litespeed and bla bla bla, then reinstall the plugin but still, the problem is persist.