Opened 3 years ago
Closed 3 years ago
#12747 closed defect (bug) (fixed)
Use another register date for the main blog
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | 3.0 |
| Component: | Multisite | Version: | 3.0 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
On ms-sites.php we can see the column Registered. For the first site its in the database 0000-00-00 00:00:00. But through mysql2date() we get 1999/11/30 12:00:00.
See also http://bugs.php.net/45647
Looks not very nice. How we should handle it?
- Idea 1: Make a check on ms-sites and return for the first site a minus instead of the date.
- Idea 2: At upgrade to multisite we could fetch the date of the first post and use this.
- Idea 3: Use the date on which we installed multisite.
- Idea 4: Wontfix. ;)
Change History (5)
Replying to wpmuguru:
I'm in favor of won't fix. That created date is a datestamp of when the record was created. If I create a new site and import an existing site into it, the creation date does not get changed.
IMO, if we start changing the creation date based on arbitrary rules then the field ceases to have any value because it's not a reliable indicator of anything.
Pardon me -> #3 would be the choice to go with. Then it would be consistent with the other records in the table.
I'm in favor of won't fix. That created date is a datestamp of when the record was created. If I create a new site and import an existing site into it, the creation date does not get changed.
IMO, if we start changing the creation date based on arbitrary rules then the field ceases to have any value because it's not a reliable indicator of anything.