Thread

I have a website with v2.0.2pb01 build 20100430 that I would like to update to the current version 2.2.2. Right now, when I login to the control panel, none of the dropdown menus work. The reason I would like to access the dropdown is because the instructions for updating say to go to Tools > Data > Clear Caching and clear the cache.

I guess my first question is if there is a quick fix for getting the dropdowns to work in that old version.

My second question is if it is really necessary to clear the cache, or can I just do the update without clearing the cache. Any potential problems with skipping clearing the cache?

I know I’m taking a big jump from v2.0.2pb01 to the current version. Any other things I need to keep in mind when updating, or should it be fairly painless?

Looking at the source code of the control panel home page, I’m not seeing anywhere that jquery is getting called, which would possibly explain why no javascript is working. Not sure why jquery isn’t getting called though…thoughts or suggestions?

Hi D. Shun-Luoi Fong,

As that is quite an old version now I think it would be best if we got you to try an upgrade to the latest version of ExpressionEngine. Hopefully this will fix any problems with the site as you will end up with a fresh set of files.

Please read through the updating instructions found here and ensure that you make a good backup copy of your site (database especially) first before attempting the upgrade.

Regarding clearing the cache :

As you can’t get to that menu on your site then if you instead FTP into your site and navigate to :

system > expressionengine > cache
(You may have renamed your system folder to something else so just substitute system above with the name of your system folder)

When you are in that folder simply delete everything in there except for the index.html file. This will allow you to manually perform that step in the update instructions instead.

If you could then come back here and post to this thread to let us know how that goes please.

Thanks.

Mark

Mark, thanks for the response. I went ahead and cleared the cache via FTP, uploaded appropriate files, and started the update process. It stopped and gave me the following errors:

A PHP Error was encountered

Severity: Notice

Message: Undefined variable: existing_fields

Filename: moblog/upd.moblog.php

Line Number: 275

---

A PHP Error was encountered

Severity: Warning

Message: Invalid argument supplied for foreach()

Filename: moblog/upd.moblog.php

Line Number: 275

---

A PHP Error was encountered

Severity: Warning

Message: require_once(/path/to/website/system/codeigniter/system/expressionengine/third_party/bridge/lib/addon_builder/module_builder.php) [function.require-once]: failed to open stream: No such file or directory

Filename: freeform/upd.freeform.base.php

Line Number: 33

---

Fatal error: require_once() [function.require]: Failed opening required '/path/to/website/system/codeigniter/system/expressionengine/third_party/bridge/lib/addon_builder/module_builder.php' (include_path='.:/usr/local/php-5.2.17/share/pear') in /path/to/website/system/expressionengine/third_party/freeform/upd.freeform.base.php on line 33

Should I have tried updating Freeform first? Do I need to restore the db and start over or can I pick things up from here?

D. Shun-Luoi Fong,

Looking at the last path in the error you posted offers a clue:

/path/to/website/system/codeigniter/system/expressionengine/third_party/bridge/lib/addon_builder/module_builder.php'

/system/expressionengine/ should not be under /system/codeigniter/ - It appears that somehow your new ExpressionEngine files ended up under the Codeigniter installation of you older install.

A fresh upload of ExpressionEngine should look similar to the image attached here.

Cheers, and let us know if you need further assistance.

Do you mean re-upload the newest version of EE and try to go through the update process again? Do I need to upload the backed up database of the old version or can I start off where I am at?

Actually, when I ftp into my site and browse down the path mentioned above, I can get to /path/to/website/system/codeigniter/system, but there is no folder “expressionengine” under there.

So a little confused as to why I would get an error looking down that path for a folder that doesn’t exist.

Thoughts?

D. Shun-Luoi Fong,

At this point, you would need to roll back to the original version of your database and be sure to follow the Udate Instructions very carefully. Most curious is why the installer is concerned with those third-party files…

Cheers,

Ok, will roll back and give it another shot. Will report back.

No luck. I rolled everything back to the last working version and went through the update process again. I’ve done quite a few updates in my time, so I’m pretty sure I did everything according to the instructions.

It gets to the screen during the update process that says:

Please Stand By…
We are currently updating your ExpressionEngine installation.
Do not close your browser until the update routine is finished.
2.2.2

And then goes to the page that gives the same errors I detailed in the original post.

Not really sure where to go from here…any suggestions?

Ok, I have no idea what went on here, but I think I got it working…

After I got the error message, just for kicks I tried deleting the installer folder and went to my admin.php page. What do you know, my login screen showed up and I successfully logged in. This after getting all those errors during the update process.

After logging in, I had the message on my CP home page that version 2.2.2 build 20110801 was available to download and update to. Funny, I thought that was the version I had just updated to (I definitely know I had uploaded the v2.2.2 files for this update). Looking down at the footer of my CP I realized I was at v2.2.1. So I decided to put the installer folder back again and browse to admin.php. Sure enough, it thought I wanted to update…and so I did, from v2.2.1 to v2.2.2. All using the same set of files both times.

It seems to be working okay. Kind of bizarre, but glad it is working. If any problems pop up I’ll post back again.

It seems to be working okay. Kind of bizarre, but glad it is working. If any problems pop up I’ll post back again.

Glad you have it working now. I’ll go ahead and close out this post now but if you do have any more problems please do feel free to make a new post.

Cheers,

Mark