This is the second site I have built and received a “500 internal server error” after adding a new section, category and article. Is there something that I need to be careful of when adding sections, catogories and articles to avoid receiving this error. I have been using joomla for a long time and never had this problem before. I have used the ja purity template [never a problem] but with ja opal and ja tube I have experienced this problem to the point that I had to start the sites over from scratch. What happens is: After I add a new section, then a new category and try to create an article or connect to article when creating a menu…. nothing shows up in the category drop down box. Even though when I go to category management I can see the category I created. Anyway, I am baffled. Probably something I am doing wrong, or something I don’t know. Can anyone help?
TomC
Moderator
It sounds like it may be a permissions issue with your current server/directory structure.
Are you sure that your folders/files are set at 755/644 respectively?
When is the last time you checked to make sure all of your template components were up to date (via Extension Manager)?
Thank you for responding. I just downloaded this template so I didn’t think I needed to check for updates. As far as the folder/files being set at 755/644 respectively, forgive my ignorance, never heard of that…. but I will check it out. Thanks again!:)
TomC
Moderator
<em>@alambtech 290780 wrote:</em><blockquote>Thank you for responding. I just downloaded this template so I didn’t think I needed to check for updates. As far as the folder/files being set at 755/644 respectively, forgive my ignorance, never heard of that…. but I will check it out. Thanks again!:)</blockquote>
You can ask your webhost provider to check this for you . . . they’re usually good about doing this for their clients.
1 user says Thank You to TomC for this useful post
Yep. Changing permissions resolved the problem 🙂 Thx.
TomC
Moderator
<em>@powietkien 291657 wrote:</em><blockquote>Yep. Changing permissions resolved the problem 🙂 Thx.</blockquote>
Glad to have helped provide some guidance on this issue.
All the best with your continued site development.
This topic contains 6 replies, has 3 voices, and was last updated by TomC 12 years, 10 months ago.
We moved to new unified forum. Please post all new support queries in our New Forum
