5.0 Upgrade instructions
#2318
Replies: 11 comments 10 replies
-
|
Should we tell people to make sure they're in |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
When running the last This is probably because one of the scripts assumes the public directory to be named |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
After these steps I needed to run the/a db migration, the one provided by bolt/core didn't work for MariaDB, see fix: #2570 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
The question is, how do I get from 4.1 to 4.2 ? |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
@eduardomart I've updated the instructions, with the missing part. (setting the |
Beta Was this translation helpful? Give feedback.
-
|
I finally got a chance to give this a try, changed composer.json: Result: 😫 |
Beta Was this translation helpful? Give feedback.
-
|
@eduardomart Could you try setting |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @bobdenotter, I followed your advice, this is the result: |
Beta Was this translation helpful? Give feedback.
-
|
Alright, I tried, after getting to 4.1.99 and continuing with the instructions at the top, I ended up here: |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Hi @eduardomart , Maybe you already got this solved, but what worked for me was to remove the I experienced a similar error with the SecurityCheckerCommand when updating from 5.0.0-beta.6.1 => 5.0.0-beta.12. |
Beta Was this translation helpful? Give feedback.
-
|
I honestly gave up. Maybe I'll give it another try later this week. |
Beta Was this translation helpful? Give feedback.
-
|
@nestordedios Thanks so much for the info, I was having trouble still, as the 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
Good to hear you got it fixed @eduardomart 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Update from new v4.2.1 to 5.0.0 to 5.0.0-beta.13 is broken too... |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Yes, I did a fresh install of 4.2.1, using the default sqlite. I followed the instructions at top. No need to edit composer.json, except for stability:"beta". Composer update & diagnose are happy. Note some strict warnings in
|
Beta Was this translation helpful? Give feedback.
-
|
@bingalls @eduardomart That issue that you two have been bumping into, should've been fixed in this PR: #2800 It'll ensure that bundles that have been removed from composer, will also be removed from |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Please notice that since the release of Bolt 5.1.X you will also have to add some lines about caching to config.yaml as you will be updating from 4.2 straight to 5.1 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I had a problem with one migration on mysql DB: To fix it you can manually delete foreign key: show create table bolt_user_auth_token;
-- Here will be a row like this: CONSTRAINT `FK_8B90D313A76ED395` FOREIGN KEY (`user_id`) REFERENCES `bolt_user` (`id`)
-- drop it:
ALTER TABLE bolt_user_auth_token DROP FOREIGN KEY FK_8B90D313A76ED395;Reinstall migrations: May be someone have a better solution. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
If you have problems with composer scripts like this: You need to add execution rules to your bin/console file: chmod +x bin/consoleNow you can check it by run script from console: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
After updating from 4.1 to 4.2, my dashboard is empty: I only see the bottom status bar (dev mode) and the cards on the right (e.g. Bolt Configuration Notices). EDIT: I just realize that setting the |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I solved my first issue (empty dashboard) by resetting the file/folder permissions. For the second issue (error 500 in production mode), I cleared the cache by deleting the content of the folder |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How to update from Bolt 4.x to 5.0
First upgrade to 4.2
Update to version 4.2 if you're on a lower version, by doing the following:
composer update.php bin/console bolt:infoor in Bolt's Dashboard.Edit the "scripts"
Switch your site to 'dev' mode by setting
APP_ENV=devandAPP_DEBUG=1in your.envor global env settings.Then, to prepare the update to 5.0, replace the
"scripts"section of yourcomposer.jsonwith the following:Add a new "autoload-dev" section in the composer.json file right after the above scripts section, like so:
Finally, replace the following:
"bolt/assets": "^4.x"with"bolt/assets": "^5.0","bolt/core": "^4.x"with"bolt/core": "^5.0".Now you can run
composer update, and you'll get Bolt 5.0.The update process will automatically make the required changes in the Yaml files in config. When it's done, the last step will be to update the database:
Beta Was this translation helpful? Give feedback.
All reactions