> 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.
If you have multiple HTML pages under a Nav node ( and it sounds like you do) you can still use Symbolic Links. Here's the key; whichever issue is the "Current Issue" needs to be the first HTML page under the Nav node. Instruct your User that when he/she is ready for the current issue to go live then they simply user the Move function to move it to the top. > 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. You can use dmLink if you want. Given what I can tell of your situation, I don't recommend this as it requires more actions from the user maintaining the archives. > 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? It would help if you sent an example of your site structure. Maybe a screenshot? ~tom --- 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/
