Click here to edit contents of this page.
Click here to toggle editing of individual sections of the page (if possible). Watch headings for an "edit" link when available.
Append content without editing the whole page source.
Check out how this page has evolved in the past.
If you want to discuss contents of this page - this is the easiest way to do it.
View and manage file attachments for this page.
A few useful tools to manage this Site.
See pages that link to and include this page.
Change the name (also URL address, possibly the category) of the page.
View wiki source for this page without editing.
View/set parent page (used for creating breadcrumbs and structured layout).
Notify administrators if there is objectionable content in this page.
Something does not work as expected? Find out what you can do.
General Wikidot.com documentation and help section.
Wikidot.com Terms of Service - what you can, what you should not etc.
Wikidot.com Privacy Policy.
I have a Wikidot Application in development that may require more than 7 levels to function, depending on how people use it.
Must the limit be reduced to 7???
Can you explain the scenario? Seven levels of nesting is a lot. It could be 10, or 15.
Portfolio
Good scenario… but is pagepath the best way to do this? You could make a nice family tree application using ListPages, PageTree, etc. similar to the subthread concept.
So your scenario needs to be (a) a tree that really has 10+ levels and (b) using this tree in forms as reference data.
Portfolio
….
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
Personally, if I used the application, I wouldn't exceed 7 generations. But other people might exceed that, and I wouldn't want them complaining about a generation limit.
It's all in development, so nothing's set in stone yet. We'll see what happens.
I propose to give a property limit to form pagepath field definition, it will be most flexible.
Bartłomiej Bąkowski @ Wikidot Inc.
';.;' TeRq (Write PM)
Flexibility here does not solve any problem. Further, it means that a pagepath that works in one form won't work in another if the limit is wrongly set. The real problem is probably (but not proven yet) people misusing pagepath.
Portfolio
I am missing something? I can only get the first level of pagepath to work. When I try to "Create New" for the second level it doesn't create anything most of the time. (I've tried this on both IE and Firefox.) Sometime it does create, but it is at the top level.
Also, when I modified the "_template" and then went to edit a page with form data, the list of pagepaths is now gone.
Have a look at http://sandbox.wikidot.com/matthewdavey
I had to manually add the parent to each page to show the levels I wanted.
An Innovator at heart.
I had a look and changed some stuff. Mainly your problem is the following:
after creating a new item… you need to press enter
category:_root = in general terms the root of the pagepath
hope this helps
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
Thanks for that.
To me, pressing Enter is not obvious as you would usually press Enter to save the whole form page (Once you've filled out all of the other fields). It would be more obvious to have a button next to the Pagepath field such as "Add".
An Innovator at heart.
I agree. It is very counter-intuitive the way it is set up at the moment. I remember that it took me a while to figure it out… in reality, a good UI design should be natural, and easy to understand the first time someone sees it. Therefore the pagepath UI is flawed, badly.
I don't know how you'd improve it whilst still keeping it looking so simple. Perhaps stick with the current method that used on the site manager "Autonumbering of pages" section… where there is an " + add category " link to add another category. Something explicit… obvious to the user.
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)