Lidstone,
Unfortunately this is not enough information to provide any useful feedback.
I would guess it is one of two things: 1) your themes directory is not writeable by the web server (although the error should be different); or 2) PHP does not have enough memory to run the plugin.
If you could find the specific error you are receiving I may be able to help further.
I’m working with lidstone – here’s the error he is getting:
[Mon Aug 11 20:44:36 2014] [error] [client 98.231.68.113] Premature end of script headers: tools.php, referer: http://192.163.239.51/~sguard/wp-admin/tools.php?page=chld_thm_cfg_menu
This is the error you are getting from that 500 internal server error.
This is a new wordpress installation, with no plugins running. The themes directory is in fact writeable, and PHP has adequate memory to run the plugin. The theme is Divi. I am on the phone with Bluehost and so far we have been unable to sort out the problem. We have it working on 2 other sites with the Divi theme. Very strange. We also got the following error:
[11-Aug-2014 21:25:09 UTC] PHP Fatal error: require_once(): Failed opening required ‘/home/sguard/public_html/wp-content/themes/Divi/et-pagebuilder//layouts/layouts.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/sguard/public_html/wp-content/themes/Divi/et-pagebuilder/et-pagebuilder.php on line 7
I would use process of elimination.
Start by activating one of the core themes (Twenty Twelve, etc.) and see if the problem occurs.
This will isolate it to a specific theme. If not theme-specific, check wp-config.php for any questionable settings. The fact that it is not finding includes tells me either a file is missing or there is a permission issue somewhere in the wp directory.
If it is the Divi theme, go into the editor and comment out the actions/filters to isolate a particular user function.
Update: specifically functions.php
We did that. It DOES work with twenty fourteen, but lidstone also has it installed with Divi on another site and it works fine. I am wondering if there is an issue with our not having a domain name pointing to the nameservers, and maybe there’s an issue with iP address?
I have seen a lot of these errors showing up on sites using UserDir directives. I haven’t had a chance to look into the WP filesystem classes but all signs point to that.
In any case, I don’t believe this is an issue with CTC so I am closing this ticket.
Feel free to post any updates.
-jf
