While not impossible, this might prove to be very long and difficult exercise. Public instances are basically just snapshots of current state. Their primary purpose is to server content and to do so fast. For this reason public instance doesn't keep any versions. When it receives content from the author, it would just go and replace existing content with the new one. To change this you would need to extend ReceiveFilter on public instance.
To obtain the view of versioned content, you can have a look in how version view does it (normally you would see that as a user by having mgnlVersion=xxx request parameter. The minimalistic approach would be to inject that by your code that intercepts the incoming request and decided what version to show the user. The last (i can think of now) but most difficult issue would be assembling the content together. As you might see in version preview, all inherited content is not included in the preview. this is due to the fact that versioned content lives in completely different part of repo and under completely different structure (the original parent page is not versions' parent anymore).There you would need to wrap such content to pretend that it is still in the original hierarchy. HTH, Jan -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=71f3d2c4-1176-4877-87c1-a25477f11a17 ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
