Structure: CP & Site go blank after site_index removal
Development and Programming
While trying to remove index.php, I removed the site index g (Admin > System Preferences > General Configuration > Name of your site’s index page) before I had it working. The site went blank as well as the CP. I turned on errors and I still get blank screen for CP and below for the site. Is there a way to manually reenter the site_index? This could be the reason the structure ext is not working as it was working just fine before this. I noticed in the path.php file there is a site_index variable as well as in the DB in the exp_sites table in the serialized site_system_preferences field. I added index.php to both of these place but no luck. Any suggestions?
Site Error: Parse error: syntax error, unexpected ‘&’, expecting T_VARIABLE or ‘$’ in [PATH_TO_ROOT]/html/cec/content_cec/modules/structure/mod.structure.php on line 1641
Moved to Modules by Moderator
Welcome to the ExpressionEngine forums, bozzly.
We don’t provide direct support to third party addons such as Structure. I’ll need to move this over to the Modules forum.
@bozzly sorry just seeing this. Did you get ti figured out?
Hmmm…I just deployed a site from our dev environment (where it’s working fine) to mediatemple and I’m getting the same thing all of a sudden. Not sure how to address this.
The server log files are riddled with the following:
[client 99.140.198.104] PHP Parse error: parse error, unexpected ‘&’, expecting T_VARIABLE or ‘$’ in /var/www/vhosts/domain.name.was.here/httpdocs/system/modules/structure/mod.structure.php on line 1641
Travis, if you have any ideas, I’m all ears. Not sure how to get out of this one.
@openmotive You’re getting something blank? or this happened after removing index.php? Please confirm the steps that got you there. Thanks!
Sorry about that.
We had already removed index.php using .htaccess. In fact, having a removed index.php is part of our internal “core” (as is Structure) so it isn’t a step we really had to go through as it is part of our project setup. We deploy this core rather frequently both locally and on live servers and this is the first time I’ve seen this symptom.
This particular site works just fine on our development servers (in the office), and all previous sites we’ve built using the same “core” and same methods are working fine on their development, and live servers.
So, the steps we went through after confirming that everything is working bug-free in our development environment:
1) We migrated the database to the staging server 2) Deployed the current version of /trunk to the staging server 3) Edited config.php on the staging server to point to the database with the correct credentials
Site itself yields blank page. domain/system yielded a login. Blank page received after login.
Thanks!
@openmotive Sounds like there needs to be some investigation into what’s different about this particular environment than the other ones and especially your development server. Have you confirmed all the same settings, PHP version, memory limits, etc?
It looks to be the same. We setup all of our servers using the same template.
I’m going to setup an environment on our production server and see how it goes there. I’ll report back here after I try.
Woohoo!
Worked like a charm on our other production server. Not sure why/how since there’s not much different between the two servers and both are hosted by MediaTemple.
We’ll be moving our old staging server to a new one soon anyways so since it works on Production, I’m not going to sweat about it. Thanks Travis!