[opencms-dev] Module for automating the publication and unpublication of conten ts

[Olli Aro]

Guillaume,

Please find zip files attached.

com.opencms.modules.roundabout.enhancedcontentmodule_2.0.zip is in OpenCms
module format. You can install this just like any module.
r2_exp_date_workplace_5.0.zip includes worplace upgrades and can be imported
with database import function. Remember to publish the workplace upgrades
and and restart your opencms after installation. Also remember to add
attributes start_date and expiry_date to content type page.

Content expiry can be checked from xml templates by including method
checkExpiryDate from the template class
com.opencms.modules.roundabout.enhancedcontentmodule.ExpiryDate. From the
JSPs it can be checked with :-

com.opencms.modules.roundabout.enhancedcontentmodule.ExpiryDate
expiryDate=new ExpiryDate();
if(!expiryDate.hasExpiredJSP(filename))
{
...
}

Have a try and let's me know what you think. Maybe we could post these to
OpenCms sandbox, if you find them reliable / sufficient enough...

Regards,

Olli



> -----Original Message-----
> From: opencms-dev-admin at opencms.org
> [mailto:opencms-dev-admin at opencms.org]On Behalf Of Apostoly Guillaume
> Sent: 24 July 2003 14:52
> To: opencms-dev at opencms.org
> Subject: RE: [opencms-dev] Module for automating the publication and
> unpublication of conten ts
>
>
> Hum, it seems a nice and tricky solution, a part from the fact that
> apparently, their's one check done for every request then.
> My idea was to have something like :
> /RootFolder
> 	/content
> 	/to_be_published
> 	/expired
> and have this behaviour : when you publish a project, all published
> documents are checked and if they have a startDate in the futur, moved to
> the mirror tree under "to_be_published". On the other hand a cron
> would look
> at the contents that must be moved to "expired".
> This to give a better view for content managers of what is about to be
> published and what have expired.
>
> Still, i'll try your solution because :
> - it seems nice
> - it's already done !! :)
>
> could you send me the .zip again ? It's unusable in the archive ?
>
> Thanks by advance,
>
> Regards,
>
> Guillaume.
>
> > -----Message d'origine-----
> > De: Olli Aro [mailto:olli_aro at yahoo.co.uk]
> > Date: jeudi 24 juillet 2003 15:09
> > À: opencms-dev at opencms.org
> > Objet: RE: [opencms-dev] Module for automating the publication and
> > unpublication of conten ts
> >
> >
> > Hi Guillaume,
> >
> > I posted something similar on the list in February. Please see posting
> > http://mail.opencms.org/pipermail/opencms-dev/2003q1/003662.ht
> > ml. Is that
> > what you are after? The opencms team was going to consider
> > including my
> > solution to version 5, but it never appeared there... Don't
> > quite know what
> > happened...
> >
> > Regards,
> >
> > Olli
> >
> > > -----Original Message-----
> > > From: opencms-dev-admin at opencms.org
> > > [mailto:opencms-dev-admin at opencms.org]On Behalf Of Apostoly
> > Guillaume
> > > Sent: 24 July 2003 13:48
> > > To: opencms-dev at opencms.org
> > > Subject: [opencms-dev] Module for automating the publication and
> > > unpublication of conten ts
> > >
> > >
> > > Hi all,
> > >
> > > I'm looking for a peace of code that enable contents to be
> > moved, from an
> > > archive to an online tree based on dates, like : I publish this
> > > document, i
> > > want it go online that day, and go offline that other day.
> > > Does anyone have heard about something like that ? If not,
> > i plan to build
> > > that and use the cronJob and publish events for that.
> > >
> > > Thanks by advance,
> > >
> > > Regards,
> > >
> > > Guillaume.
> > >
> > > _______________________________________
> > > Guillaume APOSTOLY
> > > Business-Analyst EIS-BSD
> > > Tél: +33 (0)1.30.44.95.22
> > > Fax: +33 (0)1.30.44.98.08
> > > ApostolyG at mail.europcar.com <mailto:ApostolyG at mail.europcar.com>
> > > _______________________________________
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > This mail is send to you from the opencms-dev mailing list
> > > To change your list options, or to unsubscribe from the
> > list, please visit
> > > http://mail.opencms.org/mailman/listinfo/opencms-dev
> > > ---
> > > Incoming mail is certified Virus Free.
> > > Checked by AVG anti-virus system (http://www.grisoft.com).
> > > Version: 6.0.495 / Virus Database: 294 - Release Date: 30/06/2003
> > >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.495 / Virus Database: 294 - Release Date: 30/06/2003
> >
> >
> > _______________________________________________
> > This mail is send to you from the opencms-dev mailing list
> > To change your list options, or to unsubscribe from the list,
> > please visit
> > http://mail.opencms.org/mailman/listinfo/opencms-dev
> >
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.495 / Virus Database: 294 - Release Date: 30/06/2003
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.495 / Virus Database: 294 - Release Date: 30/06/2003
-------------- next part --------------
A non-text attachment was scrubbed...
Name: r2_exp_date_workplace_5.0.zip
Type: application/octet-stream
Size: 20982 bytes
Desc: not available
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20030724/0773a356/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: com.opencms.modules.roundabout.enhancedcontentmodule_2.0.zip
Type: application/octet-stream
Size: 12520 bytes
Desc: not available
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20030724/0773a356/attachment-0001.obj>