default end dates

Evoplure · Post by **Evoplure** » Wed 20. Dec 2006, 13:31

I never checked the default end date

when creating an article, and now I realize that they will not be shown anymore after 10 years from its creation date, if i don't fix the issue before

Of course, phpwcms has not to be a cms for dumb people as me

, but I think it would be better if that option is turned off by default.

pico · Post by **pico** » Wed 20. Dec 2006, 15:53

ups

you are working for 10 Years with phpWCMS ???
so I think phpwcms is the oldest CMS in WEB

to set all end Dates to a new Value you must do a SQL Query/Replace or open all Articles in Backend and set a new Date

Evoplure · Post by **Evoplure** » Wed 20. Dec 2006, 16:33

well, i was not working with phpwcms 10 years ago... lucky me, that means that the end date is 2016, not now... so i have plenty of time to solve the issue.

Thank you for the idea of using a SQL query, that way is definitely easier that changing each date in the backend.

Anyway, the suggestion of not setting a default date by default is still there...

It is curious: when creating an article (in 1.2.8) the first step does not set a default end date, while the second does... In addition, it would be a good idea to merge both steps (note that the second one includes all the information that you entered in the first one... so I dont know the reason why the process is duplicated). It should be possible to introduce the article basic information with only one step...

pico · Post by **pico** » Wed 20. Dec 2006, 18:24

see not realy a Problem with 2016 - think your Website will not be browseble at this time anymore - then everything has changed to WEB 4.0 or what ever

Evoplure · Post by **Evoplure** » Wed 20. Dec 2006, 21:48

well, if I am not wrong websites of 1996 are still browseable... And it would be a big loss for the www if new browsers cant read old pages... big amounts of information would be lost that way... new standards can appear, but that doesn't mean that we will be forced to redesign all our old jobs... (at least I hope so...)

And sincerely, WEB 4.0 or whatever the new thing is gonna be, but I'm afraid we will be still waiting for phpwcms v.2... or do you expect big changes in phpwcms even in -only- 10 years?

pico · Post by **pico** » Thu 21. Dec 2006, 08:32

if you like to 'hack' this, you'll find the Code in ../includu/inc_tmpl/article.new.tmpl.php

find

Code: Select all

$article_end = date("Y-m-d", time()+(60*60*24*365*10)).' 23:59:59';

change to

Code: Select all

$article_end = date("Y-m-d", time()+(60*60*24*365*100)).' 23:59:59';

so Articles will end in 100 Years - so it doesn't matter you anymore

jsw_nz · Post by **jsw_nz** » Sat 23. Dec 2006, 11:27

hehe 100 years - will outlive me - methinks

Evoplure has a good point - which has been mentioned before - namely expiration set to >= never expires - as far as I know this is still not supported in core - I think OliG is aware of this as a 'wish list' item....

johnn · Post by **johnn** » Thu 8. Mar 2007, 11:09

Hi, I'm using ver 1.2.6 and there is no such code in article.new.tmpl.php

All my articles end 2010-12-31

Post by **Oliver Georgi** » Thu 8. Mar 2007, 12:09

if really neccessary it's an easy step to upgrade end date by simple SQL query.

Don't think about it.

Olier