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.
Update: actually it's not related to static fields. I've just tried to save a live template at http://vineyard.wikidot.com/settags:_template where the dataform doesn't have a static field and I get the same error screen. it worked late last night so something has broken dataforms this morning
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
I have forms running with static fields with no problems for me
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
There need to be a space after colon.
label: School
More information at:
Symfony doc - simple shortcut
YAML homepage - oficial specification
Bartłomiej Bąkowski @ Wikidot Inc.
';.;' TeRq (Write PM)
Wikidot's now checking Data Forms against the YAML standard, so things that might have worked before (but weren't 100% valid YAML) won't work now and would need to be updated slightly.
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server
This is really bad: changing something that breaks existing forms with no warning at all. I (and everyone else who builds sites with dataforms) now have to go and check every single live template on every single site we've built. I am not at all pleased. It would have been courteous to have notified us of this.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
I remember a discussion on the community forum a long time ago about whether the space was or was not required but as far as I recall there was nothing in the original documentation about it or anything ever said by Wikidot about it. So I will undoubtedly have dataforms with a mix of space and no-space, as will possibly a lot of other people.
First rule of IT software development: don't do something that breaks existing functionality! And if you do then give users a chance to do something about it over a period of time (as you did with IP addresses) rather than just break it. Didn't you realise what the effect would be?
And just pointing us to the YAML documentation is really unhelpful.
I'd better have a glass of wine to cool down or else there'll be a rant on Twitter this evening. You guys have got me really really cross.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
In the documentation I wrote for dataforms I said:
"In order for the sort to work correctly, numbers below 10 must have a property of 01, 02, 03 etc. although the value can still be 1, 2, 3 etc as in the example data form field above. It is the value that is displayed in the ListPages module, as shown below. You must also make sure that there is no space between the colon and the value, i.e. it should be this 01:1 not 01: 1. This is critical where there are more than about 8 possible selections in your field."
So I guess sorting on numerical values is now broken and the documentation will need to be altered.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
Without being rude Rob, this is not favourable advice. Prepending digits with zero causes YAML to interpret the numbers as Octal numbers.
See this bug (and more particularly, this post) for reference.
λ James Kanjo
Blog | Wikidot Expert | λ and Proud
Web Developer | HTML | CSS | JavaScript
15 minutes so far trying to debug the first template (http://vineyard.wikidot.com/band:_template)!
Definitions like:
Broken! Can't be saved.
Edit: It's the default: 0 than no longer works, the rest is OK. If we are using raw values what can we use instead of default: 0? I'll probably just leave it out altogether for now.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
Default values now don't seem to work at all. Ignore that, I got one to work.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
there is a wrong indentation in line with default: 0
Bartłomiej Bąkowski @ Wikidot Inc.
';.;' TeRq (Write PM)
Yes on that one I'd introduced an extra space. So the default: 0 does work now.
But this is why it is going so **ing long to check my 88 sites; a single spacing error in a single definition on a single live template page and it falls apart.Let alone the other problems with the sorting and numerical fields.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
Just to confirm: the sorting on numerical values is now broken. http://vineyard.wikidot.com/bands:main
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
And if you have a select field of numerical values, e.g
When you edit the page the 8 is missing. James explained it was something to do with octals. It worked when the definition was 08:8 as I explained in a post above. But now it's all broken.
Please provide some syntax for this that not only shows the 8 when you edit the form but then works when used with sorting by the dataform value in a listpages module.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.