Not signed in (Sign In)

Vanilla: Vanilla 1.1.5a Released

Bottom of Page

1 to 50 of 101

- CommentAuthorMark
- CommentTimeSep 22nd 2008 edited
# 1
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.
- CommentAuthorMark
- CommentTimeSep 22nd 2008
# 2
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.
- CommentAuthormpowrie
- CommentTimeSep 22nd 2008
# 3
Congrats! I can't wait to install it and see the new goodness
- CommentAuthorpbear
- CommentTimeSep 22nd 2008
# 4
Congrats on the release! B)

... and big thanks from all of us who can't code our way out of a nested for-loop.
- CommentAuthorDinoboff
- CommentTimeSep 22nd 2008
# 5
@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 ;-)
- CommentAuthorWallPhone
- CommentTimeSep 22nd 2008
# 6
Hip-Hip ... Hurray!
- CommentAuthorSubJunk
- CommentTimeSep 22nd 2008
# 7
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
- CommentAuthorDinoboff
- CommentTimeSep 22nd 2008
# 8
You have to refresh the page.
- CommentAuthoreugen
- CommentTimeSep 22nd 2008 edited
# 9
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
- CommentAuthoreugen
- CommentTimeSep 22nd 2008 edited
# 10
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)
- CommentAuthorSubJunk
- CommentTimeSep 22nd 2008
# 11
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 :)
- CommentAuthorpalmdoc
- CommentTimeSep 22nd 2008
# 12
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.
- CommentAuthorSubJunk
- CommentTimeSep 22nd 2008
# 13
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 ;)
- CommentAuthormpowrie
- CommentTimeSep 22nd 2008
# 14
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.
- CommentAuthoreugen
- CommentTimeSep 22nd 2008 edited
# 15
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.
- CommentAuthorSubJunk
- CommentTimeSep 22nd 2008
# 16
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
- CommentAuthorpalmdoc
- CommentTimeSep 22nd 2008
# 17
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
- CommentAuthorSubJunk
- CommentTimeSep 22nd 2008 edited
# 18
palmdoc, can you please try replacing /extensions/Notifi/default.php with this one and let me know if it fixes the problem?
- CommentAuthorWallPhone
- CommentTimeSep 22nd 2008
# 19
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.
- CommentAuthorpalmdoc
- CommentTimeSep 23rd 2008
# 20
@SubJunk - it works now thanks.
- CommentAuthorSubJunk
- CommentTimeSep 23rd 2008
# 21
Thanks palmdoc I will update the extension now
- CommentAuthormicz
- CommentTimeSep 23rd 2008
# 22
Well done guys!

Dinoboff, may you post on Vanilla-friends the usual changed-only-files package?
Thanks.
- CommentAuthorDinoboff
- CommentTimeSep 23rd 2008
# 23
@ micz:
http://vanilla-friends.googlecode.com/files/vanilla-upgrade-1.1.4-to-1.1.5.zip
- CommentAuthoreugen
- CommentTimeSep 23rd 2008 edited
# 24
@Wallphone:

"The security issue wasn't known for a year--it was known for a couple months."
Are you kidding me? "only known for a couple of months" - how long do you think a script kiddie needs to start hacking a server after a security holw is found? - RIGHT! He needs seconds ... not months! Even more if all the vulnerabilities are posted on the forums own bug tracker ^^

