Franklin
Member
Posted 5 months ago #
Hey guys, s here the issue:
- I get 500 Internal Server Error
- Using latest WordPress version
- PHP 5
Things checked:
- Theme was working but stopped.
- .htaccess not the problem
- Permalinks.
- Reset default theme (works good)
- Only shows error with theme in question
- Log shows nothing
- Theme website doe snot respond
Link to site: http://latinfranchises.com/
Them I am using: http://www.paddsolutions.com/wordpress-theme-thalliumity/
Thanks guys. I appreciate it very much.
[No bumping. If it's that urgent, consider hiring someone.]
Robert.Vidrine
Member
Posted 5 months ago #
You may want to check the directory and file permissions on the theme that's not working. Many hosts use something called suPHP or suexec or similar, which makes it easier to divide a server into several distinct accounts, but also makes it very unforgiving for file & folder permissions which are too lenient.
Usually, files can be set no more loosely than 644 (in Unix shorthand) or Read/Write for the owner, Read for the group, and Read for everyone else. Directories should generally be set to 755 or lower, or Read/Write/Execute for the owner, Read/Execute for the group, and Read/Execute for everyone else.
See Changing File Permissions at the Codex for an explanation of file permissions.
See Hardening WordPress for a couple of lines of code to set all permissions in your web space to these permissions.
Franklin
Member
Posted 5 months ago #
Robert, thanks for the reply.
I have checked that also. All things that usually come to mind when this happens I have tried. I am convinced it's some conflict between the the host and the theme, since all other themes work fine, and this particular theme works fine on other hosts too.
I mean I just can't figure out what it is.
Any other ideas?
Robert.Vidrine
Member
Posted 5 months ago #
Hmm, I don't know...
Usually when I've seen 500 Internal Server, it's a permissions thing.
What changed between working and not working?
Franklin
Member
Posted 5 months ago #
Right, it's the first time I see it. Last thing I did when it was working was to add a language selector script in the header. I have taken it off. Couldn't have been that since it did not break it instantly, as it usually happens.
First it appeared all messed up as in - when you mess with PHP, or forget to close some tags - but that was not the case. Then just stopped working and gave me the error.
