It looks like you're new here. If you want to get involved, click one of these buttons!
This is an important security upgrade for all forums.
Download it: http://vanillaforums.org/addon/vanilla-core-2.1.6
7 file changed. See the code diff.
Summary:
Thanks to the team at ZeniMax Online Studios for disclosing the password reset issue and SQL injection vector.
Comments
thanks. just upgraded to 2.1.6 BTW, info message at top of screen also needs to be updated above to reflect new version 2.1.6
function request for next release... https://github.com/vanilla/vanilla/issues/2283
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
@Linc
Should this be an announcement?
Anybody know how to upgrade to 2.1.6 from 2.1.5 .do i have to download all the package again?
It is best to follow normal upgrade procedures.
grep is your friend.
@waplist
@x00 is right, but if you check the GitHub page, you can see the 7 updated files, and just upload those, especially as you have only just installed 2.1.5
Ok thank you
There is a bug in the Dashboard News feed that causes an announced discussion to disappear, so no, not if I want folks to see it beyond this site
Ah, OK.
I shall try to remember to bump it.
This reminded me of a need for a security tracker.
http://vanillaforums.org/discussion/28568/security-tracker
grep is your friend.
@linc: It's really cool to see so much progress around here right now. Thanx for the work!
VanillaAPP - Your native App for Vanilla // Press Theme is ready for Vanilla 2.3+ - Check it out! // Made by VanillaSkins.com
@whu606 I've added the Bump addon, so you can select "Bump" as an option from the Discussions list now.
OK!
I shall shelve my other 'bump' related gags...
Forwarded to the page index.php?p=/dashboard/setup.
database in the phpmyadmin is not created.
config has no blog entries, just white.
what's the problem?
best to start a new discussion. state what you did in the new discussion.
was this an upgrade or new install. put that in your new discussion as well.
hints for everyone upgrading or installing
https://github.com/vanilla/vanilla/blob/2.1/README.md
read the faq (all comments)
http://vanillaforums.org/discussion/28420/faq
read 2.1 release notes discussion and comments
http://vanillaforums.org/discussion/26685/vanilla-2-1-stable-released#p1
and this
http://docs.vanillaforums.com/developers/troubleshooting/
and this
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
@Linc
numerous people are getting this error upon upgrading.
may need to go in and manually fix.
http://vanillaforums.org/discussion/28583/upgrading-to-2-1-6-from-2-0-18
I had one person run
in phpmyadmin and go to your database and
and run /utility/structure again and it fixed it.
http://vanillaforums.org/discussion/comment/220312/#Comment_220312
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
@peregrine Is this something specific to 2.1.6, or just a general issue surfacing for the 2.0 -> 2.1 transition?
I'm not sure, but it involves upgrading from 2.0.x to 2.1.6
two people at least were upgrading from 2.0 .18.x - > 2.1.6
if you have a Tag table as a result of installing tagging plugin in vanilla 2.0.18
I haven't seen any one report problem before Gillingham reported problem
but 3 different people (have had the issue and posted a problem).
I wonder if they don't have drop index permissions - but that would probably result in a permissions error I would think.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
@peregrine OK, would you please file this as an issue? This should be fixed via the structure file & tested before and after with a full upgrade. I don't recall if the Tagging tables are core in 2.0.18 but that's a consideration too - whether the plugin is enabled.
when I saw the error
tagging was enabled in 2.0.18 and was disabled prior to upgrade and yes it is in the core in 2.0.18
https://github.com/vanilla/vanilla/issues/2291
https://github.com/vanilla/vanilla/tree/2.0/plugins
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
This change broke a custom plug-in I have. The plug-in does
$SQL->Where('d.ScriptID IS NULL');
onDiscussionModel_BeforeGet_Handler
. The result is:If I comment out the new line, it works again.
Some images not optimized.
The following need compression, percentage savings listed.
calendar.png 94.5%
cog-expander.png 15.6%
bubble-arrow.png 8.5%
connection-64.png 5.1%
dashboard-sprites.png 7.3%
72.gif 1.0%
usericon.gif 0.9%
arrow.png 0.8%
check.png 0.8%
buttons.gif 0.8%
75.gif 0.5%
74.gif 0.4%
5.gif 0.4%
77.gif 0.3%
62.gif 0.2%
56.gif 0.2%
18.gif 0.2%
103.gif 0.1%
109.gif 0.1%
45.gif 0.1%
8.gif 0.1%
pirate.gif 0.1%
59.gif 0.1%
@Anonymoose: Jep, TinyPNG rocks.
https://tinypng.com/
VanillaAPP - Your native App for Vanilla // Press Theme is ready for Vanilla 2.3+ - Check it out! // Made by VanillaSkins.com
Command line and drag and drop for OS X:
https://imageoptim.com/
Imageoptim provides lossless compression and integrates PNGOUT, Zopfli, Pngcrush, AdvPNG, extended OptiPNG, JpegOptim, jpegrescan, jpegtran, and Gifsicle.
Filed https://github.com/vanilla/vanilla/issues/2303
Okay, I may be missing a step, so hopefully a reply can get a good solid solution
I have VF 2.1.5 and I want to upgrade to 2.1.6
The REAME.md is very limiting, so these are the steps I performed:
1.) Backed up DB
2.) Created two locations:
/app/www/vanilla-2.1.5 which symbolic links to /app/www/vanilla
I expanded 2.1.6 to:
/app/www/vanilla-2.1.6
I fixed the permissions to be owned via nginx:nginx as the 2.1.5
I rsync'd the config.php from the 2.1.5/conf to the 2.1.6/conf directory
I rsync'd the plugins & applications that I had different from the standard install.
I fixed the /app/www/vanilla symlink to point to the 2.1.6 branch
I then attemped to load the: www.myforum.com/index.php?p=/utility/update
I kept getting the error on the website:
The update was not successful.
Any advice would be appreciated. Thanks!
.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
this tells me that the htaccess file is not correct and that pretty URL may not be true thus this outcome.
check that rewriteUrl is set to true in the config.php and check that the .htaccess file is correct and that
BaseRewriteUrl is not commented out with a # before BaseRewriteUrl /
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
check what vrijvlinder says but check your nginx rules.
nginx doesn't use .htaccess right, that is apache.
http://stackoverflow.com/questions/14927184/converting-htaccess-to-nginx-mod-rewrite
http://blog.martinfjordvald.com/2011/02/nginx-primer-2-from-apache-to-nginx/
http://blog.martinfjordvald.com/2010/07/nginx-primer/
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.