Suggestion for calculation rule settings

[jjk]

A suggestion for Calculation rule settings.

Yesterday I wondered almost all day why my calculation rules stopped working again. This morning I found that many of them simply expired, probably because one of the SVN updates changed them from expiry "never" to yesterday's date. If a rule expires, the expiration is easy to miss because there is no notice (i.e. blinking in red) or warning in advance. This probably will cause trouble for shop owners in the future, because when the expiry date is reached all of the sudden the shop's prices are totally wrong.

Therefore my suggestion would be to add the "never" expiry date as a default again and eventually build in some kind of warning that notifies the shop owner that a rule is expiring soon. Currently one can only pick a date from the date picker when setting a rule. If no date is selected, a new rule defaults to today's date as the expiry date.

[Milbo]

Yesterday I wondered almost all day why my calculation rules stopped working again. This morning I found that many of them simply expired, probably because one of the SVN updates changed them from expiry "never" to yesterday's date.

Yeah that is shit. Patrick fixed the dateformat error that way. But it is not a solution to enter always a late date. I hate that myself.

[jjk]

Perhaps a relatively easy fix for this would be a default value of "Today's date + 50 years" instead of "Today's date" :-)

[Studio 42]

Hi,
we have add a reset button to the date entries.
simple  click on the image next to the date, to reset it

[jjk]

Hello Electrocity,

I've noticed that the button in revision 5015 already, but reverted back to revision 5012, because commit 5013 is causing the following error in the frontend views:

Code Select Expand

Notice: unserialize() [function.unserialize]: Error at offset 0 of 20 bytes in ...\administrator\components\com_virtuemart\helpers\config.php on line 378

[Milbo]

jjk should be fixed, please try now

[jjk]

Not really - Now I have the same error message in the backend, too.
See screenshot below.

[attachment cleanup by admin]

[Milbo]

Delete your config file and store your config. The error always means that the stored config settings do not fit to the rest.

[jjk]

Ah - ok, that did work. Thanks!