polynamaude
commented
6 years ago After reading over what you wrote, I'd add that the system itself doesn't use a direct filesystem references to deliver the css files (there's no direct link between a requested URL and it's position in filesystem hierarchy). For sure some folder are quite similar in name as the requested url but it's not directly served from the filesystem.
For example when the file color.css is requested, the system will do a "loopback" request using curl, compress, mimify and process the file as configured in the first place. Afterward on following request for the same file you'll get the cached version (what gives you a faster delivery). Some CMS like for example Joomla will do the same but use either APCu or other type of framework. Ph7CMS use s "home made" system.
There's no such thing as a "hard coded" theme, what you are seeing is basicly a theme that get served without the styling done and only bare html (no CSS files). Like I said in my first answer, start by disabling all the caching options, minify and such. Look at your logs for some 401 error also.
Afterward it will be easier to do some troubleshooting. Also, try to limit the number of opened issue as there's no use to making many when there's only one problem. It only make management harsher. I'm saying it here but it's something that you'll get wherever you do such action. Some people won't tell you but simply delete your actions at the end.
Foxtrek64
pH-7
KarlBaumann
lock[bot]
After jumping through several hoops (#187) to even get the CMS installed, it seems it does not like the theming engine. Pages render as if the style sheets for the page could not be found (and when you look in the console, this is exactly what is happening.
The stylesheet which is supposed to be at
/assets/css/color.cssdoes not exist (more accurately, the /assets/ directory does not exist). I've ensured that permissions are set correctly and that this is not an issue with it not being able to create the folder.I have tried changing the theme to see if this would kick the system into working properly, but the unthemed "theme" seems to prevail regardless of the configuration in the ACP.
Surprisingly, this bug is affecting the ACP as well, which I find interesting because in most other CMS the ACP does not use the theming system, rather it has its own hard-coded theme (see WoltLab, WordPress, etc.).
Any help in getting this working is appreciated. Besides the changes made to my .htaccess file (#187) and changes made in the ACP, this is an unmodified build as downloaded from SourceForge.