Hi, There are several approaches to get this functionality on top of MMBase. I know of two:
1) the two cloud approach (used in Leeuwarden, Surfnet and Web-In-The-Box)with a staging and a live cloud. The staging cloud is used for all editing, draf and unpublished stuff. The maintenance app works on the stagin cloud. Then, upon publishing, the object is copied to the live cloud. Deferred publishing can be done from batch by scheduled jobs. The site templates read the objects from the live cloud only. This approach allows for versioning solutions as well. It is quite some work to build this. 2) use the 'owner' field, present on every MMBase on=bject, as a status field. This is used in the HCS project. Allow for two statuses 'draft' and 'published' and possibly 'archived' as well. Then, using the context security option of MMBase, create two users (or contexts): the editor context assigned to all editors from which one can see objects of all statuses, and the live context which is assigned to the public site visitors and only have access to those objects with 'live' status. Publishing comes down to switching the status field from 'draft' to 'published'. This process can be deferred as well and be scheduled using a publication window object e.g. The publication window contains a publication date and a archival date. Using a batch, or through lazy checking, one can make sure that the status transitions happen on a scheduled basis. This approach is much less work since all status checking is done by the bridge throug the context security option. Versioning, however, is harder to do since every object just exists once. So, once published, the object can not be changed again in a staging/draft status -> all changes on a published object are directly visible. Hope this helps, Peter Hi everybody, I was wondering if someone has an example of an mmbase implementation with "preview" and "scheduled display" functionallity? So items that are editted are not displayed immediately but they can be previewed and a "live display" date can be given. Greetings, Joris van Poppel -----------------------Disclaimer------------------------- Dit bericht (met bijlagen) is met grote zorgvuldigheid samengesteld. Voor mogelijke onjuistheid en/of onvolledigheid van de hierin verstrekte informatie kan Kennisnet geen aansprakelijkheid aanvaarden, evenmin kunnen aan de inhoud van dit bericht (met bijlagen) rechten worden ontleend. De inhoud van dit bericht (met bijlagen) kan vertrouwelijke informatie bevatten en is uitsluitend bestemd voor de geadresseerde van dit bericht. Indien u niet de beoogde ontvanger van dit bericht bent, verzoekt Kennisnet u dit bericht te verwijderen, eventuele bijlagen niet te openen en wijst Kennisnet u op de onrechtmatigheid van het gebruiken, kopi�ren of verspreiden van de inhoud van dit bericht (met bijlagen). This message (with attachments) is given in good faith. Kennisnet cannot assume any responsibility for the accuracy or reliability of the information contained in this message (with attachments), nor shall the information be construed as constituting any obligation on the part of Kennisnet. The information contained in this message (with attachments) may be confidential or privileged and is only intended for the use of the named addressee. If you are not the intended recipient, you are requested by Kennisnet to delete this message (with attachments) without opening it and you are notified by Kennisnet that any disclosure, copying or distribution of the information contained in this message (with attachments) is strictly prohibited and unlawful. ----------------------------------------------------------
