Thanks Dino. Is this in a README file or elsewhere? This seems like a pretty harsh gotcha for anyone who is using svn to keep their Vanilla install updated.
Aren't there version...milestones?...in the svn for people who want to use it for updates? Obviously keeping your forum in sync with the dev svn isnt advisable.
There are tags, but the last tag has the same structure as the trunk.
@ rel1sh: Did the update deleted the content of your extension and conf folder?
What should be put in the readme file?
If someone else has to update its svn repository with the previous structure, he should switch his working copy to http://lussumo.com/svn/vanilla/trunk/src/ (or http://lussumo.com/svn/vanilla/tags/Vanilla-1.1.4/src/).
...Ant build directives. Am I crazy, or is php still an interpreted language that doesn't need to be built?
Build != compile. It is quite normal to use make/ant to check the syntax of interpreted source, and package it for distribution. It's also common for build scripts to include things like unit tests and document generation.
@Dinoboff: It didn't delete any directories which contained files I had modified, only the php files that were in trunk before. I had the trunk checked out so it installed what NOW exists in the trunk into my forum directory (build, src, etc) and accessing the forum URL was bunk since all the php files are now in trunk/src.
In the readme (or changelog) it would be nice to have a note to anyone tracking the svn trunk that they should svn switch their working copy to trunk/src via a command like: % svn switch http://lussumo.com/svn/vanilla/trunk/src /path/to/vanilla/install I realize anyone using Vanilla in a 'production' environment should be using the tags anyway, but the heads-up would've been nice.
I just updated mine from version 1.1.2 to 1.1.4
1. I followed instructions here http://lussumo.com/docs/doku.php?id=vanilla:upgrading
Uploaded all the files from version 1.1.4 listed here ... Upgrading from Vanilla 1.1.2 to Vanilla 1.1.3 PLUS /appg/version.php (you'll get a page error if you don't upload /appg/version.php)
2. Lastly, I uploaded all files listed here "Upgrading from Vanilla 1.1.3 to Vanilla 1.1.4"
3. Done
OK my last question was a bit lame and did not deserve a reply as the answer is clearly set out in the upgrade page. So i do apologise.
However, I'll now try some slightly less brain-dead questions on you all. By the way, I am upgrading from 1.0.3
1). Can I connect a test forum (residing in another folder) to the same database as my active forum (the one that I want to upgrade) without causing any upset in the operation of same? If I can, then It would allow me to test whether the extensions I am currently running are compatible before I go for the grand slam.
2). When I do upgrade, would it be advisable to turn off all the extensions in the administrators settings area just prior to upgrade and then turn them back on one at a time once the core upgrade is running? This way it might be possible to weed out any that are not happy with the new version.
3). Finally, is there a list anywhere of extensions that are proven to be stable on the 1.1.4 system
Yep you can upgrade directly to 1.1.4. The know issues when upgrading problems with bad php session settings and bad cookie settings on the forum.
For the extensions look at the extensions pages, it should tell with which version they are compatible. All extensions compatible with 1.1.x should be compatible in 1.1.4
I'm now running a test of 1.1.4 alongside 1.0.3 and I have two points of feedback:
The new version seems to run at about half the speed of the old one. (could that be a symptom of sharing a database?
Also I thought part of the security upgrade was to hide the users e-mail address in the login reminder form but I see it still displays the server address which i would imagine is just as useful to the spammers!
I have timed it with the Safari browser on the Mac:
Average 17 seconds for 1.1.4 to refresh
Average of 7 seconds for 1.0.3 to refresh
Firefox is faster - couple of seconds on 1.0.3 but not by much on the new upgrade.
Could it be an incompatibility with an extension or is it just the extra security measures going on? I'm a bit worried that new visitors to the forum will get bored with waiting and looking at a blank screen for 17 seconds or more and clear off before the forum is displayed! Firefox error reporting suggests parsing value errors around 'display' in vanilla.print.css and vanilla.css whatever they are.
Interestingly Internet Explorer 5.2 on the Mac cannot make head or tails of the forum layout.
Explorer 5.x is no longer supported, abandoned even by its creators, why not let it rest in peace filed away in the big trash can in the sky? I'm slapping my head wondering what possible motive one would have using such outdated software by choice.
I just fired it up to see how the forum displayed with it. I assume there are a lot of people with older macs that rely on it. They won't think much of Vanilla though as it displays dreadfully so let's hope you are right james and everyone has thrown 5.2 for the mac in the bin.
However it is the job of any self respecting site developer to test on e=very possible browser isn't it?
Every possible current browser perhaps. Have you tested your site in IE1, 2, 3 and 4? Or netscape? Building perfect code is hard (impossible) - I'd say aim for IE6&7, Firefox, Opera, Safari.
Hello,
I installed Vanilla yesterday and I would like to ask the experts few questions.
First, is it possible to change the overall forum font to VERDANA size 2? As of you can see here .... all of these comments are in TREBUCHET MS font, i think. I would like to change my overall forum font to VERDANA with size 2.
second, how do you install addons? i installed some and all of them are good, but i would like to install those TEXT WYSIWYG editors ... their installaion is different than other extensions or what? thanx
Comments
@Dinoboff: It didn't delete any directories which contained files I had modified, only the php files that were in trunk before. I had the trunk checked out so it installed what NOW exists in the trunk into my forum directory (build, src, etc) and accessing the forum URL was bunk since all the php files are now in trunk/src.
In the readme (or changelog) it would be nice to have a note to anyone tracking the svn trunk that they should svn switch their working copy to trunk/src via a command like:
% svn switch http://lussumo.com/svn/vanilla/trunk/src /path/to/vanilla/installI realize anyone using Vanilla in a 'production' environment should be using the tags anyway, but the heads-up would've been nice.
For the extensions look at the extensions pages, it should tell with which version they are compatible. All extensions compatible with 1.1.x should be compatible in 1.1.4
Explorer 5.2 on the Mac is not a valid browser any more, mind you my wife still uses it for her banking!
I'm slapping my head wondering what possible motive one would have using such outdated software by choice.
Posted: Saturday, 2 February 2008 at 6:08PM