Wikidot Community

I've now added an extra field onto the form and an iftags onto the page to set a tag separately from the rest of the tags. This adds an extra tag without affecting the ones already there. On the orders:main page I've then used listpages based on the tag set via the iftags. You'll see that since I placed the code in the post above I've also done a small amount of styling to layout the page. Hope it's all helpful.

Thanks! This has been helpful and I think it is something that could work for me.

Would there be a way to set a predefined tag on the form being saved? For example on save add the tag "unconfirmed". I think I can do this with new pages, but what about edited pages? Then I could use this to exclude pages that have been edited and whose data no longer matches the tags. This way I could keep other users from viewing obsolete data.

Would there be a way to set a predefined tag on the form being saved? For example on save add the tag "unconfirmed". I think I can do this with new pages,

With the newpage module or the newpage button snippet which I used in the demo you can set tags so that when a new page is saved a tag of "unconfirmed" is set. Using the newpage button snippet it would look like this:

[[image waiter.jpg width="350px"]]
[[include :snippets:newpage-button
|name=menu
|title=Customer Order
|category=menu
|parent=orders:main
|tags=unconfirmed
|size=350px
|button=Create a new customer order
]]

But for existing pages you cannot do anything on save because that would require interaction with the javascript code that is being used to save the form. If it was currently possible to set tags on save I wouldn't have needed to spend the time showing you the workaround. It requires the developers to produce a solution that at the moment isn't available.

I see. Thank you!

Ok another issue i've come across, if there is a space such as.. between a name "Joe Smith".. it kicks the same error with not listing the available link to set the tag. i've tried using the _raw & the _data option with no luck.. any thoughts?

I had thought at one time i had it working where if there was a space, it ignored it and actually combined the words so it came out in the tag as "joesmith"… but that was when i was figuring the above things out, and now cant seem to duplicate it

You'll need to post the code you are using or preferably provide a link to your live template page so we xan see the source. Without that we can't see what is happening.

[[button set-tags +advquestlvl%%form_raw{Level}%% +%%form_data{NPC}%%advquest text="Add Quest to Lists"]]

template - http://www.thetelonproject.com/adventuring-quest:_template

its the +%%form_data{NPC}%%advquest thats causing it, if the name has a space in it, it causes the "You need to set text for set-tags button." error on the pages

and here's a link to a test page that demonstrates the error: http://www.thetelonproject.com/adventuring-quest:test2

Until today I had not tested the two-step tag creation process for dataforms with any field type other than select fields where you can control exactly what the responses can be.

The "Level" and "NPC" fields in your dataform are text fields where you have very little control over what your user enters. The error you get is because the set-tags button requires a + or - and there isn't one for any word after a space in your field. But you can enforce a rule in your dataform field that prevents spaces but allows hyphens or underscores between words. You do this with regex (regular expressions) to match what the user enters to the rule you have set up:

fields:
npc:
  label: Start NPC
  type: text
  match: /^[a-zA-Z0-9-_]+$/
  match-error: NPC must not have a space between words but can have a hyphen or underscore

So your user would be able to enter John-Smith, John_Smith or JohnSmith but not John Smith. Using a regex like this means that the field is saved in a format which is acceptable to the set-tags button.

Alright, i noticed the issue with the select option as well, if trying to pull the raw data out of it, say for example "1: Test This", the space in that data throws it off as well, so was thinking that the null data from the space was causing it.

It would be nice if this could be resolved in the future to be able to handle the space in the information and join the words together.

on another note, (more of a question for data forms, ill move it there)

But with a select field you don't have to use form_raw at all. You could set up your field as follows:

cooked:
  label: How Cooked
  type: select
  values:
    no: None
    ra: Rare
    mr: Medium Rare
    md: Medium
    wd: Well Done

Above the separator use %%form_data{cooked}%%. That puts Medium Rare onto the page when saved as shown at http://vineyard.wikidot.com/menu:10. And the tag that is saved is mr whicj can be used to select records via the ListPages module.

Using this:
cooked:
label: How Cooked
type: select
values:
no: None
ra: Rare
mr: Medium Rare
md: Medium
wd: Well Done

is there a limit to number of characters that the value indicator (for example the no: or mr:) can be? i guess i could just test it..

I am not aware of any limits on the length of the raw names. I have used some longer (10+ characters) hyphenated names with no problems.

Alright Guys.. got another one for ya! using the code below in combination with the set tags button code is there a way if it returns the value of "no" for it to ignore that value and not place a tag, where if the value is returned as yes, it sets the tag?

Quest
label: Does NPC offer Quests?
type: select
values:
no: "no"
QuestGiver: "Yes"
default: no

If you go to my test page at http://vineyard.wikidot.com/menu:_template and also look at any of the pages created from that, menu:1, menu2: etc, you'll see that it only sets the tags for the items that are selected. Items not selected, where the value is None do not have the tag set. Even if you set a value to something, save it it and set the tag, then change it back to None and save the tag again, it then removes the tag. That is because the form_raw of no is a reserved value and so it doesn't set it. If it was called something else , 0 or Not for example, then it would set that tag. It works only because the value is no: None. Try it on my pages and you'll see what I mean.

Don't forget that the solutions we have been giving you are basically workarounds; without a tags field we have had to spend many hours working out a way of achieving these things - and not everything is always possible.

I was just coming back to edit my post and say to disregard due to after doing some testing, it appeared that it wasnt placing a tag of "no" on the page.

Unfortunatly there isnt a tags field yet, and I really appreciate all of the help, effort and work that everyone has put into making these work arounds work! they have been a god send and allowed me to do things with my site i probably wouldnt have been able to do otherwise! Thank you!

Not sure if this would help: http://snippets.wikidot.com/code:conditional-blocks to differentiate between some content of the form fields ( after creation/save) .

Question:

That is because the form_raw of no is a reserved value and so it doesn't set it. If it was called something else , 0 or Not for example, then it would set that tag. It works only because the value is no: None

I hear the first time of such reserved word - for tags setting!

If this is true - please would someone who understand this fact (and can explain it - Rob ?) write some explaining notes into the glossary of Tags?
http://community.wikidot.com/glossary:tags

It's not reserved words for tags exactly, it's reserved words in dataforms which, because they are reserved, won't be set for tags set from a dataform via the set-tags button. The current wording in the dataforms documentations refers to them as "Special YAML symbols, but reserved words might (or might not) be a better description:

"In case of special YAML symbols like true, false, yes, no, you may need to surround those with simple quote signs like this: "yes"."

This does not affect tags you set on normal pages. Nor does it affect tags set by the options button at the bottom of a dataform page. It only affects tags set from a dataform value by the set-tags button.

I don't think an explanation should go into the tags glossary because it is a very specific use case, but there is an explanation in the upcoming revision to dataforms documentation.

Hey guys, i ran into something else, using the match code as the example:

fields:
npc:
label: Start NPC
type: text
match: /^[a-zA-Z0-9-_]+$/
match-error: NPC must not have a space between words but can have a hyphen or underscore

if the field is left blank, as it is a optional field, it kicks the match error when trying to enter the data and save the form. I tried to use required: false attribute, but didn't help

more of a data form question, but..

Tweak the front end of your expression so the whole string looks like this:

/^$|^[a-zA-Z0-9-_]+$/

The ^$ matches an empty string. The pipe (|) creates an "or" condition. This is the trick to make match fields optional.

ahhh.. Perfect, Once again Thank you Ed!!