Flush CCK Field Cache on node insert/update to allow RC CCK field to reload [#435466]

I have managed to print the CCK Field in some Node Types.
Problem is that when new Nodes are added, old ones do not update the RC CCK Field.
I need to Edit and Save those Nodes in order to achieve that.

I guess this is related to CCK cache, but I didn't find solid information there and I want to make sure it isn't RC related.

How can I make this RC CCK Field (and preferably only this) update every time a new Node is created. Maybe with every cron run, but I have no idea how to do that.

Thanks in advance for your help.

Comments

Comment #1

nicholasThompson

English

CreditAttribution: nicholasThompson commented 16 April 2009 at 14:24

Title:	CCK Field not updating	» Flush CCK Field Cache on node insert/update to allow RC CCK field to reload
Version:	6.x-1.4	» 6.x-1.x-dev
Category:	support	» feature
Priority:	Normal	» Minor
Status:	Active	» Postponed

I would imagine you're right - it'll be related to the caching.

What is your site's caching configuration? I could look into adding a feature to flush the RC field cache on node insert/update...

Alternatively, the Devel module has an Empty Cache feature, you can just visit the modules page (which flushes the cache) or there is a flush cache button on the site performance settings page.

Comment #2

realOFF CreditAttribution: realOFF commented 17 April 2009 at 03:30

My site's cache config is as follow:

Cache mode: Normal
Minimum...: None
Page compression: Enabled
All the rest: Disabled

I guess that clearing or disabling the site's cache will slow performance down, so I have not tried that yet.

The feature you mention, will reload every RC CCK field (on every node) any time a Node is created or updated?

Thanks for your time.

Comment #3

nicholasThompson

English

CreditAttribution: nicholasThompson commented 17 September 2009 at 10:43

Status:

Postponed

» Needs work

So basically... On a node insert/update we need to:

Find which relevant content fields refer to this node type
Find all nodes which have an instance of this field
Wipe all instances of content:[nid]:* entries from cache_content.

I think that covers it. I'd probably make this an option in the settings or performace settings for the site so that people could enable it. It's not ideal to have large chunks of cache wiped on busy sites.

I guess a better option is to reduce the cache validity time and simply let the update propagate out?

Nick