Error Composr
Posted
#4062
(In Topic #815)
Error when you install a site
After installing the site, I see this picture: the login page is displayed correctly, as well as the main page of the admin panel. And all other pages are displayed crooked. Screens are attached:
https://gyazo.com/c7320252084f1e9ccc56cbfecb397aea

https://gyazo.com/b51252da12cef0a038d7d4cae4a0e4cb

https://gyazo.com/3c44995d4bf15b3d4f4c9525a1647cba

https://gyazo.com/6afa67ae5a72df5f755528b6ec160b1f
Posted
This implies CSS is not loading. Are there any errors in your browser's error console?
Did you set 777 permissions on themes/admin/templates_cached/EN? (assuming your server needs chmodding done)
Posted
Everything turned out to be much easier)) On the hosting side, debugging mode was enabled ) Thank you very much! The topic is closed.
Posted
If we can stop it causing an issue, we probably will.
My suspicion is it was injecting code into the scripts we initially use to generate CSS dynamically, or changing the mime-type to HTML.
Posted
Posted
So it looks like the host is altering mime types.
If you'd like me to take a look, please email access details to [email protected].
Posted
as we have seen, Your web page again does not display correctly.
Want to clarify, we are not web developers and customizers CMS and self-made sites, unfortunately, on our part, we can no longer provide any assistance in view of the lack of knowledge about CMS Composr.
Please contact the developers of this CMS, or specialized forums to clarify information about your situation and the necessary requirements for the CMS.
With respect, bla,bla, bla..
I created a subdomain, installed Composer there, which was installed correctly. then demolished the subdomain and installed Composer. The installation was successful. However, after the transfer of the site to the hosting, there was a problem in the form of display admin panel.
Access data is sent to the E-mail.
Posted
Posted
This is now resolved.
It was a very strange issue.
The problem was in the .htaccess file, which is based on our default.
For some reason on this server FilesMatch and SetEnvIf and SetEnvIfNoCase were not working. These were all used to apply rules for certain URLs.
However, our rewrite rules were working.
And, the server did it's own gzip compression.
The result was the CSS and JavaScript being double-gzipped, because our rules to prevent that were not activated.
I think somehow the Apache server is using different file URLs via some kind of internal-rerouting, or some kind of permission is there (perhaps AllowOverride FileInfo, but the Apache documentation says that this should stop RewriteRule working too and that does work).
Anyway, I have tweaked the default .htaccess so that our own gzipping will only happen when FilesMatch is working.
2 guests and 0 members have recently viewed this.
