Bob Harner wrote:
On 6/7/06, Joern Nettingsmeier <[EMAIL PROTECTED]> wrote:
Andreas Hartmann wrote:
> Hi Lenya devs,
>
> please comment on this bug if you're interested in this issue.
> We should either fix or close it.
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=39077
i would very much like to see bob's suggestion implemented, i.e. to jump
to the parent document if a document is deleted.
that reminds me of an issue i wanted to bring up a while ago:
the document with the id "/index" has an implicit special meaning. if
you delete it (which is easily done), all of the lenya authoring
interface will explode in your face unless you recreate it. bad.
i was wondering whether it might simplify things if we had an immutable
root page that is only displayed in the authoring area and cannot be
deleted. the issue becomes obvious in the site tree overview: there is
no root, and you cannot for example paste a document under root. you can
only paste it as a child of some existing document, never as a
first-level sibling.
so it would be really nice if the "authoring" entry in that overview
would have an actual page associated to it, and you could click on it.
this root page could become the default backlink for any error messages,
(in fact for every piece of code that currently assumes that an /index
node exists).
it would enable users to paste stuff like they are used to, and there
would be a parent element for every document, which means we can have a
generic solution to this deletion problem without conditionals.
comments?
jörn
There may be times when one *does* want to delete the root document,
perhaps to recreate it as another doc type or because one wants to
wipe the root document's history. So, as one (harder-to-implement)
alternative it might be better to fix the bad Lenya behavior when
there is no root document. But Jörn's suggestion seems like a good
interrim measure.
root document in this case means "the page that is displayed by default
in the live area". note that i'm talking about this mystical immutable
root page only for authoring. there is no conceivable reason to ever
want to delete the that, because it has no meaning in live.
perhaps the root document should have different characteristics per
area: in authoring, it should display some informational text similar to
publication.xml, but in live, it should contain a redirect to the first
node in the sitetree. this could be easily done with some pipeline magic
in cocoon.
and my suggestion is not only to fix the "missing /index" problem. it
also ensures that *every* page has a parent, which cleans up the tree
semantics and makes the sitetree overview nicer to use when moving pages
around. right now, iiuc you *cannot* cut a document and paste it as a
first-level document. it will always become a child of your current doc,
because you can't click on "[+]authoring" , where you want the page to be.
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
