Thread

So having some issues after moving my copy of EE from one server to another…

I just moved a 1.66 install from one server to another server following the various wiki entries here on the topic and items found at eedeveloper. All seems fine throughout the new instance of it, changed all the paths and tried to verify all CHMOD settings for files and directories. All seems to be owkring. And weblog names all show up on the CP Home screen and even in the db all the actual entries for a weblog are there…

However, when I click EDIT tab, I get a blank empty screen, and shows nothing :-(

... and when I click PUBLISH tab or any of the weblog titles under it, I get a blank empty screen, and shows nothing :-(

Interestingly, when I found the area to create a new weblog, it was successfully created, but when I try to access it from the PUBLISH tab, the screen comes up empty just like the weblogs that were originally in this moved version of EE.

Anyone have any ideas what am I missing here?

thanks for your help in advance…

Best regards,

David

In researching… I noticed the url for the PUBLISH tab on my old server is:

and the new server the url for PUBLISH is:

Is the S value in querystring part of cookie or sessionid? or does it tie back to unique id or something in the database? I tried using the S value from original server with new server and it just kicks me back to the CP login screen…

The published weblogs, so all the web entries that I had on the original server, when I go out to the new server at the published url… I see all the weblogs etc. So, that is good news…

So, for some reason, it still remains that I cannot see old or newly created weblogs in PUBLISH and can’t see the entries in EDIT…

Help :-0

More digging…

PHP version on old server is: PHP Version 5.2.14

PHP version on new server is: PHP Version 5.1.6

So no one has ever had issues moving an instance of EE pre 2.0 to another server like this?

thanks 😊

David

David,

The session ID in the URL should not make any difference.

Did you clear out your cache folder when moving the site?
If not FTP into it and delete all the folders inside of it except index.html

The blank page is usually indicates a suppressed error. So lets get you set-up with some error reporting and see if we can see what the issue is.

Let us know what turns up.

Hi John,

Thanks for your help. I cleared the cache, but not initially. So the old database came over with all the cache data intact. Once I realize I hadn’t then I deleted everything in there except the folders and the index, but everything in the folders was wiped out.

I tried turning error reporting on - but it seemed like it didn’t handle errors in the /admin.php or in the CP, just on the front-end or index.php… so do I have to perform the action described in the link above you listed that states:

“Additional Note: If you cannot access the Control Panel due to errors on the site or templates not rendering, you can change the system/config.php $conf[‘debug’] value to 2 temporarily which will show PHP errors to everyone.  Remember to change this back to 0 or 1 when you’ve resolved your issues.”

Or how do I get the CP to not suppress errors?

Thanks looking forward to seeing what the php errors state within the CP… will report back…

best regards,

David

Very good, please keep us in the loop. We’ll be here.

I need error reporting for php to show in the .admin screen, none of the above have shown anything than what I was seeing in the CP, everything normal except the Publish and Edit tabs not working as normal…

How do I get php errors to show while in the .admin and CP area?

Nevermind just changed my php.ini to show errors ... and 😊 success:

php error when I click any choice under PUBLISH tab except >>Edit Weblogs gives me:

Parse error: syntax error, unexpected $end in /var/www/vhosts/{domain}/httpdocs/eecms/{systemfolder}/cp/cp.publish.php on line 11777

and when I click edit tab, the same:

Parse error: syntax error, unexpected $end in /var/www/vhosts/{domain}/httpdocs/eecms/{systemfolder}/cp/cp.publish.php on line 11777

LOL

somehow without giving me a transfer error or anything…

whenever I ftp’ed the files over to the new server…

at line 11777 the cp.publish.php file, it just ends right at:

AMP.‘keywords=’.$IN->GBL(‘keywords’); 

so I re-uploaded the full file (383k vs. the version that was there 242k)

and now everything works!

😊 DUH

Thanks for learning how to use php error reporting…!

It would be good to know how to really get .admin to see php errors without me going into the php.ini file to do so, none of the info provided got me to see any php errors in the CP…

thanks for the great support though -

David

Very glad to see you’re all set. Please post again as needed.