Thread

Hi,
I recently migrated my ee install fom MT DV 3.5 to MT DV 4.0 using the Plesk Migration tool. After the migration it did not report any errors.

I have run the ExpressionEngine 2.x Server Compatibility Wizard and it reports everything is ok.

Sometimes I can see the admin login page in the browser and sometimes I can not.

When I try to login to the ee admin I get a blank page.

The admin login url is http://www.realestatefanatics.com/admin.php

Can you please advise on what the roadmap is to trouble shoot this?

I intend to eventually upgrade to 2.3.1. I already have the license. But I thought it might be wise to get this 1.6x version working ok first. Or not? 😊

Thanks and have a GREAT day!

Hi, Mike. You might want to consider upgrading the 1.6.6 site to 1.7.1, that will refresh your files, and see how it goes.

Since sometimes you see the site and sometimes you don’t - that could be a strictly MT issue. I was able to see the login page a few minutes ago.

Howdy Sue,
I have downloaded the files to update to 1.7.1. I have prepared my directories by deleting the old files and uploading the new files. I have backed up path.php, system/config.php. I have uploaded the new files from the 1.7.1 zip file.

However when I go to http://www.realestatefanatics.com/system/update.php the screen shows that the update is for Update from Version 1.6.6 to Version 1.6.7 and not 1.7.1. The screen reads:

Welcome!
You are currently running ExpressionEngine: Version 1.6.6

If you have followed the Update Instructions and are ready to update your system, please click the link below

Update from Version 1.6.6 to Version 1.6.7

Should I proceed anyways?

Also can you tell me what should the php file permissions be set to and the root/home dir?

Hi, Capt.Mike.

The update is done in stages, it will say 1.6.6 to 1.6.7.. all the way to 1.7.1.

As far as permissions go..

path.php should be 666.

config.php should be 666 as well. EE will write to that as the update concludes.

Does that help?

Thank you Sue. Yes that helps. W/ regard to the mysql db for this ee db and user mysql phpmyadmin reports that priveleges are set to ALL PRIVELEGES but GRANT is set to NO. Is that ok? I have run the ee wizard and it reports everything is ok. Just wanted to check on this before I run the update.
Thanks Mike

I’d feel better if you had GRANT set to yes. But you may not need it. Give it a try and see!

Thank you Sue. I have successfully upgraded to 1.7.1. 😊 Thank you.

Now I am ready to go to 2.3.1. 😊

I am confused w/ regard to the following when going from 1x to 2x:
-Rename system/ to system_old/ (you may have previously re-named “system” to something else)

If I have renamed my system folder to /happy/ then I renamed it to /happy_old/
Then I upload the 2x system folder named system/

After the upgrade is done do I renamed the system/ folder to /happy/ ?

What do I do with the /happy_old/ folder?

Should I remove or disable any of my 1x extensions or modules?

Besides following the upgrade docs is there anything else you think I should do or know before the upgrade?
Thanks a TON.

Let’s take a quick inventory of what you are using third party wise right now.

Are there 2.x versions for what you need?

You could rename your EE2.x folder to /happy before you start the upgrade. 😊

Congrats on getting to 1.7.1. 😊

Hi Sue,
I have:
LG Addon Updater (v.1.0.2) 

jQuery for the Control Panel (v.1.1.1)

LG .htaccess Generator (v.1.0.0)

File, by Mark Huot (v.3.1.1)
Adds a “File” field type

Thank you.

OK..

File is the add-on that you’ll need to convert over to something else before you start. (Text file would be what I suggest.)

http://ee-garage.com/nsm-htaccess-generator is the upgrade for Leevi’s add-on.

Thank you Sue,
Would the path of having the best chance for a successful upgrade be to:

1. Deactivate all the addons before the upgrade?

2. deactivate and remove all the addons before the upgrade?

Could I leave jQuery for the Control Panel (v.1.1.1) alone regardless?

Hi, Mike -

You won’t need jQuery for the CP in EE 2; that’s baked in.

If you deactivate add-ons you’ll lose that data.  Having the upgraded versions ready would be ideal.

I’d recommend running through the upgrade in a dev environment to see what you’ll need to address before you upgrade your live site.  That will be the best way to alleviate any concerns without any potential downtime for troubleshooting.

Does that help?