If you are running Savane < 1.0.4, you should run sql scripts included in savane/update/1.0.4, as described in savane/update/README.
These scripts will handle the trivial changes on the database needed.
WARNING: do not run savane/update/1.0.4/clean-usertable.sql

Also, take care to the section [SITE SPECIFIC CONTENT] of the
ChangeLog below, it will tells you which files should be added in your site specific content directory.

Bugs related to notifications no longer reproducible, probably due to others Yves Perrin's bugfixes on the same code part (closes: bug #273, bug #354, bug #399).

During the installation process, give some advices when starting the frontend (tell to register a project, etc), autodefine the unix group name of the registered project (according to the configuration), deactivate tests on the group name (that would lead to a refusal of "admin" for instance).

Implement a Posting Restriction model, following the

permission model. Projects admins can forbid posting item to users depending on their authentication level (member, logged in, anonymous). It works exactly like others permissions (configuration at the same places, possibility to rely on group type setting...) -- as a matter of fact, in does not really work like the current implementation running at CERN, but the spirit is the same and it offers the same possibilities, and even more. It applies to the usual trackers (task, support...) and news tracker (closes: bug #664, bug #665).

Links to unavailable action are now printed, but in a specific manner. utils_link() has been added for that purpose (closes: bug #685).

Inform user when he's using a theme non-compliant to latest Savane CSS Guidelines. If the theme is the default theme, even tell user to submit a support request for the installation he's using.

Switch to XHTML, use CSS more extensively. Some pages may be non-compliant, feel free to submit bug reports. Some <tables> should still be replaced by <div> and most forms are not XHTML standard valid. Apart from the "cleaning" side of the task, it gives themes more freedom (closes: bug #683).

New theme added, called "right", that specifically print the main menu on the right of the page

Savane CSS Guidelines 1.10 comes with a base.css.in, special CSS file that have no purpose apart being imported by others themes, providing the basic needed classes required for minimal layout lisibility.

Now superuser are considered as normal users as long as they do not click on the menu link "Become superuser". This is like "su" principle on unix systems: no need to be root everytime, it can lead to mistakes and misunderstandings; you just become root when you need to (closes: task #347).

After login, always get back we're you were. Do the same in case of su logout.

Feedback now pop-up in fixed-position boxes. As result, their visibility should be greatly improved.

Session management: users can see remaining open sessions and trash them if obsolete (closes: task #112).

Incorporate CERN field values transitions: projects admins can determine whether it is possible to change a specific field from a value to another. For instance, you can force technician to pass a specific "status" stage wheee the item got reassigned to someone else (closes: bug #677).

Add the possibility to set multiple transition "from value any to this value" (closes: task #749).

* Change wording in "My" area, using more frequently "I", since the area is called "My" -- we'll have to study the impact of this change on users.

Now locale textdomain is "savane", no longer "savannah".

"Secure" groups set active feature page. It avoids project admin to play will post variables to eventually activate tools the local admin did not activate. This change was made necessary by the addition of the possibility for project to configure dir_download,

if the local admin allowed it.

Allow users to get a daily/weekly/monthly reminder of item assigned to them of priority > 5. Allow admin to send a daily/weekly/monthly reminder of item assigned to project members of priority > 5 (closes: task #209, task #750).

Note: this bug caused "planned close date" and "planned starting date" to be stored with a timestamp -1 day.

Add direct pointer to the currently shown item in the headers where item #nnnn is printed. Sometimes, you may want to refresh the page, for whatever reason, without doing reload.

In select boxes, when using trackers, field value are sorted by label, if the rank is not enough. This is interesting if you have several values with the same rank (closes: bug #526).

Ignore incomplete registration when testing if a sys group name already exists in the database, during project registration. Risks of a name clash seems near 0, while not doing that require maintainance, since some people interrupt registration and try to redoit later with the same name. And even if a name clash happens, admins should notice it during approval (closes: bug #332).

Give some tips after login failure.

Filelist allow subdirectories listing.

Cookies always include the full sysdomain; this make possible concurrent sessions on different servers that got the same main domain. However, it makes impossible to share cookie between http://www.domain and domain.

Number of latest group approved by per group type now depends on how many groups type you have. If you have more than 25 group types, no more than 2 groups per type will be showned on the front page. If you have less than 3 group types, 25 groups will be shown per group type.

Configuration tool: ignore by default questions related to webalizer and mrtg integration. These are nowadays useless, since apache is no longer supposed to be able to this kind of data, for security reasons, on most installations.

Copyright (C) 2004-2006, the Gna! people. Posted items are owned by whoever posted them.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.