Page path improvements
nav_first.pngFirst: thread:379
Feedback from naive user
Edited: 26 Oct 2011 12:41 by: Sheepdog
Comments: 3
Tags:
nav_prev.pngPrevious: thread:277
Field name validation
Edited: 05 Feb 2010 08:16 by: pieterh
Comments: 0
Tags:
Last: thread:141
Which aspects of this design do people want first?
Edited: 11 Nov 2009 12:44 by: leiger
Comments: 14
Tags:
nav_last.png
Next: thread:259
line breaks in form fields
Edited: 23 Jan 2010 15:28 by: scottplan
Comments: 2
Tags:
nav_next.png

SquarkSquark wrote on 27 Jan 2010 09:49

Root page

Right now the pagepath tree has no root page. The top level pages have an empty parent. This is easy for set-up but it means the pagepath is incompatible with the PageTree module. We propose to change the pagepath field type so that top level pages are always children of a page called _root in that category. If the _root page does not exist, it is automatically created when the first top-level page is created, with no title and no body. The wiki designer can change the title of the _root page to make the breadcrumbs work better.

Level limit

Right now the pagepath tree has unlimited depth, but this allows pathological situations. We propose to fix the limit at 7 levels.


Start a new sub-thread

Current page connected to the PagePath? By leiger 2 Comments 02 Mar 2010 21:59
Pagepath Category By James Kanjo 1 Comments 19 Feb 2010 22:15
Some Live Template variables should be compatible By James Kanjo 0 Comments 11 Feb 2010 14:21
Lock PagePath Options By James Kanjo 2 Comments 11 Feb 2010 14:17
Autoparent to PagePath By James Kanjo 2 Comments 11 Feb 2010 14:10
Invisible existing pages in PP-category By Steven Heynderickx 6 Comments 09 Feb 2010 22:38
CSPP --> Cross site page path By Steven Heynderickx 0 Comments 28 Jan 2010 20:46
Ordering the page path By Steven Heynderickx 0 Comments 28 Jan 2010 09:42

Comments: 12

Add a New Comment
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License