jili maintenance.REGISTER NOW GET FREE 888 PESOS REWARDS!

carboncopy
(@carboncopy)

15 years, 5 months ago

We are encountering problems when changing the published date to before 1 January 1970.

For example,

The post is backdated to 2 April 1968
Link :
https://bibliotheca.limkitsiang.com/1968/04/02

However, it appears on the web saying its published today (1 July 2009).
Example:
Posted by Curator in Education a statement released on July 1st, 2009

If post is after 1 January 1970, there’s no problem.

Did not have this problem initially (earlier WP)

To proof my point, please check the two following links:
https://bibliotheca.limkitsiang.com/1969/12/
https://bibliotheca.limkitsiang.com/1970/01/

Viewing 7 replies - 16 through 22 (of 22 total)

← 1 2

gorky5
(@gorky5)

15 years, 1 month ago

Please note the bug is still present in 2.8.5, so if you upgrade WP you’ll have to re-edit the functions.php file in wp-includes and comment out the rogue lines again.

gosunatxrea
(@gosunatxrea)

14 years, 11 months ago

This bug will not be fixed in wordpress2.9.

https://core.trac.www.ads-software.com/ticket/10332

* milestone changed from 2.9 to Future Release

Agree this bug should be fixed, but since we’re in beta 2 now, punting to next release cycle for further testing and/or revision.

chartinael
(@chartinael)

14 years, 11 months ago

https://www.ads-software.com/support/topic/307257?replies=4

Solution proposed (commenting out) solved issue for me using 2.8.6.

Still annoying … meanwhile I have several edits in the core files system I need to re-do with every update.

herko
(@herko)

14 years, 11 months ago

* milestone changed from 2.9 to Future Release

Agree this bug should be fixed, but since we’re in beta 2 now, punting to next release cycle for further testing and/or revision.

Wow. this is an issue that’s been open for a year, and it gets delayed because ‘we’re in beta 2 now’? I thought putting issues in milestones was meant to ensure they’d be fixed in those milestones, and motivated if and when this would not be the case. This is just bad release management!

gorky5
(@gorky5)

14 years, 11 months ago

That is frustrating. I really wish this would be fixed – it’s a hassle having to change WP core files to get a website working properly.

I’ve just upgraded to 2.9. The lines that need commenting out are still 90-98 (though 95 and 96 are already comments) in wp-includes/functions.php

gorky5
(@gorky5)

14 years, 5 months ago

Does anyone know if this issue is fixed in the latest release candidate for WP3? Herco’s latest message here suggests not.

If that’s the case, can someone please let me know if the same lines in functions.php will need commenting out when WP3 is released, or, if not, how this bug can be overcome?

Moderator Ipstenu (Mika Epstein)
(@ipstenu)

?????? Advisor and Activist

14 years, 5 months ago

Checked those files in my 3.0 RC3 build, and you are correct that the changes will still need to be made.

It may be worthwhile to, tomorrow, mention this on https://wpdevel.wordpress.com/ (they usually make an open post for agenda items). It may just need a reminder?