Thread

I just tried upgrading to EE2 but it didn’t work because my server’s php is out of date. So I am trying to go back to the EE1.6.9 I was trying to replace. I uploaded the entire system directory & contents from my backup copy (backed up just before my attempt to upgrade). Now the web site pages displayed by EE are blank.

I have access to the cp. But when I try to view a template from Template Management, I get the message: “Some components appear to be missing from your ExpressionEngine installation.”

Is there a way to determine what is missing? Do I need to reinstall EE1.6.9 with the original installer? If I do, how to I make sure that I don’t lose the templates I have made?

Hi Stoelting,

After you rolled back to the EE 1.x files, did you also restore your EE 1.x database? A database upgraded to EE 2.x won’t work with 1.x.

I was never able to install EE2 because my server has php4.3 so the install wizard never functioned. That’s why I tried to go back to EE1.6.9. My server has MySQL v5.x which is compatible with EE2. Is it possible that the database got altered, even though the php4.3 is not compatible with EE2 and the install wizard?

Ah, I see. In that case the database should be intact. Can you try enabling error reporting? Typically a blank page indicates the server is suppressing an error.

I have finally enabled error reporting, after getting PHP upgraded. Whan I try to access a page in EE 1.6.9, here are the error reports:

Warning: require_once(/var/www/html/subdirectory1/system/codeigniter/system/core/CodeIgniter.php) [function.require-once]: failed to open stream: No such file or directory in /var/www/html/subdirectory1/index.php on line 175

Fatal error: require_once() [function.require]: Failed opening required '/var/www/html/subdirectory1/system/codeigniter/system/core/CodeIgniter.php' (include_path='.:/usr/share/pear:/usr/share/php') in /var/www/html/subdirectory1/index.php on line 175

Hi Stoelting,

It looks like you may have forgotten to restore your root index.php to the EE 1.x version, and the 2.x version is still there. Does that help?

That was it. Thank you. I got the old and new index.php files mixed up.

I’m ready to try again to install the EE2 upgrade.

Hi Stoelting,

Excellent. Make sure that you have complete file and DB backups before you do anything else. Have you made sure that all of your site is working properly? If you have then go ahead and try and upgrade and let us know how you get on.

Cheers

Greg

I did the upgrade and the wizard reported it was successful. The front end works except images don’t show up in entries. They do show in static page content. From viewing the page source, it shows this typical image url:

The image source url “domain.org/directory1/images/uploads/imagename_thumb.jpg border=“1” name=“image”” alt=“image”} width=“54” height=“58”
I don’t understand where the lone } after alt=“image” comes from. (I took out the http… part of the url because when I put the full url within code tags, it stripped out the stray } bracket.) Except for that bracket, the url is the correct address for the image. I did not change anything in this template, which worked find in EE1.6.9. Could it be related to the issues below?

There are also problems with the control panel.

I tried to delete a member. From the confirmation page, Delete produced this message:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 58368 bytes) in
 /var/www/html/directory1/system/expressionengine/modules/forum/mod.forum_core.php on line 11553

When I clicked submit to publish a new entry,  I get a similar error message:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 55 bytes) in
/var/www/html/directory1/system/codeigniter/system/database/drivers/mysql/mysql_result.php on line 147

How do I fix this?

Hi Stoelting,

Okay, there are a couple of things here. The first is that you only have 8MB of memory allocated to PHP. EE 2.x needs at least 16MB but I would recommend 32MB or even 64MB. Please contact your host and ask them to upgrade the memory allocated to PHP. That should fix the CP error you are seeing. For the image tag issues, were you using any 3rd party addons to manipulate images in your 1.7 install?

Cheers

Greg

I did not use any 3rd party image manipulation add-ons. I just used the standard upload button on the publish page.

Note that I changed my previous post to show the stray bracket } in the url. When I put the url in code tags, it stripped out the }.

Hi Robert,

Did you manage to deal with the issue of PHP memory?  With regards to the bracket in the source code, can you please go to Admin > Content > File Upload Preferences for your images directory and confirm that in the “Image Properties” a stray bracket doesn’t appear after the alt tag?

Cheers

Greg

I just got the memory issue resolved. The server host tech support changed a setting in a root level php.ini file that allowed the allocated memory to be changed. It now appears that all aspects of the CP functions are working properly.

I’ll get back to you regarding the Image Properties.

Hi Robert,

Okay. Glad that the CP now seems to be fine. Let me know what you find out about the image properties.

Cheers

Greg

I just noticed one other anomaly in the image source URL:
The image source url “domain.org/directory1/images/uploads/imagename_thumb.jpg border=“1” name=“image”” alt=“image”} width=“54” height=“58”

There is a double quote (”“) after name=“image”” as well as the } after alt=“image”}. These errors do not show up in the Image Properties field now.

I tried deleting everything but border=“1” from the Image Properties, but the image source urls in the existing entries did not change. Is there a way to get these to get new Image Properties to applied retroactively to existing entries?

This problem did not show up until I upgraded to EE2 & PHP 5.1.6. Either the older version was able to ignore these errors or the error was somehow introduced during the upgrade.