WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 8 years ago

#12747 closed defect (bug) (fixed)

Use another register date for the main blog

Reported by: ocean90 Owned by:
Milestone: 3.0 Priority: low
Severity: normal Version: 3.0
Component: Multisite Keywords:
Focuses: 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)

#1 @scribu
8 years ago

  • Milestone changed from Unassigned to 3.0

#2 follow-up: @wpmuguru
8 years ago

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.

#3 in reply to: ↑ 2 @wpmuguru
8 years ago

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.

#4 @wpmuguru
8 years ago

(In [14012]) set registered datestamp to current time during enable network, see #12747

#5 @nacin
8 years ago

  • Resolution set to fixed
  • Status changed from new to closed

For sites that don't have a registered timestamp, this will show as an em dash in admin (as handled in #12460). Closing as fixed.

Note: See TracTickets for help on using tickets.