What need to be added?

I did this last time and some things didn't work because, for example, there were new/modified definitions in the css file and this wasn't listed as a "changed" file.

Of course I'd make a backup first, did that last time too then, when I put things back, permissions got all stuffed up, some extension corrupted the the config file and to cut a long story short, I spent a day and a half fixing things back to the way they were.

Pardon me if I understand serafino's concerns.

Missing files in the the changed file list should not happen again; we get the list from the svn and there is at least two people checking that the list on the wiki is correct.

But really, you should upload all the core on each update - especially if you can use ssh for the transfer (sftp is as easy to use as ftp and won't corrupt your files). If you have some changes in the core files, you should use a svn repository to track your changes and merge changes in the core with your version of Vanilla.

The only problem is with extension. You can't know if they are compatible. We do our best to not break anything between each 1.1.x release, but there some stuff we can't foreseen (e.g. the Notify bug that hasn't any bad effect before 1.1.3). You should check they are compatible with your extensions on your testing forum before upload on your server. We will also try to release beta and release candidate between each stable release, so that user and developers can test them in advance.

Guys, I'm not blaming anyone, I understand this is part & parcel of the upgrade process.

Nobody's fault but mine if I modified core files, I have kept a record of such modifications but they are many and wide-spread and will take some time to re-do, re-test and re-adjust I'm sure.

Being very time-poor these days, it's not an easy thing to do.

As for sftp... something else to learn and deal with on another day!

Maybe I'm not following the recommended process here, but I had a test forum to which I had checked out a copy of Vanilla from: http://lussumo.com/svn/vanilla/trunk

Upon updating, it deleted all the php files in the root of the forum and installed a build, src, and dist directory, along with files that appear to be Ant build directives. Am I crazy, or is php still an interpreted language that doesn't need to be built?

I was using trunk as the directory to svn update against so that I could easily upgrade to the newest version and test. Is there another recommended directory in the repo which I should use for this?

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.

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.

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

And yes, you can run two vanilla's off one database.

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.

No OS 10.4 but the browser works on most internet pages

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?

Sorry, I seem to have caused things to wander off the point a little. My point/question was why does this build seem slower?

themes/vanilla/styles/default/vanilla.css and people.css are the files you want to edit, you will see Verdana already there, just move Trebuchet MS after it in the list.

For the editors, there should be a readme alongside the extensions that explain any additional steps that may be necessary.

I am having this error when trying to sign-in:

Notice: Undefined index: f0fe311a21e33ec91be4a6df34d8604d in /home/content/a/b/a......./library/People/People.Class.Joomla10x.Authenticator.php on line 38

Notice: Undefined offset: 1 in /home/content/a/b/a/....../components/com_jetigen/library/People/People.Class.Joomla10x.Authenticator.php on line 41

I have installed the latest version.

How did you solve the problem?