We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

Trouble Upgrading to V2 from V1

News and General

twotone8's avatar
twotone8
11 posts
6 years ago
twotone8's avatar twotone8

Our site is running a dangerously old version of expressionengine. Now that EE has gone open source, it was a great incentive to try and get things up to snuff, but because we’re dealing with such antiquated software, upgrading has been a bit tricky.

Our v1.6.3 site wouldn’t even load on modern LAMP stacks, but we’ve managed to finally get her updated to 1.7.4 without too many problems.

The jump to v2 has been a bit more difficult.

I don’t believe we are dependent on too many obsolete plugins, but we’re having trouble getting things ironed out.

The immediate issue at hand is that none of our picture files are being registered in their channel fields.

We’ve synchronized the upgrade folders and templates, verified the paths, and all of the files are now registered in the database and show up in the file manager, but when we go to edit the channel entry directly, each field that used to link to a picture simply states “File not found. We could not locate blahblahfilename.jpg on the server.”

If we delete the non-existent picture and re link the existing file from the database, it shows up just fine, but we have hundreds of past entries and would hate to hammer them all by hand.

There are several other issues, but this is the brick wall I’ve been hitting my head against most recently.

We have the main upload directories linked as follows

Server Path to Upload Directory: /var/www/images/uploads/

and

URL of Upload Directory: https://blah.websitename.blah/images/uploads/

We’ve tried making tiny modifications to each, but still, the files do not register as existing to the channel entries. If anyone could shed any insight, we’d love it. We’re a tiny non-profit, and have no money to throw at the problem. I’m no web designer, and I’ve inherited this task from someone else who is long gone. It’s a simple site, but no one has touched the inner workings in many years.

edit: Hrm. I dug around the raw mysql database after fixing some of the channel entries manually (by deleting and re-adding the file from the main upload directory).

the field data previously read filename.jpg, and now reads [filedir_1]filename.jpg. Should I figure out some way to manually input the [filedir_1] tag into each of these fields before the file name? Strange behavior.

edit:2 Very frustrating. I managed to use a tiny script to manually add the [filedir_1] directly in front of each field entry for the column in exp_channel_data, but they still aren’t being displayed. The editor still says ‘[filedir_1]filename.jpg’ was not found on the server. Again, when I delete the pic and re-add the picture from within the interface, it shows up just fine, and the sql database registers it with an identical ‘[filedir_1]filename.jpg’ just like I had it. I’ve cleared the caches, but for some reason I can’t get EE to recognize those pics.

3dit:E Figured it out. In the mysql database, the fields were full of line breaks after the filename. [filedir_1]image.jpg ended up working just fine once i used a script to get rid of any line breaks or spaces after the entry. Not sure why [filedir_1] wasn’t automatically added after the V1 upgrade, but it’s all fixed now.

       
Derek Jones's avatar
Derek Jones
7,561 posts
6 years ago
Derek Jones's avatar Derek Jones

Glad you figured it out @twotone8! If you just upgraded to v2, then you are in perfect shape for an easy and smooth upgrade to v3, and then jump to v5. Most v1 installs did not have many third-party add-ons, which was the challenge for many going from v2 to v3. So take advantage of the fact that you were coming from v1 and get on the latest, feature-rich, secure, and supported version!

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.