Jaci,
How about creating a standard dmhtml page under your navigation node - with no content, then add a content rule to this page to display your desired dmHTML object.
You could either set up a handpicked rule and define the object to be picked each month.
Or, better still, create a rule that will list your dmHTML objects, in descending date creation sequence, and only select the last one to display. Adding a category will allow you to flag the dmHTML objects to be picked up by this rule. You could also add an automatic archive to display the last n monthly pages as links.
hth, Chris.
Jaci Chesnes wrote:
I've used the symbolic link before but it wont' work in this instance
because I don't want to link to an entire nav node I want to link to a
specific page of another nav node. Kind of like a redirect. Anybody
hitting this particular button will always get routed to the most
current version of this particular column, but all past versions of the
column need to continue to exist for archive purposes.
In essence I'm having the user build all new content pages directly into
the archive structure and just link to it from the current issue
structure.
Does that make sense?
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
