Michael Ralston wrote:
My project is currently using the StaticHTMLExporter to save pages to a remote
web server. I'm not using the ant task (it didn't work), I'm using the
publishing target.
What does this exporting system do when a page is deactivated and then
deleted?
you mean the StaticHTMLExporter? It just dumps the "HTML" when
a document is being published. That's it. No deletion or updating of
links.
It appears the page is not removed from the static publishing
location. Also, navigation links to the removed page will not be updated
unless all pages with a link to the removed page are republished (which is
also an issue when you make a new pages, all pages that will link to the new
page need to be republished).
Are there any improvements to the way StaticHTMLExporter works which can be
merged back into an existing 1.2.4 project?
I would be great if you could improve it and contribute according
patches
Should I modify the wget/html
classes to recursively publish pages if they have links to the page being
removed?
Is there a better option than the way I'm currently trying to achieve this?
re updating links it's important to have a centralized link management
and using UUID ("unique IDs") for the links, otherwise one will run
into scalability issues.
HTH
Michi
Thanks
Michael Ralston
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
