Hi,
On Tue, Aug 4, 2015 at 12:35 PM, vincent(a)massol.net <vincent(a)massol.net
wrote:
Hi devs,
When we create a new page through Add > Page (for example) we are still
setting the parent ATM, even though it’s not used by default in the
breadcrumb or elswhere.
Question 1: do we still want to set it or should we stop doing that
when core.hierarchyMode=reference?
Well, if we don`t keep setting parents in the create step and still support
the parent-child hierarcy option, this option becomes very misleading. What
I mean is that if you go some time with core.hierarchyMode=reference and at
some point you change it to core.hierarchyMode=parent (or whatever the
value is called), you will end up with tons of orphan documents.
Question 2: do we still want to enforce having a parent set in our build?
My preference would be to not enforce it anymore, however, for the same
reasons as above, you might have to... otherwise the
core.hierarchyMode=parent option will be misleading and might not behave as
expected.
> My preference would to not change any in
the 7.x cycle (i.e. keep setting
> the parent when creating new pages and keep enforcing parents in the
> build). The rationale is that:
> * 7.x is a transition cycle for Nested Spaces/Documents so it’s good to
> observe how users are using them
> * We should not use Nested Documents in our apps in the 7.x cycle as this
> would cause potential breakages in existing extensions since we would
> change location of wiki pages. IMO we need to implement aliases before we
> start doing so, but not before 8.x.
> WDYT?
+1 for handling (re-discussing) it in 8.x
Thanks,
Eduard
> Thanks
> -Vincent
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
>
http://lists.xwiki.org/mailman/listinfo/devs