Posted by szy on February 12, 2009 at 2:35am
Jump to:
| Project: | Node clone |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
| Issue tags: | CCK, date, link, Node Clone, node reference |
Issue Summary
Hi,
When editing node and then saving it, all CCK fields (Date, Link, Node Reference)
and Imagefield are gone from node view.
But... I can see, that they all are saved into database tables. And all of them
become visible in about 15 minutes - after the nearest cron run probably?
Have you seen anything like this? I've found only one person with the same
problem in Date's issue queue...
Help! :>
Szy.
Comments
#1
---
#2
Sorry, it's not about editing and saving - it is about *cloning* a node!
Moving to Node Clone.
Szy.
#3
@Peter,
It looks like my issue is a duplicate of #366857: Clone Appears to revert changes on save.
Could you tell me, how can I clear the cache after submitting a cloned node?
My fields appear again only after I manually clear the cache.
Now I even see, that fields are being deleted from original nodes...! :/
Is it only happening to me? :/
Tia,
Szy.
#4
-> #365771: Disappearing dates because of Date Popup?, comment #4
Szy.
#5
What module is doing the caching? Is this an issue for anonymous users or authenticated users?
#6
#7
Here's how I solved this issue. In one of my many custom modules, I put a nodeapi hook that fires whenever a node is inserted, clearing the cache for that node.
function MY_MODULE_NAME_nodeapi(&$node, $op, $a3 = NULL, $a4 = NULL) {if($op == 'insert') {
db_query("DELETE FROM {cache_content} WHERE cid = 'content:%d:%d'", $node->nid, $node->nid);
}
}
That's all it took! No fuss! A bug that eluded extermination for over a YEAR is squashed flat dead. Yay!