>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.
Well, I wasn't thinking so much about the current core
(assuming you're talking about 1.2). I assumed the symlink
discussed was for 2.x.
Right now, I don't know how I'm going to accomplish what I
need in the current version of Midgard. I'm sold on the
potential for the technology, but scratching my head a lot
trying to figure out how it's going to work.
Trying to design a site with Midgard that is in some ways
like 40 different sites (the markets like
pittsburgh.radiodigest.com), with one MASTER site/page
(www.radiodigest.com), that all share some articles in one
way or another, but will be displaying them differently for
different lenghs of time in different sort orders...looks
daunting, if not code-expensive in the current version of
Midgard.
If I could have articles each with two complete sets of
variables for date, score, etc., I could see how to do it.
I'll keep plugging away...
Todd Daniel Woodward
Technical Consultant
RadioDigest.com Inc.
http://radiodigest.com
512/583-5448 Office
512/415-6840 Cell
"Radio you can READ!"
--
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]
