User tests: Successful: Unsuccessful:
Pull Request for Issue #24649.
Timestamp format.
Added Instructions from #24649 (comment) by @franz-wohlkoenig:
| Status | New | ⇒ | Pending |
| Category | ⇒ | Front End com_banners |
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-04-21 09:58:53 |
| Closed_By | ⇒ | twister65 | |
| Labels |
Added:
?
|
||
| Status | Closed | ⇒ | New |
| Closed_Date | 2019-04-21 09:58:53 | ⇒ | |
| Closed_By | twister65 | ⇒ |
| Status | New | ⇒ | Pending |
@HLeithner , for review please.
See #24652 (comment)
I have tested this item
This unfortunately is the wrong way to fix this. We still need to format this with ->toSQL(), since the used format() might not be the right format for the RDBMS. So you would have to modify the trackdate or create a helper trackdate which you can then format with ->toSQL.
I expected something along the lines of ->setMinutes(0) or something like that, but I think date objects are immutable... So it isn't really a nice solution, but should work...
I have tested this item
I have tested this item
@Pinkeltje please test again.
RTC ?
| Labels |
Added:
?
Removed: ? |
||
I have tested this item
| Status | Pending | ⇒ | Ready to Commit |
RTC
| Labels |
Added:
?
|
||
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-03-17 16:49:16 |
| Closed_By | ⇒ | zero-24 |
Merging here thanks for the patience
We have #24652.