Not sure how to describe this error as Im new to the web design world but the site appears to lack a theme

 

Accepted answer

Ah, interesting.

I'd suggest to turn aggregation and compression of the asset files (css/js) off on /admin/config/development/performance and see if that fixes it.

If it does, then it's something with gzip on that server. Then please contact your hosting service providers for help.

Again, please inspect the status page for warnings (/admin/reports/status).

Most helpful answers

I can't give a direct solution to the problem, but here is information that can help the experts in the forum:

The Backdrop is installed in a subdirectory of a real domain that is hosted in the United States, most likely on shared hosting.

https://mirroryou.net/me/

In the main directory there is a main site

https://mirroryou.net - built with OpenCart and seems to work fine.

Backdrop styles are located in a folder

https://mirroryou.net/me/files/css/

but when analyzing the code with Firebug you can see for each style not a css content but the following text:

<! DOCTYPE HTML PUBLIC "- // IETF // DTD HTML 2.0 // EN">
<html> <head>
<title> 500 Internal Server Error </title>
</head> <body>
<h1> Internal Server Error </h1>
<p> The server encountered an internal error or
misconfiguration and was unable to complete
your request. </p>
<p> Please contact the server administrator,
 and inform them of the time the error occurred,
and anything you might have done that may have
caused the error. </p>
<p> More information about this error may be available
in the server error log. </p>
</body> </html>

The same text is read when checking the script files in the head element.

Ooops... That's what Backdrop looks like when no css files at all could get loaded.

First of all: check the permissions of the /files directory - it must be writable for your webserver user.

Is this "real" webhosting or a local development instance?

If you go to /admin/reports/status - are there any warnings?

What about /admin/reports/dblog? Are there any warnings?

Can you post your settings from /admin/config/media/file-system?

Can you post your settings from /admin/config/development/performance?

Comments

indigoxela's picture

Ooops... That's what Backdrop looks like when no css files at all could get loaded.

First of all: check the permissions of the /files directory - it must be writable for your webserver user.

Is this "real" webhosting or a local development instance?

If you go to /admin/reports/status - are there any warnings?

What about /admin/reports/dblog? Are there any warnings?

Can you post your settings from /admin/config/media/file-system?

Can you post your settings from /admin/config/development/performance?

I can't give a direct solution to the problem, but here is information that can help the experts in the forum:

The Backdrop is installed in a subdirectory of a real domain that is hosted in the United States, most likely on shared hosting.

https://mirroryou.net/me/

In the main directory there is a main site

https://mirroryou.net - built with OpenCart and seems to work fine.

Backdrop styles are located in a folder

https://mirroryou.net/me/files/css/

but when analyzing the code with Firebug you can see for each style not a css content but the following text:

<! DOCTYPE HTML PUBLIC "- // IETF // DTD HTML 2.0 // EN">
<html> <head>
<title> 500 Internal Server Error </title>
</head> <body>
<h1> Internal Server Error </h1>
<p> The server encountered an internal error or
misconfiguration and was unable to complete
your request. </p>
<p> Please contact the server administrator,
 and inform them of the time the error occurred,
and anything you might have done that may have
caused the error. </p>
<p> More information about this error may be available
in the server error log. </p>
</body> </html>

The same text is read when checking the script files in the head element.

indigoxela's picture

Ah, interesting.

I'd suggest to turn aggregation and compression of the asset files (css/js) off on /admin/config/development/performance and see if that fixes it.

If it does, then it's something with gzip on that server. Then please contact your hosting service providers for help.

Again, please inspect the status page for warnings (/admin/reports/status).

Hi Thanks Guys.. Well the only warning there is in /admin/reports/status is trusted host warning that i should get to but.. turning the css/js off did the trick..

I appreciate the thorough and speedy responses from the community. its warming.  well, i hope not to be back to learn anything else el oh el cus that infers more breakage but if not then i cant come back as a contributing member of the community.. ill stay learnable tho and with that said ill be back with more issues. kudos