Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Vanilla Pre-Release 2
This discussion has been closed.
Comments
We came across some problems while upgrading Vanilla... Vanilla seems to have been upgraded already. You will need to remove the conf/settings.php and conf/database.php files to run the upgrade utility again.
If i delete the files as mentioned and try again, it just creates them again and gives me the same error, but this time it has the next step underneath (the server details)
If i fill those in, it keeps giving me the same error again and again
This also happens if i try a fresh one.
any reason for this?
It then gives me the same page back, but i can see by looking at the databse that it has actually created some tables and the files on the webserver have been configured correctly from what i can see - it just wont go past stage 2!
any ideas?
Turn on the HTML formatter and then go to your account page, preferences, and make sure that your preference for hiding those things isn't checked.
I downloaded from the svn before v1pre1 and there were a lot of extensions included (such as markdown, rss2, etc) These extensions aren't available from the addons page, and the ones I got from the trunk don't work with the v1pre2. I really like markdown for comment styling and since I use safari, rss is great, but atom not so great. Any plans to release rss2 for v1final? Markdown?
A lot of the extensions in svn don't work. I haven't been working on the extensions at all. I just want the core done and working properly. When Vanilla 1 is released I'll be getting those extensions working and adding them to the add-ons directory.
Bizarrely, this time when I went through the upgrade I couldn't be bothered to change permissions on the files but it went through fine and still worked. Does that make sense?
Sure. It could be that your server's default settings are lax...
I'm finding a chunk of extensions don't work properly or at all. I just tried 777 on the ext folder but this did nothing. Could a missed permission be causing a problem?
It could be permissions, yes. It could also be that you're using extensions from the previous version that aren't compatible with the new version. If you are having problems with an extension that you got from lussumo.com/addons, you should be telling people about your problems on here.
Am I the only one having problem with the extensions that came with the package - like Clipboard? I keep getting fatal errors about the DB not existing. I don't think its being created for come reason.
Like I said above, those extensions haven't been worked on for months and aren't ready for release. The only ones that ARE ready for release are at lussumo.com/addons. And if you get one from lussumo.com/addons that doesn't work, you should tell people about it on the forum here (in a new discussion).
So there are supposed to be no extensions that are packaged with Vanilla by default with this release?
No. There won't be *any* extensions with the next release of Vanilla. I want the community to really own the add-ons and make Vanilla what they want it to be. That's why I've got that big message when you first install it about going to lussumo.com/addons for your extensions.
having trouble with the upgrade to be honest, it passes the 2nd step (permissions) and then tells me:
We came across some problems while upgrading Vanilla...
Vanilla seems to have been upgraded already. You will need to remove the conf/settings.php and conf/database.php files to run the upgrade utility again.
If i delete the files as mentioned and try again, it just creates them again and gives me the same error, but this time it has the next step underneath (the server details). If i fill those in, it keeps giving me the same error again and again. This also happens if i try a fresh one. any reason for this?
Hmm. I'd say try downloading it again from here. I had messed something up in the first hour that I released the zip that caused a very similar problem. I fixed the problem and re-uploaded the file really quickly, but you may have grabbed that old zip.
When I release Vanilla 1 I'll be tagging the svn repository as V1 and moving from there.
Just checked and on both accounts it's right, HTML formatter is enabled and it's checked in my accounts page, the "Format comments as" text is still present, just not the actual radio buttons, I tried disabling all extensions apart from HTML formatter and it still happened
What version of PHP?