-
New Commercial Services Section
We have now opened a commercial services section here on the forum for registered users. If you have a Fabrik project that you wish to have someone work on for you, post it under Help Wanted. If you are an application developer and wish to earn some money helping others, post your details under Fabrik Application Developers.
Both of these are unmoderated. It will be up to both parties to work out the details and come to an agreement.
-
Joomla 5.1
For running J!5.1 you must https://fabrikar.com/forums/index.php?wiki/update-from-github/ or include the new file manually https://fabrikar.com/forums/index.php?threads/joomla-5-1-and-fabrik-cannot-find-files-error.54473/post-285151 See also Announcements
Plugin timestamp updates the date even when the function is disabled
- Thread starter mvilela
- Start date
cheesegrits
Support Gopher
Well, Troester is correct in that we shouldn't supply any values, and the timestamp field should behave according to the "Update on edit" setting, which controls whether the field declaration includes ON UPDATE CURRENT_TIMESTAMP or not.
The problem was that since we wrote that plugin, we'd added the "new" generic "Store in DB" setting (under the Access settings) for all elements, which had a side effect of overriding the timestamp element's decision about whether to provide a value when saving. So if that "new" setting was left set to Yes, we would erroneously provide a value for the timestamp when saving the record (and thus overriding MySQL's default update behaviour).
I've added an override in the timestamp element so it always returns false for recordInDatabase(), regardless of the "Store in DB" setting.
https://github.com/Fabrik/fabrik/commit/4ec6c887c056d75d312c36ff4a84a0acb2f30640
-- hugh
The problem was that since we wrote that plugin, we'd added the "new" generic "Store in DB" setting (under the Access settings) for all elements, which had a side effect of overriding the timestamp element's decision about whether to provide a value when saving. So if that "new" setting was left set to Yes, we would erroneously provide a value for the timestamp when saving the record (and thus overriding MySQL's default update behaviour).
I've added an override in the timestamp element so it always returns false for recordInDatabase(), regardless of the "Store in DB" setting.
https://github.com/Fabrik/fabrik/commit/4ec6c887c056d75d312c36ff4a84a0acb2f30640
-- hugh