Is it impractical to have them link to a more permanent nav node associated with the page?
Sorry. Forgot to mention that this is for situations where a navigation node has multiple dmHTML objects underneath it.
Another option is for the pages to have the often-changing content inserted dynamically so that the page objectid doesn't change.
We have many of those already. But these are specific to static-type pages that are best suited for dmHTML and are not updated often. However there are so many pages throughout the site (hundreds in fact) that at least one of them is being edited on a daily basis (thus causing the linking issue). I guess I'll just have to tell them not to make multiple dmHTML pages withing a single dmNavigation object. That would solve the problem. A bandaid, yes. But a solution none-the-less.
-Jeff C.
--- 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/
