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.
Options

Vanilla 1.1.5a Released

MarkMark Vanilla Staff
edited March 2009 in Vanilla 1.0 Help
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.

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.
«1345

Comments

  • Options
    MarkMark Vanilla Staff
    Personal Note
    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.
  • Options
    Congrats! I can't wait to install it and see the new goodness
  • Options
    Congrats on the release! B)


    ... and big thanks from all of us who can't code our way out of a nested for-loop.
  • Options
    @mpowrie: it is just a maintenance release (with important security fixes). However one features should please extension developers; you now can overwrite controllers and classes created before the extensions are loaded.

    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 class

    ps: the wiki page about the Object factory need to be updated. It would be great if someone more articulate than me could do it ;-)
  • Options
    Hip-Hip ... Hurray!
  • Options
    Good job everyone, great release. I'm installing it now.
    On getvanilla.com it still says "Latest version: 1.1.4; Released: Oct 21, 2007" by the way
  • Options
    You have to refresh the page.
  • Options
    edited September 2008
    Great! I just updated manually from 1.1.4 to 1.1.5 just 20 seconds ago and still everything seems to work fine ;) Im glad and very happy and seriously relieved that all the security problems and holes are fixed now! But... 1.1.4 - released Oct 21 2007 1.1.5 - released Sept 22 2008 In cases of security problems and their fixes there should be an update released earlier then 1 year after the last has been released. Hasn't to be a big update then, but if a security problem is detected a mini-update/fix should be published as soon as possible, even just one file has to be replaced. Just my opinion :P Any known issues and problems with other styles (using europeaftertherain) or any extension yet? Greetings Eugen
  • Options
    edited September 2008
    Another little bit "off topic" but surely helpful: There is a massive amount of extremly outdated and since long times not continued & developed addons. There should be some moderators (or even Mark) who should do a big clean up there. An idea for the future: If an addon is not updated or bugfixed longer then (lets say) 6 months, it should be kinda disabled or get an fat "outdated" sign. I'm using on my own forum a lot of very nice addons, but most of them are buged, outdated and noone cares about, even the discussions of this named addons are full of complains and bug reports and help requests. Just an example: There are 2 member list addons, both are not working 100% and are buged like hell as they are developed years ago and are not up to date. in this case someone should program a new one and the two old ones should be "deleted". Just an example, but i could call you a list of 30 realy good and helpful addons which are buged and nooney cares about since months ... :( Just wanted to mention that there should happen something ... maybe ... thank you! Keep up the good work - i love vanilla and i hope mark will continue vanilla and sometime will get more time again for his baby ;) Eugen (sorry, english isnt my native language)
  • Options
    Ah dino that would do it ;) I just started using Chrome (amazing JavaScript speed benefits, I really like it) and it didn't refresh automatically, I'm used to Firefox doing that. Hopefully they improve that.

    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 :)
  • Options
    Haven't upgraded yet but just wish to say thank you to all developers. It's a fun forum and a great community. I just sent in my donation. Keep up the good work.
  • Options
    eugen I don't think the solution would be to base the "outdated" sign on how long ago it was updated, because there are extensions that were updated over 2 years ago and still work perfectly (for example the one they use on this forum, Legends.
    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 ;)
  • Options
    Eugen: I agree completely with the outdated plugin problem. (Sorry to continue the off-topic conversation!) Perhaps these plugins themselves could be turned into collaborative projects complete with SVN management and a wiki for workarounds or "watchouts"? This way, if the original author loses interest in their plugin but the general community still wants to maintain it, the plugin can keep updated? This is fresh on my mind after wrangling with a particularly cool but outdated plugin for the past few days on my forum.
  • Options
    edited September 2008
    SubJunk: I agree, whatever, something must happen - i dont care which system pr improvement, but in my opinion it cant be as it is atm. :( And i did already 1 month ago: http://lussumo.com/community/discussion/8584/request-member-list-addon-needed-addon-cleanup/#Item_1 But as on most of the threads or questions or bug reports or addon problems: it takes weeks or months for any response, if there is even any response :( Thats the only thing i hate on vanilla :P Else i realy love it, vanilly is *LOVE!* but the community to small and the response to addons, addon bugs, addon developing, and so on sometimes realy sucks :( thats sad... If i check my participated threads ( http://lussumo.com/community/?View=ParticipatedThreads ) there are 15 threads where i asked something, posted bugs or got improvment ideas. mhhh lets say that i got responses and feedback on FOUR of em .. the rest its "dead" . since months ... no feedback, no response, no comments, nothing ... thats realy annoying and making me sad as vanilla is to great to be so "lamed" ... But sorry again for the off topic, just a good thread to mention it again i think :P hehe ... Vanilla rocks ... sure ... hopefully for ever ... and there are several realy good ppl working on it and helping others, but there are still some things like mentonied above who should be fixed, improved or brainstormed ;) VANILLA 4 EVER! Edit 1: SubJunk: I totaly agree also with your post before (#11) - 100%! (about the security hotfixes should be emmediatly published). But you should keep it on firefox, chrome sucks and is just another "googleisation spytool" who wants to dominate us. :/ Google yet knows more about you as your own mother! Think about it ;) Edit2: mpowrie: dont worry, as you see there seem to be a lot of people beeing annoyed by this "buged and outdated addons" problem.
  • Options
    To eugen:
    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
  • Options
    Hmmm. After upgrading I am getting this error: Technical information (for support personel): Error Message An error occurred while sending the email. Affected Elements Email.ServerParse(); The error occurred on or near: Couldn't get mail server response codes. I checked the SMTP settings and they are unchanged. Looks like I have to disabel Notifi until it is resolved
  • Options
    SubJunkSubJunk ✭✭
    edited September 2008
    palmdoc, can you please try replacing /extensions/Notifi/default.php with this one and let me know if it fixes the problem?
  • Options
    The security issue wasn't known for a year--it was known for a couple months. Thanks to the security researcher who found the issue, there was already a public release canidate avaliable when the issue became public knowledge.

    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.
  • Options
    @SubJunk - it works now thanks.
  • Options
    Thanks palmdoc I will update the extension now
Sign In or Register to comment.