To migrate from Typo3 7.6. to 9, do I have to make an intermediate step via Typo3 8?
I have a Linux Server and the current PHP is 7.0. PHP would be updated as well.
Would like to get to the current version of Typo3 but not sure if a direct jump would cause more problems. (This is aided by an agency, but would like to get second opinion whether intermediate step makes sense)
You should always do an upgrade step by step.
It's also good to have this step for all the DB migrations and some manual stuff like raising PHP version.
Depends on the extensions and the level of your knowledge. I would also prefer the step from 7.6 to 9/10 via 8, but if the Extension is still from pi Age or early extras, i would prefer to rebuilt it from the scratch, also because of changing db routines and other depreciation stuff.
Related
I want to update typo3 v7.6 to v11.5.3. I copied the files from the latest version to the old installation. The files are updates but I am facing database issues. The DB structure of v11.5.3 is different from v7.6. I need to migrate my data from v7.6 database to v11.53 database. Is there any way I can do it?
The core does only ship migrations for 2 major versions. Therefore you need to switch 1st to version 9 and do all the upgrade steps there and after that you can update to 11 and do the update wizards of 10+11.
All upgrade wizards can either be run via cli or via Install Tool.
Additional code migrations can easily done by using tools like rector
I personally don't care if the the frontend works in the intermediate versions and fix that at the end but as 7.6. is really old (and the used code could even be outdated in those old times) it will take a bit of manual work.
I am new to moodle and I need to do an upgrade. I have several questions first:
I have to upgrade from 3.4 to 3.5 and then to 3.9. Would I have to install all custom/aditional modules to 3.5 or can I do it just on 3.9.
This might be a dumb question, but I want to make sure I don't give anything for granted. In other to know which are custom/aditional modules I just have to go to the plugins view in administration and just copy the plugins that are on the section aditional plugins, right?
Thanks in advance
In general, you can get away with not installing all the custom plugins in 3.5. It is, in theory, possible that a 3rd-party plugin would choose to clean up their older upgrade steps, in the same way that core code does (which is why you can't jump direct from 3.4 to 3.9). I can't remember of any occasion where I've been caught out by a plugin doing that (and I've prepared hundreds of upgrades for different customers over the years). Note: you will see messages about plugins 'missing from disk' during the 3.5 upgrade step, but those should be fixed when you add the plugins back to the 3.9 code.
The list of additional plugins contains all of the plugins that are not part of the core Moodle code. It won't tell you about any custom changes that have been made to core Moodle files, but if you have simply been installing plugins and not messing around with core files (which is true in almost all cases), then you should be able to rely on the list.
Hopefully it goes without saying that you should always take a full database and moodledata backup before you start the upgrade, just in case there are problems (but, in my experience, they are fairly rare with normal upgrades).
What are the required steps to upgrade TYPO3 7.6.x to 8.X?. Currently My project running on TYPO3 7.6.15 and linux systems.
The only requirement that changes when you update from TYPO3 7 LTS to TYPO3 8 LTS ist the PHP version.
TYPO3 8 LTS requires at least PHP 7.0.
So first of all you need a local environment and a server with PHP 7.0 or 7.1. Then make a copy of your project (keep the original as a backup and a reference) and check all extensions. You want to know a) if you still need them and b) if they are already available for TYPO3 8LTS. If they are, you are fine, if they are not, you have to find an alternative, disable the extension (temporarily) or just wait with the update.
You then update the core and the extensions to the latest releases and go to the install tool. First you want to compare the DB structure to add new fields and tables (don't remove anything yet). After that go to the Upgrade Wizards and perform all of them that are not marked as "optional". Perform the optionals as you need them.
Now your backend should work if no extension breaks it. Your next steps are testing the functionalities that are provided by your extensions and make sure they still work. You might also want to have a look at the breaking changes of the TYPO3 core since 7 LTS to see if your system might be affected. Those can also be found in the install tool (Upgrade Analysis) and they usually have a migration documented.
You can find additional advice regarding updates of TYPO3 systems here: https://usetypo3.com/upgrading-projects.html
we are going to upgrade our typo3-instance from version 6.1.5 to 7.6. Since we need to clone the instance and afterwards upgrade it in two steps (6.1.5 -> 6.2, 6.2 -> 7.6) we wonder if it was easier to setup a clean 7.6 instance and migrate the data (templates, sites, binaries etc.) afterwards.
There are multiple instruction pages on the web describing how to upgrade to 6.2 and to 7.6 but it seems to be a really tricky process.
So I'd like to know if the t3d data is compatible between those versions. Can we export the data from 6.1.5 and import it to 7.6 without troubles?
What do you think of the approach?
Thanks,
Thomas
So I'd like to know if the t3d data is compatible between those versions. Can we export the data from 6.1.5 and import it to 7.6 without troubles?
Most likely this process will not go without troubles.
Best advice I can give, is to upgrade to 6.2, do the upgrade wizards in the install tool. After that upgrade to 7.6 and do the upgrade wizards in the install tool again (those will be different ones).
Your content should now be fine.
You can keep incompatible extensions uninstalled during this process as it is merely targeting content migration. Don't bother with extension code while doing this. Just the core and your content is enough to provide a working content structure for 7 LTS. Migrate the extensions afterwards.
I prefer the upgrade way to do it, because the t3d export / import thing may work, but may cause some troubles too, especially if this is a bigger site.
If you update the extensions on your 6.2 site to current versions, fix the namespaces and deprecation log entries in your individual extensions, the 6.2. => 7.6 upgrade should be quite smooth. In my experience it is much more convenient than a 4.5 => 6.2 upgrade.
What are the steps to downgrade a typo3 site and is this even possible?
I cannot get a few plugins to work on my 7.4 typo site so I decided to downgrade but I cannot find anything about it on typo forums or in the documentation. Are there any steps I can follow if this is possible.
Before upgrading your website you should always backup your data and avoid downgrading at any time.
Compatibility mode for TYPO3 6.x
The system extension compatibility6 is shipped with TYPO3 7, have you tried installing this extension already?
See also: Retaining compatibility to TYPO3 CMS 6
Downgrading from 7.x back to 6.2
There is no such thing as a documentation with downgrade instructions. But if you have no other option than you can try the following:
Before running TYPO3 again:
Backup your data
Remove the TYPO3 7 core as well the composer.json (and /vendor/ directory), .htaccess and index.php file from your website.
Remove the content of /typo3temp/, /fileadmin/_processed/ and /fileadmin/_temp_/.
uninstall all TYPO3 7 related (system) extensions by setting the state to inactive in the /typo3conf/PackagesStates.php file.
Uninstall or downgrade all extensions which are only compatible with TYPO3 7.x.
Set manual the ['SYS']['compat_version'] in /typo3conf/LocalConfiguration.php to '6.0' (we let TYPO3 think that we are uograding from 6.0. Please note that TYPO3 7 doesn't have this option anymore and you need to create it yourself.
Remove all array items from the array ['INSTALL']['wizardDone'] in /typo3conf/PackagesStates.php.
Set manual options such as ['FE']['activateContentAdapter'] back if needed.
Put the TYPO3 6.2 core back in it's place.
Now you're allowed to run TYPO3 again:
Log in on the install tool by accessing /typo3/install/.
Run the database compare but please don't remove fields or tables that belongs to extensions which you have temporary disabled for downgrading purposes.
Clear all caches from the install tool.
Run al steps from the upgrade wizard.
Reactivate disabled extensions (manually).
Check if the ['SYS']['compat_version'] is set to '6.2'.
Test your TYPO3 instance as good as you can.
Arek van Schaijk solution worked to downgrade 8.7 to 7.6. But a couple of additional changes might require.
in the file
typo3/sysext/core/Configuration/DefaultConfiguration.php
change fileCreateMask from 0664 to 0660
change folderCreateMask from 2775 to 2770
Symbolic links can be rectified with this solution.