php-residence 0.5.5 changelog and notes

[marco]

0.5.5 (14/11/2005)
======================
-don't show reservations of previous year in all reservations table when all these reservations end
-possibility to automatically create the new year with the first login of the year of any user
-possibility to modify a reservation of previous year ending in current year from current year
-when modifying a reservation, updade also the corresponding next year reservation if present
-do not permit inserting reservations for next year if asked final date exists in next year
-delete imported reservations from previous year when importing in new year
-changed assignation in assignment in english translation
-possibility to use an extra cost as minimum stay (associate cost if "always" on)
-fixed bug: couldn't modify permitted periods of extra costs
-fixed bug: "continue anyway" didn't work when inserting reservations
-bug: when going back from inserting a reservation, a list of apartmens was selected if a rule 2 rate was
-possibility to change the day of end/start week with daily periods in tables
-added small link to show all dates in menus
-show availability overview in availability template also when requested period is full
-possibility to show only intervals of dates in some periods in dates menus
-fixed bug: not possible to restore backups with users with german language
-fixed bug: no availability overview customization for normal users


When creating a new year now the imported reservations that are completely in the new year are deleted from previous year, so if you afterwards delete the new year you will loose those reservations, differently from before. Making a backup before the creation of the new year is always a good idea. You will see also other changes regarding new years, now it's easier to manage reservations between years and there's a preference to create the new year automatically at the fist login of the year, so you not even notice it.

Another change of behaviour is for extra costs that are associated "always" to a fare and for a minimum amount of days. In previous releases the cost was not associated if the reservation was shorter than the minimum days, now it gets associated anyway and gives you an error, actually not letting you to insert the reservation. This way you can use these costs as a minimum stay (or maximum if you set it so). To get the old behaviour it's sufficient to change the cost from associated "always" to "if possible".

The intervals in dates (you set them in "configure and customize") allow you to have weekly periods between daily ones, for example. Anyway there's now a small link near the dates that lets you easily use the dates that are not shown. This link for normal users only appears if the user has the privilege to change his own customizations, so this is a new way to limit the periods that can be used.

Lastly notice that this is not the planned major release 0.6. You can expect that one not before March/April I think.

Ciao,
Marco