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
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
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
You're after Lamplighter and the add-on that accompanies it.
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'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
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
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
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
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
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
Never ever do direct EE1 to EE3. First of all upgrade EE1 to EE2. That will make necessary changes to your database. (Remember change all the plugins with EE2 version otherwise backend and/or frontend may crash.)
After upgrading it to EE2, upgrade your server then upgrade site to EE3.
Remember to:
Always take a backup copy of your site.
Its good to ...
1
Pretty sure you don't need this in a plugin `$this->EE =& get_instance();
ref https://docs.expressionengine.com/v2/development/plugins.html
1
Change permissions to system/user/cache/rss_parser/cpnews_feed to 777
1
If Steven's answer doesn't get you the version number, you could deduce the general version by the table names and native fields used and comparing them to the ExpressionEngine release notes.
It might not get you to an exact release but perhaps closer than not knowing at all.
(Update: you asked for a "specific version of EE", which my suggestion will not ...
1
Have you identified which field is id 14?
You can by looking at table exp_field-types or by looking at your field-groups inside the CP. Once you figure out the field in question, that may give you a clue. If unused, you can try getting rid of it.
Or you can change the NULLs to "" by running the following Query (backup your table before doing this, just in ...
1
Ooo yeah you shouldn't have tried to revert. I ran into this issue upgrading a huge site; they literally just have a bug in the updater if I remember correctly. You just need to get the settings for the column from a previous backup, and make sure you create that column manually with the correct settings. Sorry, wish I could be more specific, but I don't ...
1
Ok, To update the jquery reference globally you can do it by redefining the constant PATH_JQUERY. This definition is defined in the file /system/expressionengine/modules/jquery/mod.jquery.php, lines 39 through 46 (on EE2.10.1).
This patch assumes you have your jquery and its dependant libraries in the same folder structure as in /themes/javascript.
And my ...
1
No new features - view changelog.
EE v3 is being released this year and the developers confirmed that there are no more features to be released in the v2 family, it will only be security additions and bug fixes.
1
I ran into the same problem. After talking to EE support, they informed me I'd need to update the meta hidden field as well if I wanted to update the entry, instead of creating a new one.
The meta hidden field is an encrypted string representing the settings for the form. This includes the entry_id, so if the meta value isn't updated, it posts a new entry ...
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