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 1.1.5a Released
Mark
Vanilla Staff
I am pleased to announce the release of Vanilla 1.1.5. This release was entirely the result of this community's participation - kudos to you!
Particular kudos go out to Wallphone, (who contributed over 50% of the fixes and enhancements), and Dinoboff (who keeps me in the loop!). A list of all contributors can be found here.
Vanilla 1.1.5 can be downloaded from getvanilla.com now.
A full list of all fixes and features can be seen in the release notes.
Upgrading instructions can be found here.
Other Notes
I personally found that there was a strange glitch after I performed an upgrade to the community forum - the stylesheet disappeared for me, and another user reported that their stylesheet was switched to a completely different one I have sitting on this server. I fixed the problem by going to the "Themes & Styles" form on the settings tab, selecting the default Vanilla style, checking the box next to "Apply this style to all users", and clicking Save.
If you run across this bug, or any other bugs with the release of Vanilla 1.1.5, please use this discussion as a place to resolve those issues.
A list of the bug-fixes can be seen in the release notes.
Upgrading instructions can be found here.
Particular kudos go out to Wallphone, (who contributed over 50% of the fixes and enhancements), and Dinoboff (who keeps me in the loop!). A list of all contributors can be found here.
Vanilla 1.1.5 can be downloaded from getvanilla.com now.
A full list of all fixes and features can be seen in the release notes.
Upgrading instructions can be found here.
Other Notes
I personally found that there was a strange glitch after I performed an upgrade to the community forum - the stylesheet disappeared for me, and another user reported that their stylesheet was switched to a completely different one I have sitting on this server. I fixed the problem by going to the "Themes & Styles" form on the settings tab, selecting the default Vanilla style, checking the box next to "Apply this style to all users", and clicking Save.
If you run across this bug, or any other bugs with the release of Vanilla 1.1.5, please use this discussion as a place to resolve those issues.
Update
A new version of Vanilla (1.1.5a) has just been released. This version fixes three minor bugs that were affecting a small number of users.A list of the bug-fixes can be seen in the release notes.
Upgrading instructions can be found here.
0
Comments
I have never before been so disconnected from the goings on in my software. Every other release previous to Vanilla 1.1.5 has had my fingerprint on almost every aspect of it. This one, however, doesn't have any part of me in it. I may have offered advice to the contributors when asked, but I don't think I personally wrote even a single line of code for it. It is both bitter and sweet that it has come together so well without me. I cannot say enough how grateful I am to all of the contributors.
... and big thanks from all of us who can't code our way out of a nested for-loop.
To force vanilla to use MyUserManager, defined in /Path/to/extensions/MyExtension/library/People/People.Class.MyUserManager.php you simply need to add the following settings:
// conf/settings.php ... $Configuration['OBJECT_FACTORY_REFERENCE_USER_MANAGER'] = 'MyUserManager'; // persistent Object Factory reference $Configuration['LIBRARY_INCLUDE_PATH'] = '%LIBRARY%;%EXTENSIONS%/MyExtension/libary/'; // Where object factory will look for the classps: the wiki page about the Object factory need to be updated. It would be great if someone more articulate than me could do it ;-)
On getvanilla.com it still says "Latest version: 1.1.4; Released: Oct 21, 2007" by the way
eugen, I agree completely. It is my opinion that security and bug fixes should be released immediately (as versions like 1.1.4.1 or even just 1.1.4a, 1.1.4b, etc) and new versions like 1.1.5 or 1.2 should be for added features. But you don't have to wait for a release in order to fix them, you can always just follow this page and implement the fixes as soon as they are put on there, or even offer fixes for unresolved bugs
However I do agree that a better system would be great. A good thing about this forum is that you need to be approved in order to join, so that means voting-based systems are suited to it. We can easily make it so that if you are a member of this forum (meaning you are approved by the admins) you gain the ability to vote or "flag" an extension as outdated or buggy or broken, etc, and those flags or votes could show up in the add-ons section so that people are warned.
Similarly there could be flags like "verified" that have a big green tick to show that the extension has been tested by members and works perfectly, with a number next to the green tick to show how many members have verified it. Then there could be a smaller green tick stored over from the last version of the addon, so that say if someone's addon has 100 verifications and then they release a new version, they don't completely lose all those verifications, so users can see they have a good record of releasing a good extension.
Anyway I guess we should start a new topic for this if we are going to discuss it huh
Have you tried emailing the authors of those extensions instead of posting in the threads? With my extension Notifi I check the page regularly for new comments, but it is annoying to have to do it. In fact I will go make a suggestion now that I remember...
Also in response to the Google thing, I have never been one to care about things like that; if you don't want things to be publicly available then don't do them in public, simple. If a website asks for information you consider to be private then just don't submit that information.
I use Chrome now because Firefox 3 is buggy and slow and bloated, I was already planning to switch to Opera when Chrome came out and I like it better. I have also noticed huge speed improvements in JavaScript handling compared with other browsers, as you can see in this image it is nearly 7 times faster than Firefox 3
That also illistrates why we can't have a timer that marks extensions as outdated--I've got more than one that are over a year old, each downloaded more than a thousand times--yet they've never been updated and don't have any comments indicating bugs.
If you are using a buggy extension that has been abandoned and the author can't update it, ask them if they will contribute it to the Vanilla Friends project, so it can be adopted by community developers.