Composr 10.0.20 released issue

Yesterday I upgraded afansite.net to Composr 10.0.20 from Composr 10.0.19 via softaculous.  Since upgrading I'm unable to view sections of the site correctly unless I do it via safe mode.

The following sections not loading correctly:
https://afansite.net/cms/cms.htm
https://afansite.net/adminzone/start.htm

Anyone else having this issue and how can I correct this ?
Please let me know.  Thanks in advance.

- Mary D

Hi,

Can you tell us more about the issue?
We won't be able to see without having a login.

I don't believe there are any reports of this breaking. The one major issue some people have had is CSS and JS not loading, due to an Apache bug we accidentally triggered.

I do believe the issue was related to the CSS and JS not loading based on the screen shot provided at: 
0003712: theme does not load after login - Composr CMS feature tracker

I ended up doing a restore from a backup I did before applying the latest update.
I did try the solution mention in the bug tracker link listed above by removing the .htaccess file from the templates_cached folder of the default theme.  However, when I did that the site won't load period.  So I login to Cpanel and did the restore.
The webserver that the web host uses is LiteSpeed Web Server. 

surfsupnet said

I do believe the issue was related to the CSS and JS not loading based on the screen shot provided at: 
0003712: theme does not load after login - Composr CMS feature tracker

I ended up doing a restore from a backup I did before applying the latest update.
I did try the solution mention in the bug tracker link listed above by removing the .htaccess file from the templates_cached folder of the default theme.  However, when I did that the site won't load period.  So I login to Cpanel and did the restore.
The webserver that the web host uses is LiteSpeed Web Server. 

From “Post #5211”, 21st Feb 2019

Ok. Sorry for the troubles, and thank you for explaining. Removing the .htaccess should not have caused an issue, so I can't explain that. However I can certainly see why the very Apache-specific .htaccess code might not work on LiteSpeed. LiteSpeed emulates Apache, but not perfectly.
The next patch release will not have these rules, people will need to enable them by hand if they want them.

No problem.  
This is why I make backups of the site before applying a patch.  T

Thanks Chris for looking into this issue.  

Next time I have a problem, I'll just screen cap or video record to document it better.