"...there was already a public release canidate avaliable when the issue became public knowledge."
Yes, sure, and thanks for it. BUT it is NOT our job to check every bugtracker or hackerforum or security webpage of the heavy amount of software we are all using! (or do you check the microsofot knowlegebase every 24 hours beacuse there are 5 more bugs and security hols found in M$ products? Dont think so. BUT OF COURSE IT IS our job to use the integrated upgrade/update feature to see if any update/fixes are avaialble - that's what we can do regularly.

"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."
Thats absolutly correct! No question - but on the other site there are 20 times more addons which are buggy, outdated and need to be dumped, deleted or updated/continued! Let's say 1 out of 5 addons will even work after 5 vanilla updates and will even work 2-3 years later after published. so what? where does this fact will fix the general problem?

"f 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"
Sorry, but its not very usefull to OUTSOURCE everything ^^ Whats next? Vanilla Friends will develop vanilla instead of mark or vanilla itself? Any new Vanilla Addon Friends will keep outdated and buged addons alive? Any new sourceforge.net project will develop aqny new features or semi-vanillas? whats next???
Sorry again, this will kill vanilla over short or long time! This is the wrong progression as vanilla should stay in one and should be central.
WE CANT check 5 pages/projects daily to keep vanilla, vanilla addons and security bugfixes updated ... this kind of development will even smaller the vanilla community until only a few "freaks" who invest 4 h daily on vanilla will use vanilla at the end ... but i think 60-90% of the vanilla users are CASUAL forum users - wanna loose them all? that would be very sad :(

Sorry thats just my opinion and i think many of the vanilla fans think similar!
I dont wont to be rude or agressive with my words - sorry if its sounds like, english just is not my native language.
I LOVE VANILLA ANY EVERYONE WHO HELPS KEEPING IT ALIVE & UPDATED! /THANKS!!!!
but the actual splitting of development plus the additional fact of plenty of buged and outdated addons plus the fact that security updates of vanilla taking months ... thats the absolutly wrong direction we are going i think.

We need solutions! Not the beginning of the end :(
Why should someone use vanilla with longtime open security holes and fort years buged and outdated addons when there are plenty of bigger forums and communitys out there he could use without checking 5 pages and projects to be sure he is up to date and safe?

Eugen
- CommentAuthorDinoboff
- CommentTimeSep 23rd 2008 edited
# 25
@eugen: The security issues have all be reported in august and fixed quickly. Mark was on holiday at the time and couldn't release 1.1.5 (but a release candidate was available).

We delayed the release again at the start of September to try to fix an other security issue. Since it took 3 weeks we shouldn't have waited for it, but it did not seem it would take so long at the time.

About a 1.1.4a release, we do not maintain a branch for last minor release, but know that we are heading for Vanilla 1.2, we will probably soon open a 1.1.x branch.
- CommentAuthormicz
- CommentTimeSep 23rd 2008
# 26
Thanks Dinoboff! :)
- CommentAuthorDinoboff
- CommentTimeSep 23rd 2008 edited
# 27
Subjunk reported a problem with the integrity check for a fresh installation. If you have the same problem, just delete appg/md5.csv and let us know.
- CommentAuthorDinoboff
- CommentTimeSep 23rd 2008 edited
# 28
Also, with Vanilla 1.1.5, one of the field in the Lum_User table need to be updated. Vanilla do it automatically but need to edit conf/settings.php. If you don't want Vanilla to alter the User table on each load, make sure that $Configuration['DATABASE_VERSION'] = '2'; has been added to conf/settings.php. Edit it manually after some few requests on your forum if for what ever reason Vanilla doesn't have write permission on your setting files.
- CommentAuthorbochenn
- CommentTimeSep 23rd 2008
# 29
Dinoboff, the Lum_User table field was already present in Vanilla 1.1.5 RC4?
- CommentAuthorDinoboff
- CommentTimeSep 23rd 2008
# 30
Yep, it was in 1.1.5's rc3 and rc4
- CommentAuthorDinoboff
- CommentTimeSep 23rd 2008
# 31
they have the same update feature; if you have used one of them the field (the password field) has been changed and $Configuration['DATABASE_VERSION'] = '2'; has been added to conf/settings.php
- CommentAuthorbochenn
- CommentTimeSep 23rd 2008
# 32
Guys, is there a guide on how to upgrade from Vanilla 1.1.5 RC4 to 1.1.5 final?
Thanks
- CommentAuthorXK
- CommentTimeSep 23rd 2008
# 33
Thank you!
- CommentAuthorDinoboff
- CommentTimeSep 23rd 2008
# 34
@bochen: no, but there is nothing special. Using ssh, I personalty just copy every 1.1.5 files over the old installation.
- CommentAuthorDinoboff
- CommentTimeSep 23rd 2008 edited
# 35
Here is the list of files changed between rc4 and the final release:
appg/md5.csv appg/settings.php appg/version.php setup/installer.php library/Framework/Framework.Class.Email.php library/Framework/Framework.Class.DirectoryScanner.php library/Framework/Framework.Class.IntegrityChecker.php
- CommentAuthorsamsoom05
- CommentTimeSep 23rd 2008 edited
# 36
Congrats!
- CommentAuthorWallPhone
- CommentTimeSep 23rd 2008
# 37
@Eugen

I agree it's not a perfect world, I anticipate word of a better solution. In the meantime, things will progress the same--the best way we have.
- CommentAuthorsparky
- CommentTimeSep 24th 2008
# 38
I got the following error message when signout after upgrading from 1.1.4 to 1.1.5:

Some problems were encountered
Can you please confirm your would like to sign out?

anyone else have this issue? How do I find out what is wrong? thanks in advance.
- CommentAuthorDinoboff
- CommentTimeSep 24th 2008 edited
# 39
@ Jun: Do you always get the message or just some time?

Some time is normal. Vanilla just want to be sure you want to log-out and that it is not a CSRF.
If you always get it, try to re-upload themes/menu.php. If you are using a theme, it might need to be updated.
- CommentAuthorsparky
- CommentTimeSep 24th 2008
# 40
Dinoboff: I always get this error. If I revert back to 1.1.4, I do not see this message any more (had to restore the old database). The menu.php is uploaded. Note I do not see this error message when I log off this forum (it uses 1.1.5 as well). Anything else should I try? thanks.
- CommentAuthorDinoboff
- CommentTimeSep 24th 2008 edited
# 41
Which theme are you using?
Can you give me the address of the forum?
- CommentAuthorsparky
- CommentTimeSep 24th 2008
# 42
Thanks Dinoboff. I am using tabled theme. After I switch to back to the default vanilla theme. The problem is gone. I do not have an external site yet (just on my own PC), my ISP blocks the 80 port. It will take me sometime to put on another port.
- CommentAuthorXK
- CommentTimeSep 24th 2008
# 43
Thanks for the upgrade package Dinoboff!
<3

I've applied it to my sandbox copy of my live forum. What are the suggested checks before applying the changes to the live site? Drive it around and if nothing is broked, apply?
- CommentAuthorMark
- CommentTimeSep 24th 2008
# 44
I've added the 1.1.5a package to getvanilla.com, posted an announcement on Swell, and updated the updatechecker for lussumo.com.
- CommentAuthorDinoboff
- CommentTimeSep 24th 2008 edited
# 45
@XV: Apply this one as well:
vanilla-upgrade-1.1.5-to-1.1.5a.zip

Check your theme need update; the following files have been changed:
themes/account_preferences_form.php themes/categories.php themes/comment_form.php themes/comments.php themes/discussion.php themes/discussion_form.php themes/discussions.php themes/menu.php themes/people_foot.php themes/people_signout_form_nopostback.php themes/search_results_comments.php themes/search_results_users.php themes/settings_update_check_validpostback.php

If you are using a customized authenticator, check login/logout/change-password/reset-password are still working.
- CommentAuthorSubJunk
- CommentTimeSep 24th 2008
# 46
I just tested 1.1.5a with a fresh install and it fixes the error with the integrity check I reported. Thanks for the fast release, great job.
- CommentAuthorvanoob
- CommentTimeSep 25th 2008
# 47
hello, just a note, vanilla 1.1.5a is still reporting as vanilla 1.1.5.
- CommentAuthorDinoboff
- CommentTimeSep 25th 2008
# 48
What do you mean?
Which part of vanilla shows 1.1.5 and not 1.1.5a?
- CommentAuthorBruceD
- CommentTimeSep 25th 2008
# 49
Hi Dinoboff,

I just downloaded 1.1.5a and the appg\version.php states:
define('APPLICATION', 'Vanilla');
define('FRAMEWORK_VERSION', '1.1.4');
define('PEOPLE_VERSION', '1.1.4');
define('APPLICATION_VERSION', '1.1.5');

When I sign in, it also states 1.1.5 instead of 1.1.5a

When I trigger the update check it tells me, that there is an update 1.1.5a avaible :(
- CommentAuthorDinoboff
- CommentTimeSep 25th 2008
# 50
I contacted Mark about it. Thanks Bruce.

You can download it there on the meantime:
http://vanilla-friends.googlecode.com/files/vanilla-1.1.5a.zip

1 to 50 of 101

Lussumo Community

Categories

Feeds

Vanilla: Vanilla 1.1.5a Released

Update