Vanilla 2.0.17 Released

cdavid

Hey, @Tim !

There seems to be a bug with the e-mail notifications system in the last version (and the version on VanillaForums.org -- are you using the latest version?). For example, I have bookmarked this discussion, but I don't receive any e-mails saying that "someone has commented on your bookmarked discussion" -- the other emails get sent, weirdly enough). I couldn't find any issue in GitHub, so I was wondering if you are aware of this issue and, if not, should I make a new ticket?

Thanks,

/cd

ffunnyman

It also looks like "header" categories are not handled sanely in that they appear clickable but will take you to an empty page instead of listing sub-categories.

this is because the concept has changed - a header category now is a category in itself. this is a bit confusing - especially as it lists the total number of posts in the left hand category list behind it, but when you click it it does not show all posts in there but only the posts that are posted directly in the header category. i struggle(d) with this myself.

I'm eventually going to write a patch to configurable have child cat discussions show up in parent cats but I'm not quite up to that yet.

jrapage

However we're getting a crash on resetting password. It happens on submitting the page where you get to enter the new password:

Fatal error: Nesting level too deep - recursive dependency? in ...\library\core\class.authenticator.php on line 122

I can't see a line 122 there, though. Any ideas?

I fixed this. See this thread:
http://www.vanillaforums.org/discussion/14945

Nobody else seems to have been bothered enough to comment on this, despite password reset being a critical feature!

Linc

@jrapage I can't get password reset to fail like you describe in 2.0.17.8.

Stash

Just on shared hosting so who knows how long this will last

Also, I've not tested each and every one of these, so use at your own risk. If things die, you're on your own. Just for testing purposes etc...

Have fun!

vanilla-core-2.0.17.8 from 2.0      - 1,354,991 bytes
vanilla-core-2.0.17.8 from 2.0.1    - 1,346,320 bytes
vanilla-core-2.0.17.8 from 2.0.2    - 1,346,325 bytes
vanilla-core-2.0.17.8 from 2.0.3    - 1,346,310 bytes
vanilla-core-2.0.17.8 from 2.0.4    - 1,325,103 bytes
vanilla-core-2.0.17.8 from 2.0.5    - 1,325,111 bytes
vanilla-core-2.0.17.8 from 2.0.6    - 1,325,096 bytes
vanilla-core-2.0.17.8 from 2.0.7    - 1,317,342 bytes
vanilla-core-2.0.17.8 from 2.0.8    - 1,317,351 bytes
vanilla-core-2.0.17.8 from 2.0.9    - 1,317,358 bytes
vanilla-core-2.0.17.8 from 2.0.10   - 1,315,375 bytes
vanilla-core-2.0.17.8 from 2.0.11   - 1,313,752 bytes
vanilla-core-2.0.17.8 from 2.0.12   - 1,009,798 bytes
vanilla-core-2.0.17.8 from 2.0.13   - 1,009,787 bytes
vanilla-core-2.0.17.8 from 2.0.14   -   471,059 bytes
vanilla-core-2.0.17.8 from 2.0.15   -   451,195 bytes
vanilla-core-2.0.17.8 from 2.0.16   -   451,191 bytes
vanilla-core-2.0.17.8 from 2.0.17   -   178,857 bytes
vanilla-core-2.0.17.8 from 2.0.17.1 -   178,861 bytes
vanilla-core-2.0.17.8 from 2.0.17.2 -   178,764 bytes
vanilla-core-2.0.17.8 from 2.0.17.3 -   178,732 bytes
vanilla-core-2.0.17.8 from 2.0.17.4 -   144,426 bytes
vanilla-core-2.0.17.8 from 2.0.17.5 -   134,094 bytes
vanilla-core-2.0.17.8 from 2.0.17.6 -    48,885 bytes
vanilla-core-2.0.17.8 from 2.0.17.7 -       892 bytes

MiguelTarga

teste

phreak

@Stash: Thanx man! Upgrade 2.0.16 > 2.0.17.8 worked great.

Stash

Good to know! Glad to help

DanDevine

I wonder what changes were made in the 2.0.17.9 update? I can' t find anything about the update?

luc

That's still a branch only in the git repo.

bobtheman

it shows .19 was released but no updates on this thread showing what the updates included.

luc

Nope, the master repo is still as 2.0.17.8, there is a branch to fix issues for 2.0.17.8, and a tag created for 2.0.17.9, but the master repo is not up to date yet. The branch is unstable_fix_2.0.17.8.

Linc

@bobtheman Nothing shows .19 anywhere. You're misreading.

@luc The main download is now for 2.0.17.9, it simply hasn't been merged into master yet, probably because of the weird merge order or they just didn't have time to do it yet.

Announcement is soon, it just got delayed slightly.

luc

@Lincoln As I don't use the download, but git fetch/merge, I didn't noticed that.
I merged the unstable_fix_2.0.17.8 yesterday evening (Europe time)

Linc

2.0.17.9 fixes a cookie theft vulnerability in user authentication. (Original post's release history has been updated).

I strongly recommend upgrading to this patch-point release as soon as possible.

Adrian

https://github.com/vanillaforums/Garden/commit/d1666b7b8456eea765833200ff45ebebf8f84992

so you I had to manually re-add in the minify or my users would be in trouble if they forgot their passwords.

Linc

@adriansonline That fix will be in 2.0.18. This was a patch-level release strictly for the security issue; it's otherwise identical to 2.0.17.8, meaning that Minify fix isn't there yet. Sorry for the confusion; we try to keep bigger stuff like that out of minor patch releases for minimum impact.

dan39

So, I take it these are the only changes from 2.0.17.8 to 2.0.17.9?:

https://github.com/vanillaforums/Garden/compare/Vanilla_2.0.17.8...Vanilla_2.0.17.9

Linc

Should be.

kkgamestudios

i don't understand the readme