I think I have touched on this with you briefly before Richard but I work with a charity that has about 11 sites in a single install. The site has an automated import process to pull in tagged links from the del.icio.us bookmarking service where they tag their press releases and industry news articles. Some of this content should appear on multiple sites within the install but because the DataSourceKey is just the <guid /> from the RSS feed item it will only get imported into one of the sites.
If the DataSourceKey was perhaps comprised of the import type, the unique identifier and the parent/root node it would allow this process to work as expected? The only way I can see around this at present is to create a proxy that changes the <guid /> value so that it is unique per site that imports it.
Change DatSourceKey Composition to account for root node in multi site installs
I think I have touched on this with you briefly before Richard but I work with a charity that has about 11 sites in a single install. The site has an automated import process to pull in tagged links from the del.icio.us bookmarking service where they tag their press releases and industry news articles. Some of this content should appear on multiple sites within the install but because the
DataSourceKeyis just the<guid />from the RSS feed item it will only get imported into one of the sites.If the
DataSourceKeywas perhaps comprised of the import type, the unique identifier and the parent/root node it would allow this process to work as expected? The only way I can see around this at present is to create a proxy that changes the<guid />value so that it is unique per site that imports it.Cheers, Simon
Hi Simon,
Yeah that's a bit annoying at the moment. Making the key unique using the proxy is the best thing indeed.
Cheers,
Richard
is working on a reply...