By ccbelland on

I have installed Auto Expire in my site. The module works great for nodes created AFTER the installation of this module. However, nodes that were created PRIOR to the installation of this node are showing that they were created in 1969 and will not become part of

Auto Expire. Is there a setting that I'm missing or is they a way to trick the system to think that pre-exsisting nodes were created after the Auto Expire module was implemented. Any other ideas?

Thanks

⋅ Categories: Drupal 5.x

Comments

wobbler’s picture

wobbler commented

does updating (edit and save) the nodes update them?

ccbelland’s picture

ccbelland commented

no, I'm afraid it doesn't. Further, I have a lot of preexisting nodes so I am looking for a "bulk" method... whatever that may be.

wobbler’s picture

wobbler commented

I don't know how the auto expire thing works, but you could manually do it if you have db access, in mysql you could use a line like

update [db_name].node set status=0 where status = 1 AND type = 'page' AND changed < UNIX_TIMESTAMP('2008-01-01 00:00:00') AND nid NOT IN ( 1,2,3,...,10)

This basically says unpublish (set status to 0) any node where it is published (status = 1) is of type page was last updated before 2008-01-01 and the node id is not 1,2,3,...,10. You would need to adjust the parameters to make sure that all your main page node ids are included. The beauty of this approach is that you can always republish the node if it is picked up by mistake.

Then you can sort of bulk delete just using the normal content management page, by filtering by nodes that are unpublished.

This is completely untested, and you should always always make a backup of the database before running a bulk command like this.