12
I'll attempt to keep this answer opinion free!
Your first stop should be the EE3 changelog, and also catching up on the EllisLab blog over the past 6 months. But you'll also need to look at the EE2 changelog to see all the changes since your version that are also included in EE3.
The main changes are the infrastructure and Control Panel but it's where the ...
6
I use Git and Beanstalk to do a 2-phase upgrade process. I upgrade and troubleshoot locally then quickly deploy the upgrades to production when I'm done.
I wrote a blog post about it: https://www.kristengrote.com/blog/articles/the-20-minute-expressionengine-upgrade
5
Yes EE has gone for months without a bug fix release. No this doesn't make any sense. But so long as you're being a Smart Developer and backing up as you go you're not likely to encounter any major issues. Just build the site and search the bug tracker if you run into an issue. In all probability most known bugs won't affect you. If something explodes, which ...
5
Most of the errors I run into have to do with Safecracker, since I usually build out my stuff in the front-end. I have a rolling fork for it.
Saferacker_lib.php (Line 1210)
http://expressionengine.com/bug_tracker/bug/18233
There is another item I forgot to write down, but it's in the Safecracker API classes that extends the channel entries API.
5
You may want to consider updating to the latest 1.x branch (1.7.3) before upgrading to 2.x. That's solved all issues for me in the past.
4
There's also this nasty one that prevents you using {path=...} or {encode=...} tags inside your entries. Hotfix here:
https://support.ellislab.com/bugs/detail/18239/
4
Replace "parent::EE_Fieldtype();" on line 23 of ft.copee_pastee.php with "parent::__construct();"
4
If you're upgrading EE3 to another version of EE3:
https://docs.expressionengine.com/latest/installation/update.html
If you're upgrading from EE2 to EE3:
https://docs.expressionengine.com/latest/installation/upgrade_from_2.x.html
If you're upgrading EE2 to EE2:
https://docs.expressionengine.com/v2/installation/update.html
3
Per the 2.7.2 change log:
Addressed a security issue where XIDs may not invalidate properly.
Based on that you can make your decision. But, you're right that it's not clear how far back they see this vulnerability reaching. EE folks will always tell you to update.
3
I had this happen to me recently as well, upgrading a DB from 1.7.3 to the latest.
Even if you are in the DB and can respond to each error, the maddening thing is that as soon as you fix one error, it restarts the whole process for the version number it's on, meaning that you have to fix the entire list of errors, or it will simply re-choke on error number ...
3
I don't have an exact answer, but I had a problem similar to this. I was using Navicat and MAMP and I had character set issues in my local set up. I wrote a blog post about it for my own reference because it tripped me up several times. Not sure if this helps your issue though.
3
You're after Lamplighter and the add-on that accompanies it.
3
As error says, PHP 7 is only allow variables to passed by reference not an instance. You now need to remove that line and replace all $this->EE calls to ee(). That will work for you.
3
I've done several EE 2.X upgrades to 4.X and 5.X in the last few years, and on some pretty big sites to boot. It is non-trivial, but you can totally do it. Rather the retype a bunch of info, I laid out some strategies I've used successfully in this answer:
Upgrade a site from EE2 to EE5
If you have more specific questions, feel free to ask a new question ...
2
Okay so this one is a bit strange but I got it to run in the end! I thought I would post my own answer in the hope that it may help others if they come across this issue themselves...
Having rolled back to 2.1.3 a few times (that was fun!) and running through the update whilst watching the expected changes to the database I discovered the following:
The ...
2
I had exactly the same issue you had except I hadn't converted any of my fields first, I just totally spaced them. It is a little hard to be sure what you have and haven't tried, especially browsing from my phone, but I believe the SQL query here did the trick for me. Pasting it here for your convenience:
UPDATE exp_channel_data
SET field_id_XX = CONCAT('{...
2
First - you can get this count in your template by using {my_matrix_field:total_rows} - but I'll assume you need the number stored as a value in a field for other purposes (use in orderby perhaps).
In which case - yes, you'd write an extension, and use the entry_submission_ready hook.
Then in your method, pass $data by reference, so you can modify it. ...
2
Same process here, except that I update all add-ons the site uses in the process.
DevDemon updater can speed up the process a little bit.
2
This would only work if the install of EE had been updated at least once since initial install, but there is a log of version updates found in table exp_update_log. You've probably already checked this, but I thought it might be worth mentioning in case someone else runs into this issue in the future and didn't realize this table existed.
2
Important edit: a database backup before you do any module updating might prevent data loss and is always a good idea!
It is a pretty straight forward process. For Transcribe simply follow the official installation instructions and overwrite the currently installed module files. Find the instructions here:
https://eeharbor.com/transcribe/documentation/...
2
You could duplicate templates and alter their names but I'd only do that if there where only a handful of items.
If you have more then is manageable by simple duplication then it warrants the creation of a dev server and work directly on the templates then transfer across to live once happy with new codebase.
You can always backup the code by using git and ...
2
Thanks to the Romans-8---31-39 comment's, I discovered when i am logged as admin, exp:visitor:update_form is not processed, logged as member it is processed, so the the problem is solved!
1
Solved! Updating instructions say to copy the entire system/language/english folder from the old system folder to the new, updated one. But the old one was missing a file: template_router_lang.php.
I was able to go back to the files I downloaded from EllisLab, find that file, and put it in my server. Voila.
1
Since posting my question, I haven't figured out why this happened, but I did come up with a workaround for it:
Import your upgraded production environment's MySQL database on your local environment*
Follow the update instructions from EllisLab up to but not including step 6.
Change $config['app_version'] in system/expressionengine/config/config.php to 292
...
1
Something similar - possibly a plugin not responding. Remove third-party plugins in your system folder, try updating again and then return your plugins...you should update fine, and then you'll need the third-party items back in to open the control panel.
1
We ran the updates on our server and we didn't run into any problems. It seems EE v2.7.3 is compatible with all of these versions of Redhat, PHP, & MySQL.
1
First think I'd check is that the server meets EE's minimum server requirements:
https://ellislab.com/expressionengine/user-guide/installation/requirements.html
There is a server Compatibility Wizard you can download here:
https://ellislab.com/expressionengine/user-guide/installation/requirements.html#server-compatibility-wizard
If the server meets the ...
1
This error was fixed in version 3.0.1
1
Assuming you mean the instructions in the EE documentation then you need to ensure that the installer directory is within the system directory. Also ensure that the system directory hasn't been renamed.
The most important thing Back up your database and files before starting. It is very common for the update process to run into problems when going from a ...
1
Did you deploy the files from your local machine to dev environment?
I ran across a similar issue a few weeks ago as a result of deploying the upgrade files to my dev environment.
In that case the config.php had the $config['app_version'] = ""; updated to 273" instead of the needed "253" for the EE upgrade script to run properly.
Only top voted, non community-wiki answers of a minimum length are eligible
