I want to update my TYPO3 8.7.8 to the v8 LTS, but i can't seem to find any way to do this via the Backend. Do i need to manually install the new version as a fresh installation?
You don't need to add TYPO3 Source manually if you have create symlinks in your typo3 installation and already running with TYPO3 Version 8.7.x.
If your TYPO3 Version running in 6.2.x Then First you need to upgrade TYPO3 Version 7.6 and after TYPO3 8.7. You can't upgrading Directly version 8.7 if your systems is running in 6.2.x.
Just you need to follow below steps.
Login TYPO3 BE and Go To Install Tool.
In Important actions you see the Check for core updates button. click on this, Here you can find latest TYPO3 version.
After download latest TYPO3 Version. Click on Compare current database with specification and update typo3 core Database.
After compare DB Go to Upgrade Wizard and perform all required steps.
Note: When performs all above steps first you need to take a backup of your database. So, in case of any problems then you can restore old DB.
Follow the upgrade guide in the docs
https://docs.typo3.org/typo3cms/InstallationGuide/Upgrade/Index.html
I want to upgrade a moodle website currently on version 2.5 to the latest version.
I need to clarify that is it possible to upgrade Moodle 2.5 directly to Moodle 3.3.
OR
As mentioned in the moodle upgradation document
"Note: You can only upgrade to Moodle 3.0 from Moodle 2.2 or later. If upgrading from earlier versions, you must upgrade to 2.2 as a first step."
I can only upgrade to Moodle 3.0.
Please confirm.
Thanks in advance.
In order to upgrade Moodle 2.5 to 3.3, start by backing up your site. This includes:
The Moodle files.
The Moodledata files.
The Moodle database.
Make sure you have everything and that no errors occurred while you were backing it up. If you want to be extra sure, restore it to a different location, maybe even locally on your computer and get it working there. Don't forget to adjust the settings in the config.php file as well as running the Moodle Search and Replace tool (it is not in the Moodle menus). Once you are sure that everything is working, and you still have the original unmodified backup files, you are ready to move on to the next step.
Verify your web server environment
Make sure your web server meets the hardware requirements for Moodle 3.3. Note the changes, especially in memory requirements from 2.5 to 3.3. Also make sure your server meets the software requirements for Moodle 2.7. In fact, when upgrading, it is best to verify the software requirements for every version of Moodle you will be skipping in order to find out which system components you will need to be add before proceeding.
Also, before you get started, make sure any 3rd party plugin and themes added to your site will be compatible with Moodle 2.7 and Moodle 3.3. If not, you will need to upgrade these first. If they are not available for the newer releases of Moodle, check with the maintainer of the plugin/theme to see if there might be an updated version forthcoming. If not, you will either need to fix any problems in the code yourself that may come up, switch to another similar plugin that provides similar functionality or remove the plugin completely.
Re-creating .git
The easiest way to upgrade Moodle is using Git. If Moodle was not installed using the "git clone" command, your installation will likely be missing the .git directory. You can check this by using the "git status" command. If you already have a .git folder, you can skip this section and go straight to Upgrade to Moodle 2.7. Otherwise, here is how you can re-create it:
Take note of the build date for your current Moodle installation. You'll find this on its Notification page near the bottom of the page.
Re-create your .git folder using the following commands:
# git clone a new copy of Moodle into another location
git clone git://git.moodle.org/moodle.git
# Checkout Moodle 2.5 (the version of your current site).
cd moodle
git checkout MOODLE_25_STABLE
Look through the log for a weekly release that is dated the same as your build number. The build number is a date in the following format: YYYYMMDD. Take note of the related commit number.
Next, rollback the files to the commit number of the build. Replace "56e05fced" with the actual commit number.
git reset 56e05fced
Once this is done, copy the just the .git folder into the web root of your current Moodle site.
Upgrading to Moodle 2.7
Before you get started, make sure any 3rd party plugin and themes added to your site will be compatible with Moodle 2.7. If not, you will need to upgrade these first.
git checkout MOODLE_27_STABLE
Login to your website as an administrator. You should see prompts that will guide you through the process of upgrading Moodle.
IMPORTANT: Up to this point, you could just roll back the files and everything should be back to the way it was. Once you move beyond this point, the only way to revert your website will be to delete the whole site and restore the backups you made earlier of your site's files and database.
Follow the prompts to upgrade the database. Be prepared as you may need to upgrade some of the plugins as well or make some upgrades to your web server and/or database environment.
Once you have everything running again, it will be time to upgrade to Moodle 3.3.
Upgrading to Moodle 3.3
Have you upgraded to Moodle 2.7 yet? If not, go back and complete that step first. Don't forget to make sure your web server meets the hardware requirements for Moodle 3.3.
Make sure your server meets the software requirements for Moodle 3.3 in order to successfully complete the upgrade from Moodle 2.7.
Next, upgrade Moodle from 2.7 to 3.3:
# Enable version tracking so that it is easier to upgrade Moodle in the future.
git branch --track MOODLE_33_STABLE origin/MOODLE_33_STABLE
# Upgrade Moodle to version 3.3.
git checkout MOODLE_33_STABLE
As you did before for Moodle 2.7, Login to your website as an administrator. You should see prompts that your database is about to be upgraded. If not, go to the Notifications page under Site Administration. Follow the prompts again to upgrade the database. As before, be prepared as you may need to upgrade more plugins and themes, and will likely need to make some upgrades to your web server and/or database environment.
That's it. If you followed the above instructions, your Moodle 2.5 site should now be upgraded to Moodle 3.3. To get the most out of your upgraded site, be sure to at least read the New Features page for each version of Moodle from 2.6 to 3.3.
To upgrade your site to newer bug/security release of Moodle 3.3, you will need to repeat some of the instructions. Essentially it will involve:
Backing up your site files (moodle and moodledata) and database.
Using the "git pull" command from within your Moodle folder.
Logging in as an administrator and following the upgrade prompts from the Site Administration > Notification page.
Verifying that everything on your site still work as expected.
Bug and security fixes come out every week but are only officially release every 2 months.
Hope you find this information useful.
Best regards,
Michael Milette
Per the upgrade documentation for 3.3 it says "You can only upgrade to Moodle 3.3 from Moodle 2.7 or later." https://docs.moodle.org/33/en/Upgrading
So you must first do an upgrade to v2.7 before you can do an upgrade to v3.3
Also note in the v2.7 upgrade documentation it says "You can only upgrade to Moodle 2.7 from Moodle 2.2 or later." https://docs.moodle.org/27/en/Upgrading
Personally I have found less problems when I do upgrades in smaller jumps. So in your case 2.5 to 2.7.20 is a requirement. In theory you could then go from 2.7.20 all the way to 3.3 but you may want to consider 2.7.20 > 3.0.10 then 3.0.10 > 3.3
I can say that I have actually upgraded Moodle 2.3, and Moodle 2.5 successfully to 3.x, though not 3.3 specifically.
That being said, you have to also take the following considerations:
Are you up to the minimal PHP version? (5.6.something)
Do you have the new modules required by 3.x version (3.3 added a few I think)
Are your modules ready for 3.x?
If you aren't sure of any of these, I would go grab a Vagrant/VirtualBox/Docker setup of Moodle, stage your current site (i.e. install it with the same software you have installed on your production server), and upgrade it locally to ensure everything goes as planned.
First you backed up before any moodle 2.5 upgrade.
Then download new moodle 3.3
After then unzip folder
go to xampp->htdocs->your project
paste and override new folder
Copy your old config.php file back to the new Moodle directory
Sometimes, the environment may cause issues, sometimes the Moodle versions. I have faced both. But managed to upgrade. Last time for upgrade to 3.9.2 installed the old version to local server for reference and did a clean install on the cloud. I have upgraded Moodle 2.x to 3.2 for a couple of institutions. Please feel free to contact if needed.
Few steps to consider in this
Take backup of Moodle app, Moodledata and DataBase
You have to follow the upgrade process twice
First you need to upgrade from moodle 2.5 to moodle 3.0
Now you can upgrade you new moodle 3.0 to moodle 3.3
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.
I have a Typo3 4.2.6 Version running.
To which version should I upgrade? (Can I upragde to 6.x?)
How should I do the upgrade?
You should upgrade to 4.5 in an first step. The Version 4.5 is a LTS (Long Term Support) Version, the end of maintenance is in 3/2015 (see https://typo3.org/download/). I would not recommend to update to 6.0 now. Many extensions are not yet compatible and they changed a lot. At least the end of maintenence is the same as with 4.5.
I would suggest it to be upgraded to the latest version of typo3 4.7. Upgrading the site to typo3 6.x won't be a good choice as there's exists lot of open issues in typo3 forums regarding the upgrade to typo3 6.x. Most of the extensions in typo3 4.x won't work smoothly in typo3 6.x. So I suggest an upgrade to the lastest version typo3 4.7.
For typo3 4.6 onwards need PHP 5.3 otherwise you can upgrade to 4.5.x.
How to upgrade typo3?
Check this link: https://sankartypo3.wordpress.com/2012/05/17/how-to-upgrade-typo3-version/
I've once successfully upgraded typo3 4.2 to 4.7 in a step by step way (4.2 to 4.4, 4.4 to 4.5 and 4.5 to 4.7). The issues after typo3 upgrade were solved using methods mentioned under "Some simple ways to find out the errors/issues after upgrading typo3!" in the above link.
Migration
STEP FOR UPGRADING TO 6.2
1)take a backup of old site (Dont forget to take backup of Database)
2)check if any extension installed globally make it local means (remove extension from /typo3/ext/ and install from TYPO3 TER which stored in folder /typo3conf/ext/ )
3)upload folder "typo3" of newly downloaded TYPO3 version
4)create folder "typo3_src" in root
5)remove "t3lib" folder
6)upload index.php from root folder
7)go to typo3 BE, go to install tool
8)click on "System environment" and check if there is no error. if error exists solve the error.
9)click on "Folder structure" and try to solve as much error as you can.
10)click on "Upgrade Wizard"
11)perform all update wizard Section like
"Migrate all file relations from tt_content.image and pages.media"
"Migrate all file links of RTE-enabled fields to FAL" etc...
12)click on Link "Go to Database Analyzer" at the end of "Upgrade Wizard" page.
or
click on "Important actions"
13)Go to "Database analyzer" section and click on "Compare current database with specification"
14)perform execution in section "Database analyzer"
15)Click on "All configuration" and Go to "$TYPO3_CONF_VARS['SYS']" and change the value of "[SYS][compat_version]" to 6.2
16) perform "Clear all cache" from "Important actions"
I upgraded from TYPO3 4.1 to 6.1 using this procedure:
Export all the content to .t3d. (If too large, make it in chunks)
install 6.1 and all your plugins. (This ensures the DB has all needed tables).
Copy the old fileadmin/ content into the 6.x fileadmin/
Import .t3d
Fix plugins problems, i.e. deprecated functions etc.
It is wise to try it first in your Windows local machine.
After updating my TYPO3 CMS from 4.3 to 4.5 LTS the news were no longer displayed. So i decided to update tt_news extension as well. It was at version 2.5.2 and had to be upgraded to the newest 3.4.0. It suggested to me, to use its own 'update script' (and as mentioned at other resources too) to work properly because of serious changes. Under 'Extentension Manager' - 'tt_news' - 'UPDATE!' it shows up with a simple blank page and nothing can be done.
Is there any hint to solve this?
You have got some PHP error. Copy the /var/log/apache2/error.log or enable in TYPO3 Install Tool configuration PHP errors.