500 Internal server error: /theme/[themename]/styles.php

500 Internal server error: /theme/[themename]/styles.php

by Jamie Lynn O'marr -
Number of replies: 5

I am having some trouble using anything but a custom theme on my moodle installation (v 1.9).  The standard themes work just fine, but whenever I select any kind of theme with a nice menubar on the top it turns into instant crapola!  The menubar doesn't come up at all, which leaves a text-list at the top of the page.  None of the images for the theme render either.  This is pretty consistent across all the non-standard themes I've tried.  

Firebug claims I'm getting an internal server error 500 for the styles.php file of every theme I have this problem with.  I'm not sure how to resolve this.  

I apologize if this has already been discussed.  I did use the search function and didn't find anything helpful.  Feel free to link me to past resolutions of this problem.

Thanks,

Jamie Lynn 

Average of ratings: -
In reply to Jamie Lynn O'marr

Re: 500 Internal server error: /theme/[themename]/styles.php

by Mary Evans -

Hi Jamie,

Have you just started to have this problem, or has this always been the case since you started to use Moodle?

How many 'non-standard' themes do you have in your theme directory?

Can you list these themes here for me?

Also, how did you upload theme to the server, I am assuming you are using a host server?

Thanks

Mary

Average of ratings: -
In reply to Mary Evans

Re: 500 Internal server error: /theme/[themename]/styles.php

by Jamie Lynn O'marr -

I've just started to use moodle, so this has always been the case since I installed it last friday.  This is the first time I am configuring moodle.

I have a great number of non-standard themes in my directory, mostly because I've been uploading and trying different themes to see if I can get one to work.  If it is helpful, I can remove all but one of them.  Here is the current list (and I am aware a few of them are moodle 2.0 themes; it took me a little while to realize that my webhost installed moodle 1.9 rather than 2.0)

The list:

MemMed_Main_Theme

aardvark(2.0 theme, my bad)

aardvark-stc

aardvark-stf

aardvark_pro

aardvark_pro 2

afterburner

beaux

beaux_purple

college_red (the menu in this one sort-of renders, but the text is invisible)

edulabs-green

gekko

gekko_twopointoh (moodle 2.0 theme, again, my bad)

ingenuous

melbourne

mymobile (moodle 2.0 theme, did not try this one)

newburycollege

zebra

 

I am using a host server (1and1) AND their 1-click install of moodle.  I am not happy with that, but I could not install it myself because I don't have access to anything outside htdocs to securely create the moodledata folder, and I couldn't get that part of the installation sad

In any case, I uploaded the theme files directly to the theme directory via ftp.  I assumed that when they showed up in my theme selector I had done so correctly, but perhaps I missed an obvious step (edit yadda yadda line in such and such a config file)?

I am in contact with my web server help desk about this error, but I spent an hour on the phone trying to explain what a debug console was, so it's not looking good.  I really do appreciate your time.

Jamie Lynn

over.

Average of ratings: -
In reply to Mary Evans

Re: 500 Internal server error: /theme/[themename]/styles.php

by Jamie Lynn O'marr -

Also, here is the page:  http://moodle.dailylibertine.com/

 

You can check your own debugging console to duplicate the error and see if I've done something idiotic.  You can also see how fubared the menu is.

 

Jamie Lynn

over.

Average of ratings: -
In reply to Jamie Lynn O'marr

Re: 500 Internal server error: /theme/[themename]/styles.php

by Mary Evans -

Hi,

It looks like the style.php is working in the theme.

Have you tried to install the themes using your File Manager in the cPanel. I am assuming 1and1 use cPanel. 

Mary

 

 

Average of ratings: -
In reply to Jamie Lynn O'marr

Re: 500 Internal server error: /theme/[themename]/styles.php

by Lei Zhang -

Jamie, 

Have a look this wiki page:

http://docs.moodle.org/20/en/Errors_FAQ#Error:_.22500:Internal_Server_Error.22

or my copy and paste version:wink

There are several possible causes for this error:

1. Syntax error: There is a syntax error in your .htaccess or httpd.conf files. The way in which directives are written differs depending on which file you are using. You can test for configuration errors in your Apache files using the command:

#apachectl configtest

2. PHPsuexec: Your server does not support .htaccess files, especially if it is running PHPsuexec, which is an Apache module used for increasing the security of a site on a hosted system. In this situation:

- you may also see a 403: Forbidden error.

- the webserver executes under your own username and all files have a maximum permissions level of 755. Check that this is set for your Moodle directory in your control panel or (if you have access to the shell) use this command:

#chmod -R 755 moodle

- use a PHP.INI file instead of a .htaccess in the directory where the Moodle PHP script is being executed. For example: if you are receiving a memory exhausted error when your server is executing the file moodle/admin/cron.php, use a PHP.INI file to change your memory_limit and copy it to the moodle/admin directory. Remember that for PHP4, PHP.INI files are per-directory, so you'll need to copy it to each sub-directory. If you are using PHP5 or higher on a shared host, check with your host on whether they support custom PHP.INI files, and how to create them. The syntax used in a PHP.INI file is different from a .htaccess file and you need to take out php_value/php_flag at the beginning of the line and use an equals sign to assign a value, e.g.

php_value memory_limit 128M <-- .htaccess
memory_limit = 128M         <-- php.ini equivalent

3. Incompatible directive: You may have a directive in your .htaccess or httpd.conf files which are not compatible with your web server version. Check your webserver documentation.

Average of ratings: -