Symphony 3.0.0
officially only supports updating from a 2.7.x
LTS release.
There are various changes between 2.7.x
and 3.0.0
that make this update impossible.
You first need to update to 2.7.x LTS before doing this migration.
Symphony 3.0.0
introduces numerous improvements that may affect extension compatibility.
Before updating, be sure to consult the extension compatibility table to verify that the extensions you’re using have all been updated for Symphony 3.0.0
.
-
Pull from the
master
branch atgit://github.com/symphonycms/symphonycms.git
-
Update all extensions to their latest versions.
-
Delete the vendor directory and run
composer install -o
-
Point your web browser at the
install
subdirectory (e.g.,http://example.com/install/
) to complete the update process. -
Manually add those lines to your
.htaccess
file under the security group
RewriteRule ^vendor/(.*)$ - [F]
RewriteRule ^extensions/(.+)/vendor/(.*)$ - [F]
-
If running on a remote server, make sure all those changes are replicated on the server.
-
You and your website are now in the future. Buy yourself a silver jumpsuit.
Follow the instructions below if you are updating not from git.
-
Download the latest release tar ball.
-
Unzip it and copy the content in your current project.
-
Update all extensions to their latest versions.
-
Delete the vendor directory and run
composer install -o
-
If you run it on a remote server, upload
/extensions
,/symphony
,/install
,/vendor
&index.php
, replacing what is already on your server (Ideally, delete the folders/files first). -
Point your web browser at the
install
subdirectory (e.g.,http://example.com/install/
) to complete the update process. -
Call a friend and brag that your copy of Symphony is newer than theirs.