db_next_id() is deprecated. Use db_last_insert_id() instead.

Comments

yrocq’s picture

Title: Use db_last_insert_id() instead of db_next_id » Remove custom node_save function

Remove custom node_save function and use sql query to change the fields that we can't set when creating the node.

raines37’s picture

Custom node_save function just looks like a stripped down version of 5's. What extra fields were being set in it?

yrocq’s picture

Hum, I may have confused with something else. If I remember, I created the wordpress_import_node_save because I wanted to prevent the watchdog table from being filled by nodes creation notices. Maybe it wasn't necessary and we could use the original function.

yrocq’s picture

Assigned: Unassigned » yrocq
lavamind’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev
Assigned: yrocq » lavamind
Status: Active » Fixed

Fixed in 6.x-2.x-dev, we use Drupal's built-in node_save() function now.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.