I wish there was an attribute for the pagepath so I could limit the levels. I would like to have this because I think an editable pulldown-select tool is very powerfull, however I am sure not many users will understand why a second pulldown-select tool opens if you enter the previous one.
So please make this possible
Possible syntax could be:
fields:
reason:
label:Please select the reason why wikidot should make this.
type:pagepath
maxlevel:1
category:reasons
I second this. I like the function, especially since I can't sort my information via ListPages with selectable data. This is the next best thing but it's confusing to my users that they keep having more options … unfortunately, even when I warn them, haha.
Agreed.
~ Shane (Wikidot Community Admin - Volunteer)
Wikidot: My Blog, Wikidot Editor, Official Docs
Work: ZoomPlanner (built for freelancers/small business)
Other: YouTube (gaming channel)
I'll mark this planned. Keep rating it up, so that it goes higher in the list!
Piotr Gabryjeluk
visit my blog
Thanks Gabrys,
From memory, is Terq the one who developed PagePath in Data Forms???
λ James Kanjo
Blog | Wikidot Expert | λ and Proud
Web Developer | HTML | CSS | JavaScript
You can do this by css… but it want to keep it as a wish because there will come a day that I need a pagepath with four levels and a pagepath with only two in one form So…
But here is a workaround
this will only show 1 level
form table tbody tr td span div span span{display:none}
this will only show 2 levels
form table tbody tr td span div span span span{display:none}
this will only show 3 levels
form table tbody tr td span div span span span span{display:none}
this will only show 4 levels
form table tbody tr td span div span span span span span{display:none}
But now that I wrote this… since the field-names are also integrated in the HTML of the form… It's probably also possible to have two pagepaths of a different level in one form… I need to try that though!
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
You need to have the css in the Site theme, which isn't something that's suitable for Wikidot Applications (it makes things complicated for the End User when they need to play with their CSS).
It was good with the CSS module, but when creating new pages the CSS module in the _template doesn't work.
That is why this wish needs to be granted, because the CSS workaround is too complicated for most users.
λ James Kanjo
Blog | Wikidot Expert | λ and Proud
Web Developer | HTML | CSS | JavaScript
Indeed… for some strange reason is creating a new page different from editing an existing page with regards to what css the page will use.
But there is no need to put it in the Site Theme… as you know every category can have its own CSS and that CSS can be located on any page you wish in a code-block… So…
But STILL I agree this is a very good wish and I hope it will be developed soon.
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
Have run into this issue with a recent project of mine. With CSS I can achieve what I want, but it affects all pagepath fields in the category.
This means that I can't have one pagepath field with a limit of one, whilst a second field on the same form has a limit of two.
Being able to set the limit on a per-field basis (as part of the Data Form syntax) would solve this problem (and also prevent the need for a per-category theme, where the only difference from the main theme is to format the data form correctly).
~ Shane (Wikidot Community Admin - Volunteer)
Wikidot: My Blog, Wikidot Editor, Official Docs
Work: ZoomPlanner (built for freelancers/small business)
Other: YouTube (gaming channel)
@Wikidot, it's great that you've accepted this wish, but that was longer than a year ago!
Could you please work on allowing us to create page path limits?
λ James Kanjo
Blog | Wikidot Expert | λ and Proud
Web Developer | HTML | CSS | JavaScript
Yes… It has been a while now… What's happening here?
Bump!
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
Yes, here's a bump to my bump!
λ James Kanjo
Blog | Wikidot Expert | λ and Proud
Web Developer | HTML | CSS | JavaScript
SUPER: status Work In Proces!! thanks
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
Implemented, please test:
Bartłomiej Bąkowski @ Wikidot Inc.
';.;' TeRq (Write PM)
thanks! Will test it asap.
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
That works really well. I have used in on my test site at http://vineyard.wikidot.com/band:_template (with a resulting page at http://vineyard.wikidot.com/band:bjh) where I have 4 pagepath fields for continent, country, city and community. The new max-level is exactly what I needed. Many thanks.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
Thanks - this helps!
I use this now in all my genealogy-template
live _template pages ( which all have near only pagepath fields.. :)
http://genealogy-template.wikidot.com/per:_template (Person)
http://genealogy-template.wikidot.com/fam:_template (Family)
http://genealogy-template.wikidot.com/per-occu:_template (Person-occurence)
http://genealogy-template.wikidot.com/fam-occu:_template (Family-occurence)
and other…
What I need now is to change the CSS-Module I have used to "hide" the second level…in some live templates No, I leave the CSS module unchanged - there are lots of hints inside displayed how to use the pagepath fields ….l .
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?