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

szy’s picture

szy commented
Title: Fields disappear when cloning and come back later... » Fields disappear and come back after cron run
Project: Node clone » Content Construction Kit (CCK)
Version: 6.x-1.x-dev » 6.x-2.x-dev
Component: Code » General
Issue tags: -Node Clone

---

szy’s picture

szy commented
Title: Fields disappear and come back after cron run » Fields disappear when cloning and come back later...
Project: Content Construction Kit (CCK) » Node clone
Version: 6.x-2.x-dev » 6.x-1.x-dev
Component: General » Code
Issue tags: +Node Clone

Sorry, it's not about editing and saving - it is about *cloning* a node!
Moving to Node Clone.

Szy.

szy’s picture

szy commented
Title: Fields disappear and come back after cron run » Cache is not cleared after submit, original fields disappeared too
Project: Content Construction Kit (CCK) » Node clone
Version: 6.x-2.x-dev » 6.x-1.x-dev
Component: General » Code
Issue tags: +Node Clone

@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.

szy’s picture

szy commented

-> #365771: Disappearing dates because of Date Popup?, comment #4

Szy.

pwolanin’s picture

pwolanin commented

What module is doing the caching? Is this an issue for anonymous users or authenticated users?

pwolanin’s picture

pwolanin commented
Status: Active » Postponed (maintainer needs more info)
millenniumtree’s picture

millenniumtree
he/him/they/them
Location Volcano, HI
commented

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!

pwolanin’s picture

pwolanin commented

So this seems more like a CCK bug?

pwolanin’s picture

pwolanin commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)