Fixed. But judging by the number of similar threads I still think this is beta-ish.
On the initial upgrade from EE 1.6.8 to 2.10
- Backed up DB
- Upgraded. Could not login to the CP. This is a frustrating cookie / session issue. Went back to EE 1.6.8 DB and changed session & security preferences to both session as opposed to cookie
- Upgraded again. Still couldn’t login. Followed yet more threads on this topic and ended up adding a few more cookie override lines to the config.php line and was able to login to the CP
- Once in the CP, images were a bit screwy as well. To everyone who has ee2 CP theme issues, notably the background in the menu background missing and in my case the website selectively serving up some images and not others. Upon investigation, some URLs has S={long string} appended and that was part of the confusion. Suspected this might have to do with session login, which I enabled for the privilege for logging into the CP in the first place.
- Went back to the CP, disabled sessions and went back to cookies.
- Works and I can see all the images
- Now navigation is hosed, but the site and images load. I just need to deal with apparent template/weblog embed logic that seems to have changed between EE 1.6x and EE2.
I’m really glad I backed up the DB and used a staging site, because it is likely to be a while before I’m comfortable doing all this for a production site.
Also - on the initial upgrade itself, EE2 upgrade process to claims to disable extensions / plugins. I didn’t find that to be the case. Using Levi Graham’s Better Meta 1.8 (great product) on the 1.6.8 site - it was *not* disabled and wouldn’t let me login to the website at all until that was disabled. And I had to do that in the old 1.6.8 prior to upgrade. So on the second upgrade I manually disabled just about everything I could find, cleared the caches, crossed fingers and then proceeded with the second upgrade