[opencms-dev] Switching to static export on demand.

[Michael Moossen]

Hi Andy!

mmm, indeed, the export on demand is more thought to be used in a 
production system where your templates are really stable, then when you 
change something there you just have to purge the whole export folder.
this would cover points 1, 3 and 4.

but your second point should be working, may be there is a bug somewhere 
there, you can check the A_CmsStaticExportHandler#addMovedLinkSources 
method...

anyhow you could implement your own cleanup method. you just need to 
extend the 'on demand' handler and to overwrite the scrubExportFolders 
method.

HTH

Kind regards,
Michael

-------------------

Alkacon Software GmbH  - The OpenCms Experts
http://www.alkacon.com - http://www.opencms.org


Andy Savin wrote:
> Hi Michael,
> 
> Thanks for that, I have that working and when you publish a resource it
> correctly deletes that resource and apache sends you to the cms 404
> handler as expected.
> 
> However, the problems I am having are with the following situations:
> 
> 1) You make changes to a template.  None of the xmlpages that are using
> that template are removed which means apache will always server the
> version using the old template.
> 
> 2) You rename or move a resource that is linked to (href) from another
> resource.  I now know, thanks to your presentation, that the linking page
> won't get updated until it is read but it is not deleted and so apache
> never asks for it to be re-read.
> 
> 3) You update a property on a folder, which is used by all resources in
> the folder (via the template) to define menus etc.  The folder is
> deleted but the resourses are not deleted and so never use the new
> property.  I'm not sure if this one would be solved using the Html Subtree
> handler.
> 
> 4) You update a resource that is included in a template using a property
> defined on a folder (see point 3).  This doesn't force the folder to be
> reexported.
> 
> These were all possible using export rules when using after publish static
> export.  Am I missing something or is on demand static export not as
> suitable to our needs as it appeared?
> 
> Regards,
> 
> Andy
> 
> 
>