The best way to do this is to proceed carefully and make backups of your database at each step of the way. I have previously written a blog post on this, but will elaborate further.
Step 1: Before running your upgrade change all ngen field types to text, don't worry the data won't be lost.
Step 2: Next upgrade ExpressionEngine as per the official docs and ...
The guys at P&T did come back to me in less than 24 hours with a fix. I'll post it here in case someone runs into the same problem.
Take a look at the columns in exp_playa_relationships table in the
Does it have a field parent_var_id? If no, then the version you should set is 4.1.
If yes, does it have a field parent_is_draft? If ...
Luckily the add-ons you are using have some upgrade paths from EE 1 => 2... The only two you need to tweak are the file fields before and after the upgrade:
nGen File Field https://stackoverflow.com/questions/13041491/expressionengine-1-to-expressionengine-2-upgrade-with-ngen-file-field
File by Mark Hout http://ellislab.com/forums/viewthread/218268/
I asked this same question for a recent EE upgrade. The answer is on Stack Overflow:
The EE2 equivalent field is Safecracker File. Worked perfectly for my upgrade.
The upgrade from EE2 to EE3 is a major step - from EE3 to EE4 not such a big one. So getting your site to EE3 is the thing to focus on. How hard this will be will very much depend upon how your EE2 site is set up, and in particular what add-ons you are using.
To be able to upgrade to EE3 you need to get your copy of EE2 up to a late version (I think 2.10....
I've recently done about 8 EE1 to EE2 upgrades. For the most part everything went really smoothly. The key is to prepare and backup, backup, backup. Did I mention you should backup?
Use the native upgrade wizard and be sure to follow the instructions carefully. The download for structure includes a separate folder for upgrading structure 1 to structure 2. ...
So some quick googling, while MediaGirl was typing, found the answer here.
When EE updates, it’s running through each update file in order, and
those update files can be found at /system/installer/updates/. They
look like ud_231.php, where 231 is the version number that’s being
updated. When EE finishes running through the routines in that update
I usually document this stuff on my own (for the next time) so I'm racking my brain trying to remember. However, I think for me, there was an add-on (probably accessory) that wasn't compatible, and it blanked the whole thing out. I ended up disabling until it started working. You might just update all of your stuff to see if that helps.
To workaround the issue, I followed the advice from this EE Support thread by renaming the system/expressionengine/third_party folder to something else immediately before carrying out the upgrade. The upgrade then worked fine, and I renamed the third_party folder back afterwards and all was well.
The explanation for having to do this (from the same EE ...
Chat with the folks at Solspace that will soon have the ability to use http://www.solspace.com/software/detail/importer/ to convert EE 1 gallery to EE 2. I can't remember the full details at the moment but there was a screenshot on twitter just a bit back showing EE 1 gallery to P&T Assets as an import selection could be other options but they are in a ...
I think the best user-focused solution is actually changing galleries into entries in a dedicated Galleries channel and using Channel Images. You can do the transformation of existing data after your upgrade with some fairly simple SQL, and then going forward your editors would just add images into the Channel Images field in the channel entries.
Totally agree with Steven's comment, I'll give my own answer though as we recently went through similar.
We were migrating to a new server and took the opportunity to build php 5.5 on the server to skip a version and save us the hassle of any major version upgrades again anytime soon. Here was our strategy.
Upgrade all sites to latest EE build
Upgrade all ...
The installer/update script doesn't create the missing column. You can create it manually if you're comfortable editing your database. I was updating from 2.4 to 2.5.5 and ran into the same issue.
As with anything you should back up your database BEFORE doing the update or this procedure.
Run the following SQL on your database;
ALTER TABLE `...
I did a lot of different trials trying different methods. In the end no single method is perfect. I've found the thread Brad suggested very useful before.
Whatever method you try, make sure to backup everything twice. What I initially did was create two separate test DBs (one being a copy of the EE1 DB and a separate new EE2 DB) just to test out before the ...
This looks like a bug in EE2.6. Here's the proposed fix from that report:
Changed line 407 of system/expression/libraries/core.php from:
Have you checked all of your installed add-ons for updated versions? White screens are also typically a sign of hidden errors, so make sure that display_errors is enabled in your PHP environment, and set the $debug value in the admin.php file to 1. That may reveal a PHP error that identifies the problem.
If that doesn't help, and you think you have the ...
Alright, let's do this. I got you, fam. I've done several 2 > 5 upgrades, both small sites and some real big ones.
First thing, so far no client has opted to go the rebuild route. Generally it would take longer than the upgrade process (so more money from them), and I would only recommend it to a site that was in such bad shape (templates are a mess, PHP ...
The short answer is that there isn't a easy solution that will migrate all of the galleries features to EE2, without getting your hands a little dirty in code, other add-ons, or doing some manual migration by writing SQL queries.
Like you mentioned, the Gallery wasn't migrated to EE2, which was either an oversight when EE2 was built or just not a priority.
Did you check your channel's Posting Preferences? (Admin > Channels > Channel Prefs) Could "Automatically turn URLs and email addresses into links?" be turned on? This has caught me a few times in the past...
While ugly, you could otherwise wrap the output with URL Decode tags. This fall under the heading of "quick and damned-dirty" tho.
If somebody will have the same error - check if you have Solspace FreeForm . I had the same issue because of this (FreeForm v.4.0.4). Fix - temporary remove freeform folder. You can return it back after update will finish.
Funnily enough I'm going through exactly the same process at the moment.
I'm undertaking a conversion from LG Poll to VWM Polls.
If you don't care about these errors, you can just set the field's type to 'text' in the exp_channel_fields table, which will at least get your site working again. Then if you don't want to upgrade or migrate LG Polls you can ...
EE Recommends that you're on 2.10.1, this way you're less likely to run into issues. You'll want to make sure you have EE3 compatible plugins. The EE3 upgrade process requires you to change a lot of your EE2 files/directories to adhere to the new EE3 standards.
Edited for clarity ...
It looks like the installer didn't run properly and I suspect was a permissions issue. I set the appropriate permissions and then re-ran the installer and this time it seemed to run successfully and I could log back in to the control panel.
If you look within the table structure for the relationship, the relationship data is stored within database table exp_relationships so only we need to update this table for the field_id. The parent_id and child_id are already in same format required for multi-relationship.
You need to follow these steps:
1) Make the "book_author" as multi-relations by ...