500 Internal Server Error with Page Types Defaults - version 5.6.3.1

Permalink
Greetings,
This is a brand new install (actually a complete reinstall due to same error) of v. 5.6.3.1

On previous install I discovered that trying to access the Defaults of any of the Page Types would produce a 500 Internal Server Error (if Pretty URLs was off) or a Page Not Found (with Pretty URLs enabled).

Funny thing is my cpanel error logs shows no errors. Now for the really strange part. Since trying to access Defaults was causing an internal server error - I didn't want to take a chance that the entire install might be corrupted - so I completely uninstalled concrete and did a fresh install using a different DB, etc.

The very first thing I tested was the Page Types > Defaults and it worked - all was well. So, I added some new pages to the site, added some content on home page and went back to setup the defaults on a page type - no go - same error.

I simply can't edit the Defaults.
When I click on Defaults for a page type - it is trying to get tohttp://highdeserthomesteading.com/index.php?cID=125&mode=edit...

Obviously the cID= number changes for each page type. If I remove the &mode=edit from the URL I still get the same error. Those pages must exist because I can use them?

Since cpanel isn't showing any errors I'm kind of lost here. BTW, this install is on the same server that is successfully running numerous other concrete sites.

Any help would be much appreciated.

ssnetinc
 
exchangecore replied on at Permalink Reply
exchangecore
So with your new page type, are you able to just simply add a page with that type without trying to set the defaults first?
ssnetinc replied on at Permalink Reply
ssnetinc
Yea. The server error occurs with ALL page types (the default ones that concrete installs and ones the theme installed) - it even occurs on a new page type that I created from scratch.

Yet, I can use any of the page types when I create a new page or via the Design function on an existing page.
ssnetinc replied on at Permalink Reply
ssnetinc
SOLVED! FIXED!

Believe it or not, this problem was a bug in the theme I had purchased. I had copied the theme developer on the issue on the outside chance it had something to do with their theme.

It did. They fixed and updated theme - everything works now.