Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
[Request] Test upgrading to 2.1 and 2.2
UnderDog
MVP
I would love to request this to anyone who has an opportunity:
Let's set up a separate installation of your Vanilla. Either with your plugins and themes or just a standard, basic installation with a 'demo' database.
As soon as you have current situation running on that separate Installation (local computer or on your server) with Vanilla 2.0.18.8 or lower, save your files, database, etc. and try an upgrade
There was an error rendering this rich post.
1
Comments
I can tell you how I upgraded, well the way I installed Vanilla 2.1
I could not install using upgrade, I installed vanilla 2.0.18.8 , then ftp the new version and overwrite the old. That worked for me and did not erase my plugins or themes other than the default contents. I did have to tweak many things to get it to work . The data base was the same one. I changed the version to 2.1b1 in the config that already existed.
I did not go through the set up process for 2.1 I only overwrite the old one. I don't have a huge , well not even a little user base , so I had nothing to lose if it went bad, But everyone should be careful and know what they are doing as best as possible.
I could test doing the same with 2.2 .
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
utility/update - that is the primary question.
does it work.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
My last upgrade from 2.0.18.8 to 2.2 used utility/update and worked without issue.
Search first
Check out the Documentation! We are always looking for new content and pull requests.
Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.
awesome @hgtonight
so 2.2 must be the ticket. i never tried it. glad it worked.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
I'm gonna wait for 3 , two point three that is....
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
I would also use utility/structure in case.
Add Pages to Vanilla with the Basic Pages app
I am already running 2.1b on my live forum. Though I understand that it is not meant to use in production environment but I have waited very long. In fact longer than the wait for next version of Mario Bros.
Here is what I have done to upgrade -
1. made a fresh install of 2.1 from Github.
2. Used Vanilla exporter to import old database.
3. Ran utility/update and utility/structure. Everything was good.
Everything is smooth till now.
No issues faced with 1500 members and 800 discussions on shared hosting.
I would say, release the Kraken. I mean 2.1.
They even rhyme
There was an error rendering this rich post.
I suppose I should clarify that I am using the master branch version at github. My upgrade took place around 3 weeks ago.
It went well though.
Search first
Check out the Documentation! We are always looking for new content and pull requests.
Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.
Sorry, but I do have problems with the update. After searching across this community forum for similar problem I found many users in this situation, but no clear solution.
I'm using 2.0.18.8 and would like to upgrade to version 2.2.3.11 or 2.2.3.4 (or any above 2.1 for that matter). Upgrade stops at trying to use
utility/update
. It returns blank blue screen with one horizontal blue line, no error shown. If I tryutility/structure
it returns Bonk page with this error:So, it stops here. Any way to get around this?
@tom762 Try disabling your plugins first, there may be some that are incompatible with 2.1+
There was an error rendering this rich post.
Irritation: Updating to 2.2 is not recommended or as the 2.1 branch has been developed much futher than 2.2 (and 2.2 is now considered quiet) or?
Don't use 2.1 or 2.2 unless you are comfortable filing bug reports on GitHub. Even then, don't use it for production.
Search first
Check out the Documentation! We are always looking for new content and pull requests.
Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.
Ups, didn't know that. Guess I'll wait for a solid release.
Thanks for all answers