For those of you having no FTP access it might help to create a new CP HTML in the backend containing the following in the [PHP] inline tag. Run the article once in frontend. It should return a bool(true). The article in which the new CP HTML is created must have a valid end date. Check that first, otherwise the [PHP] is not processed!!!
Code: Select all
$r = @mysql_query("UPDATE ".DB_PREPEND."phpwcms_article SET article_tstamp=article_tstamp, article_end='2030-12-31 23:59:59' WHERE article_end='2010-12-31 23:59:59' AND article_deleted=0", $GLOBALS['db']);
If everything is fine then, you can delete the CP HTML again or just disable it.
I have released a patch file which can be downloaded on GitHub. This fix will update the fixed article end date (2010-12-31 23:59:59 problem) by adding additional 20 years. It works with every install of phpwcms. Download the fix, unzip it and put it in the web install root directory of your phpwcms installation (in the same level as login.php, index.php and phpwcms.php). Upload the script by ftp then point your browser to http://%yourphpwcms.com%/phpwcmsfixarticledate.php.
To solve that behavior (sorry for that) you have to update article end dates. I have prepared a short screencast how you can do this using phpMyAdmin or equivalent tool. http://flic.kr/p/96Hv8s
Check this upgrade script which corrects article end date:
https://github.com/slackero/phpwcms/blo ... ledate.php