Shape 5

Wordpress Club Themes => Life Journey - Club => : dmsolution April 20, 2012, 05:30:52 AM



: Theme configuration results in blank page
: dmsolution April 20, 2012, 05:30:52 AM
Dear support,
we installed the life journey template in one of our wordpress blogs and tried to get it working but the configuration can not be accessed. When we try to access the Shape5 Theme Options we only have a blank page with "save" and "reset" buttons.

We also tried to use the Site Shaper Demo installation where also the backend configuration is blank.

Any ideas how to solve this problem?

best regards
Danijel


: Re: Theme configuration results in blank page
: Tristan Rineer April 20, 2012, 11:02:39 AM
Please run a server check by extracting the php file from This Zip (http://goo.gl/MQ5eF), placing it (anywhere) on your server, and navigating to it in the browser.

There is a possibility that your server may not support some of the PHP functions necessary for the Vertex Admin to load properly.  If that is the case, you will need to ask your host to enable those capabilities.


: Re: Theme configuration results in blank page
: dmsolution April 21, 2012, 05:00:59 AM
Hello Tristan,
thanks for your fast response. I uploaded the .php file and tested it, everything great so far. "simplexml_load_file" and "simplexml_load_string" are both supported. Any other ideas?

best regards
Danijel


: Re: Theme configuration results in blank page
: dmsolution April 21, 2012, 06:03:33 AM
We tried some other wordpress themes and got them all working until the theme from december 2011. The newer themes from january 2012 are not working. Maybe this information helps finding the issue.


: Re: Theme configuration results in blank page
: Tristan Rineer April 23, 2012, 09:48:13 AM
Thanks for the additional information.  I'll have to take a way at the admin for those newer themes and try to figure out exactly what changes were made that would prevent it from loading for you.

If you can PM login & ftp information, it'll be a lot easier for me to figure it out for you; working on the server that's having the problem is a lot easier than trying to duplicate the problem on a server that doesn't have it.