[#15770] - [4.0] Published: 01 January 2011
- Closed
- 26 Dec 2017
- Medium
- Build: master
- # 15770
Steps to reproduce the issue
install Joomla 4
Look at the published dates on the frontend
Expected result
some recent date... like the date I set up the site, or at least something this year...
Actual result
Published: 01 January 2011
| Labels |
Added:
?
|
||
| Category | ⇒ | Installation |
| Status | New | ⇒ | Discussion |
so people couldn't identify the CMS version based on the dates of the content
All the more reason to have the installation date (which will be pseudo random then) as the timestamp.
Wasn't this fixed for J3
| Status | Discussion | ⇒ | Information Required |
@brianteeman all Articles get installation-Date in J3, so i guess this Issue can be closed.
@franz-wohlkoenig this refers to j4
@brianteeman i understand your Comment that if it is fixed in J3 its also fixed in J4.
any Update @wilsonge?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/15770.
Sample data will be rewritten for Joomla 4 I hope so this won't be an issue. I would close it for now
| Status | Information Required | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-12-26 07:24:43 |
| Closed_By | ⇒ | franz-wohlkoenig |
| Closed_Date | 2017-12-26 07:24:43 | ⇒ | 2017-12-26 07:24:44 |
| Closed_By | franz-wohlkoenig | ⇒ | joomla-cms-bot |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/15770
closed as Issue solved in the Meantime.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/15770.
Someone made the decision years ago that all of the default/sample content should use that date so people couldn't identify the CMS version based on the dates of the content. Can't say I agree with it, but that's the reasoning.
It also doesn't help that in 2017 we still work with raw SQL dumps and still can't use proper PHP APIs to seed our database.