I am looking at implementing this setup on my organization's website (the hub) and its regional sites (client sites). My issue is that when I promote a node in the client site(s) to the frontpage of that site, it also promotes to the hub's frontpage (which logically makes sense since the node is on both sites).

I need a way to stop this from happening, otherwise it kind of defeats the purpose of my client site.

Thanks

Comments

nedjo’s picture

Good point, and not an issue I'd considered.

Probably we need to store certain properties separately and reset them as appropriate to a given site, using hook_nodeapi(). That is, roughly:

* create table with three fields: prefix, nid, promoted
* in hook_nodeapi() op validate, detect change in promote value and, if present, set $node->local_promote to the promoted value and reset promoted to original value.
* in hook_nodeapi() op 'load', reset 'promoted' value with local value

I hope to be working more intensively on the module in two or three months when I will be completing a second round of development for the client who contracted it. I'm unlikely to be able to do much further development before then.