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.
Yes I fully agree. The sorting by dataform values in a ListPages module which was released recently is brilliant, but would be even more powerful if sorting on multiple columns was possible. I raised this in the wish related to dataform date fields at http://feedback.wikidot.com/wish:365/comments/show#post-1345343 but have not had any response yet from the developers
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
Any chance this can get some attention? I have a use case where I'm using data forms to track training status for employees who work at multiple restaurant locations. Ideally, i'd like to be able to sort like this:
_location
_lastname
_firstname
Code Example
The best option I have right now is to create multiple dataform categories (one for each of my 20+ locations) and then sort by lastname only. I'd prefer to use a single category and then filter the output using @URL values.
The other option is to try and manage this via the API, but that is pretty cumbersome for something like this where having multiple sort levels would easily solve my problem.
Community Admin
would help to have a (hidden?) dataform "field type": "connected" fields=(…,…,…) .. but this is only a work around than to use such intermediate storage field..
perhaps this is easier to implement?
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 ?
Using a data form field to specify the sort would work, but the users will think it's silly to enter the sort parameters, constructing it from data they have already entered. They would not understand why it's necessary. First, I ask them to fill in (among other things) the field data used for display proposes (shop, lastname, firstname). Then I'd have to provide a "sort field" and tell them to enter it as "shop[space]lastname[space]firstname" (or something similar) so I can use that field for sorting. Not really a solution for me. There would be too many opportunities for errors or non-compliance.
If we could sort by tags, I could use the set-tags to construct a "Confirm Sort Order" button and construct a tag from form data fields like "shop-lastname-firstname", but it doesn't help because ListPages doesn't have an option to sort by tags (and I'm don't think it's necessary unless a multilevel sort option is too hard to implement).
My current solution, which gets me 2 levels of sort, is to construct links with URL parameters and then use "@URL" in list pages. I can select by "_shop" and order by "_lastname". This is workable for me until this wish is granted. The only negative is when I want to list all shops. I have to order by "_shop" and let the rest of the sort fall where it may.
I have 21 shops and nearly 1000 employees that we are tracking training status for, so @URL works well for filtering and sorting the data for now.
Community Admin
Thanks Ed, for the long explanation why the manual feed of such sorting field is really nonsens. :)
My idea for the developers was more the implementation of a field type "Auto-connected" were we , the builder of the dataform template can insert (one or more ) "hidden" fields ( at the end of all others?) with the automatically connected field-content of fields we enter to build the content.
More a simulation of the connected strings - as you have written for the manually string but prepared automatically by entering&saving the original fields … and than filled automatically into the "sorting" field.
This new type of field could be implemented more easily I think from the wikidot developers as a sorting order with more than one input.
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 ?
Yes, a field that worked similarly to the altField option for the date picker that can gets it value from other fields would be great and I'm sure would have many other potential applications (like constructing custom tags, class names and so on).
But we're straying off topic from the original wish here. An altField-type option would help with my specific use case, but doesn't help if you want to sort on multiple levels if data forms are not used. Time for a new wish!
Community Admin