I want to determine what tags a created pages gets by the values a person fills in in the form.

So if I ask "What type op level is client"? The options are 'low' 'medium' and 'high'
Depending on the input I want to add a tag to the page called low medium or high, so I can list them on a different page.
Is that possible? Or is there any other / easier way?

So i want to control the creation of tags, based on the input of a user.

I can't for the life of me figure out what I've done wrong here, but when I try to create a test page to see my data form, it simply won't load. I'm taken to the '(this page) does not yet exist' message, which usually you see flash briefly before being taken to the data form. But the process goes no further, even if I'm offered the 'intercept the lock' option.

Is there a size limit on data forms? Mine is rather large. But it was working perfectly well earlier. :/

Last I played with forms, you could neither 1) display raw data on the page without the attending label (field type: raw?) nor 2) place a particular field in it's own division of the page. I assume these are both still true.

I see that, rather than pushing a data field into a page division, they appear to be creating new properties (i.e. %%form_raw{name}%%, instead of %%content{n}%%). That seems unfortunate. ListPages + Live Templates is a dreamy combo, and I'd really rather data forms really be another way to let end users input data and to let admins craft clearer input instructions — not a whole new page type. All the right elements are present in the LP + LiveTemp scheme to make data forms work with creating nearly so much new ballast.

I suppose it's 6 of one, half a dozen of the other once these new properties work in Live Templates, it just seems like the developers are making more work for themselves doing it this way. Also, for the record, I'm thrilled forms are finally here. They'll be a great addition to the wikidot toolset.

When I first looked at forms when they were first released, I thought they looked really crappy. Not to pick on Only Joking, but that was my first exposure to a site that used the new forms and it just seemed really limiting in what you could do with the layout. Now that some CSS classes have been thrown into the mix, I think the look and feel can be improved dramatically.

After getting more acquainted over the weekend, I see a lot of promise, but until a few things that are still on the Planned implementation list get done, data forms won't be able to reach their full potential.

As you said, getting them working in live templates will be huge. That, along with the other things on the drawing board for ListPages Improvements (like being able to list a page by a specific name) will really make data forms a desirable feature and I think we'd see them really proliferate among Wikidot sites.

I have the same question. I tried to play at http://forms.wikidot.com/ b creating a new genre in the pagepath form field, but it does not save.

Steven is trying to help me and we've had a short PM discussion:

Steven,
Earlier, I was looking at http://forms.wikidot.com/. Is there a problem with pagepaths? It doesn't seem to work. Maybe I just don't fuly understand. Is the idea to build a trail similar to breadcrumbs up and down the tree? If so, that's cool if it works. Especially if we have the ability to make it dynamic as that site tries to show (but any genres I try to enter don't seem to save). Am I missing something?

Hi Ed,

Pagepath works fine for me…

What it does:
you define a field in your form type pagepath
in this definition you set a category…
Every thing you enter in the input-dropdown-field on the page will create a page in that category… noting more
so if you entered some things… and you query the pagetree of that category… you will see all the pages appearing in the correct parent-child relation as you entered them in the pagepath… It does nothing more.

If you make then for example a _template for that category and you put in [[the backlinks module] you will see all the original pages (in the category of the form_template)

For example
you wish to make an address-book
You create contact-person:_template
In this template you formulize a form with a pagepath referencing the category "address"
you now add you first contactperson
in the pagepath you enter
Europe —> Belgium —> Limburg —> Hasselt —> Somestreet and number
Now all these pages will be created on the fly. With zero content
However if you would make a address:_template with in there the backlinks module…
The page "somestreet and number" will display the name of your first contactperson

Got it!?

Steven

I'm not sure I've "got it" yet, but I'm going to play some more and try to sort this out in my brain.

To try to use a real "use case", I've been playing with a list of members in my golf league. I'm using a pagepath field for the member "status" to build a path like this:

Active

Full-time

Member Name (the page with the form)

…

Part-time

Member Name (the page with the form)

…

Inactive

Member Name (the page with the form)

…

I realize that a simple layout like this would be better served by using simple radio button options, but I'm trying to learn how pagepath works. ;)

It works really well to create the structure, but I just don't see the usefulness until the unfinished design sketches for both data forms and ListPages are completed. If I can't filter or sort on the data I'm collecting, I might as well use the methods we have available today (hidden tags, etc.)

Can we count on the items described in the design sketches to actually be implemented? If so, any idea how soon?

Speaking before Ed has a chance to reply… if I was creating a website with that type of content, I would see myself wanting to list all members. I would then want to be able to filter them into active/inactive or full-time/part-time lists.

Much further than that (e.g. filter by suburb that the member lives in) is probably redundant IMO

Or were you thinking about going that far Ed? Being able to use Wikidot like a database is an interesting concept… and being able to create a list of contacts and to sort and filter that list would be very powerful.

I would then want to be able to filter them into active/inactive or full-time/part-time lists

Exactly. The ListPages improvements documents a selection method of Select by form data field: property="property-selector" and the ability to use multiple selectors. Futhermore, the data forms planned implementation features will give us the ability to set tags and parents through a data form, giving us even more options for controlling how our form data is displayed.

and being able to create a list of contacts and to sort and filter that list would be very powerful.

Yes it would and it would spring loose a multitude of other new and interesting applications!

I tested this, just this morning, and was surprised to find that it doesn't work, as you said Gerdami. I thought PagePath set the parent of the page you were on… but it seems I was mistaken.

Is this a bug or design decision? Based on the name "page path", I'd naturally expect the current page to be included as part of the path… and therefore the final item to the far right of the page path field should be made to be the page's parent.

Yes? No?

Now that I'm starting off on a design tangent… I should probably start this discussion in the projects forum where it belongs.

Could any of you Leiger or Gerdami tell me what the problem is. Pagepath has a correct working… I really don't see the problems you are making… tell me what you wish to do in a clear question, not refering to some other post that sombody made somewhere. And I will try to explain.

I'm not sure if it's a problem as such, but pagepath does not set a parent on the form page itself. If it did I could use something like ListPages as parent="status:active" and parent="status:full-time" as Shane suggested. I like how pagepath and data forms in general are set up now. I think I'll just wait for a few more enhancements to be implemented in data forms and ListPages before using them too much. Additional features that I think will be important for usability include: