On Wed, 8 Dec 1999, Todd Daniel Woodward wrote:
> A special type of article (say a symArticle) that is pulling
> the data from another article, but this SymArticle has its
> own properties that I can set individually. I could have one
> master article, with 50 symArticles, each with their own
> properties, and I can update the abstract and content in all
> 50 symArticles from one place.
This would be very hard to accomplish with the current core
structures. I think a workable solution would be to have the
'main' content trees separate from the 'publish' content trees.
Store all the originals in the main tree, then make only
'dumb' symlinks in the publish trees. Sorting would work
as usual, and you could have the extended properties in a
separate table (expiry, placing), indexed on the link id. The
displaying code would have to act upon this data; writing a
PHP function to handle this would not be hard.
I'm probably sounding like a broken record here, but the 2.0
extendable records are going to make these separate tables
unecessary.
Oh, and you will definately want to build a custom admin interface
for this.
Bye,
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
