User tests: Successful: Unsuccessful:
Pull Request for Issue #13031 .
This a fix aimed towards the Joomla 4.x branch that ought to be in the 3.x branch too. Currently we don't always set this value (but with STRICT_TRANS_TABLES
disabled it automatically has a null date applied). In the 4.x branch we've enabled this parameter causing modules to fail to save.
We are doing this same check in com_contact for example hence why I'm making this PR at the staging branch rather than 4.x even if the results aren't obvious to test in this branch
Check modules continue to save in the 3.x branch with a null date if any of publish up, publish down or the checked out time isn't set
None
Status | New | ⇒ | Pending |
Category | ⇒ | Libraries |
Labels |
Added:
?
|
I've removed checked out time. It corresponds to whether the module is checked out or not - but I think we are actually ok there, because JTable and JModel seem to handle it correctly
I have tested this item
I have tested this item
Milestone |
Added: |
||
Status | Pending | ⇒ | Ready to Commit |
Labels |
Added:
?
|
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-02-16 19:20:18 |
Closed_By | ⇒ | rdeutz | |
Labels |
Null Data works in Publish up, publish down on several Modules,
in
Modules: Articles - Category
works onStart Date Range
andTo Date
too@wilsonge Can't find Field
checkout out time
.