Possible Conflict with Publish Content module

cheuyungphat - February 25, 2009 - 05:43
Project:Node Expire
Version:6.x-2.03
Component:Code
Category:support request
Priority:normal
Assigned:Unassigned
Status:active
Description

First let me say thank you for a wonderful module - It will definitely make like much easier!

I have recently been working with the Publish Content Module in an attempt to provide registered users the ability to re-publish nodes that have expired using Node Expire. However, I have run into a couple of issues that I was hoping to gain some insight into.

(1) Using Drupal 6.9, Publish Content 6.x-1.x-dev, Views-6.x-2.3 and Node Expire 6.X-2.03 I have created a view where registered users can pull up a table that provides links to edit, delete and publish (using the Publish Content Module) their own content.

Whenever a registered user chooses to either Publish or Unpublish a node, the node status is correctly updated to published or unpublished - however the following error message is displayed:

user warning: Duplicate entry '3' for key 'PRIMARY' query: INSERT INTO node_expire (nid, expire, expired) VALUES (3, 0, 0) in D:\xampp\htdocs\drupal\includes\common.inc on line 3425.

I recognize the duplicate entry referring to the node ID, however, I am not certain where to look in order to fix this. Can anyone suggest what I might look at in order to get these two to work together?

(2) I have applied a patch to Publish Content that updates the Post Date of a node to the current date/time that the node is "re-published" - which works great. The only problem (which I recognize is very specific to my needs) is that Node Expire does not update the Expiration date accordingly.

Is it possible to have Node Expire update a Node's expiration date according to a new/updated Post Date?

Thank you again for a great module and I certainly appreciate any suggestions that anyone can provide - best wishes!

#1

barckhoff - May 19, 2009 - 07:10

Hi,

I don't think this is necessarily a conflict with the other module. Try the fix listed here:

http://drupal.org/node/426636

#2

cheuyungphat - May 20, 2009 - 16:20

Thank you barckhoff for the link! I will definitely take a look at this.

 
 

Drupal is a registered trademark of Dries Buytaert.