Closed instantflorian closed 10 years ago
Have you tried to re-set the date preferences?
Ah, That and logging off/logging on did the trick. Thank you.
Well, that's a workaround, but it's still a bug.
This happens if a user has no settings yet. Cause it that initialize.php
sets the key twice:
REGISTER -CAT_DEFAULT_DATE_FORMAT- -%d.%m.%Y-
REGISTER -CAT_DEFAULT_DATE_FORMAT- -d.m.Y-
Second is the old default date format for WB and LEPTON. I don't know why this happens yet.
I'm really confused, it seems to be a problem not in BC, but with the mysql_* methods used. There are two keys with similar names:
DEFAULT_DATE_FORMAT
CAT_DEFAULT_DATE_FORMAT
The CAT* is found first (as sort order is by name), so fetchRow() returns the correct values. But in the next iteration, the OTHER value is retrieved, though the key ist without CAT*
???
At least, I found that I was looking into the wrong DB. oops In fact, the key is set twice in the settings table, which is caused by an error in the upgrade.php.
In Backend & Frontend view date placeholders appear instead of values. I'm quite sure this did not happen in 1.0.3