Just practicing to pass the Turing test.
Bug 1: First reported 16th May 2000
If the site hierarchy contains page with names whose url encoded form is different to the unencoded form (i.e. it needs to be url encoded) the render this page button posts a request for the url encoded form - correctly.
However when the relative path is computed in manilsuite.staticRendering.displayRenderButton it is never url decoded , so the objectnotfoundhandler fails to find the page and the render fails. (As an aside, just to make life difficult, rendering the whole site works fine).
I see no fix that doesn't require patching manilasuite, my choice was to add a line to urldecode in manilasuite.staticRendering.getRelativePath as follows
relativepath = string.urldecode(relativepath); «00/05/16, 16:06:29 by DAB
pta^.pathRelativeToSite = relativePath;
Bug 2 :
Manila does not support Scalable Content. This is the ability to render a single content page in multiple formats or to mutiple destinations using templates and the ftpSite parameters; it is a standard feature of the underlying html suite upon which Manila is based.
This patch is one of a series to the static rendering of Manila that restores that ability. One of our clients used that ability to excellent effect in his 2 version Glasgow West End website which is manitaiend in manila and rendered in 2 versions.
Manila Managing Editors can use the ManilaFixer Plug-in to maintain additional templates and ftpSites for their websites.
Relative to Frontier version 9.7b10