[opencms-dev] embargo/expiry of content

[Olli Aro]

Hi Alex,

Please find a zip file attached. This works if you do the following
(requires Opencms 5 RC1):

1) Create a module com.opencms.modules.expirydate.

2) Upload classes ExpiryDate (a class to control the response object) and
NavTemplateExtension (a class to control the CmsNav methods). Upload also
class R2CmsNewResourcePageRC1 (replaces CMSNewResourcePage class) in
com.modules.expirydate.workplace directory.

3) Replace /worplace/action/explorer_files_new_page.html with the file from
the zip.

4) Add entries from \workplace\locales\en\core_en_mods to
/workplace/locales/en/core_en.

5) Replace /worplace/template/explorer_files_new_page with the file from the
zip.

6) Include method com.opencms.modules.expirydate.ExpiryDate.checkExpiryDate
in your content template.

What the module does, it returns http error 404, if the content is not valid
(plus hides it from the navigation). Start date and expiry date are handled
as content parameters (named as start_date and expiry_date).

Regards,

Olli

> -----Original Message-----
> From: owner-opencms-dev at www.opencms.org
> [mailto:owner-opencms-dev at www.opencms.org]On Behalf Of Alexander
> Kandzior
> Sent: 17 February 2003 11:14
> To: opencms-dev at www.opencms.org
> Subject: RE: [opencms-dev] embargo/expiry of content
>
>
> Olli,
>
> sure this is interesting. Just send me what you have, and I will see if
> and how it fits in the core.
>
> Best Regards,
> Alex.
>
> Alexander Kandzior
> Alkacon Software - The OpenCms Experts
> http://www.alkacon.com
>
> > -----Original Message-----
> > From: owner-opencms-dev at www.opencms.org
> > [mailto:owner-opencms-dev at www.opencms.org] On Behalf Of Olli Aro
> > Sent: Monday, February 17, 2003 11:10 AM
> > To: opencms-dev at www.opencms.org
> > Subject: RE: [opencms-dev] embargo/expiry of content
> >
> >
> > Hi all,
> >
> > I have just finished implementation for this and am currently
> > testing my code. My solution is template class based, but I
> > am more than happy to to contribute my code to the project,
> > if the project decides that this would be useful feature to
> > include within the core opencms.
> >
> > Regards,
> >
> > Olli Aro
> > Clicks and Links Ltd
> >
> > > -----Original Message-----
> > > From: owner-opencms-dev at www.opencms.org
> > > [mailto:owner-opencms-dev at www.opencms.org]On Behalf Of
> > David Tildesley
> > > (DSLWN)
> > > Sent: 16 February 2003 22:28
> > > To: Opencms-Dev (E-mail)
> > > Subject: [opencms-dev] embargo/expiry of content
> > >
> > >
> > > Hi,
> > >
> > > I may be wrong, but I don't see any way of embargo (don't make
> > > available content before stated date/time) or expiry (don't make
> > > available after stated date/time) of content in the current and new
> > > versions of OpenCMS. Has anyone achieved this with OpenCMS and can
> > > they share their experience?
> > >
> > > thanks,
> > >
> > > David Tildesley,
> > > Consultant,
> > > Datacom Systems Ltd,
> > > Wellington.
> > > DDI 04-4601549
> > > MBL 027-2808252
> > > FAX 04-4601610
> > >
> > > Note: This communication is private and in no way constitutes an
> > > agreement or commitment on behalf of Datacom Systems Ltd, Datacom
> > > Holdings Ltd or any of its subsidiaries. If you have received this
> > > communication and you do not
> > > think you should have, please let the originating sender know
> > > immediately.
> > >
> >
> >
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: opencms_expiry_date.zip
Type: application/x-zip-compressed
Size: 16884 bytes
Desc: not available
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20030217/3c7ea04f/attachment.bin>