[[div class="show-data" style="background-color: #FEF5AF; padding: 10px;"]] Order Status Note: %%form_data{adminnotes}%% [[/div]] 

 [[module CSS]] .form-row.row-3, .show-data { display: table-row !important; } [[/module]] [[module CSS]] .form-row.row-3, .show-data { display: none; } [[/module]] 

Thanks again. This is great stuff!

What I'm stuck on right now is that I'd like to somehow create an "administrative notes" field in the form so that the site admins can enter specific notes about the status of the order beyond the tags.

I think I may have found a way to do this.

If you see this page, only Ed Johnson and I are able to edit the Notes section. The notes section is invisible to everyone else.

This is all done with the following snippet on the _template page along with some other pages:

 [[module CSS]] .form-row.row-3{ display: none; } [[/module]] [[div style="display : none;"]] [[module ListUsers users="."]] [[include css:%%name%%]] [[/module]] [[/div]] 

I am able to view it because the page css:timothy-foster has the following code on it:

 [[module CSS]] .form-row.row-3{ display: table-row !important; } [[/module]] 

The same goes with css:ed-johnson. Obviously, you would need to change the row number based on the row your notes section appears on. Unfortunately, the row's name cannot be used since for some reason the label is not included.

Now, since the _template CSS module will not be invoked upon page creation, it is better to put it on the nav:side page or something so that in can be applied to new pages. Interestingly, James recently made an article about how to do that.

I hope this helps.

I use SUO to display the admin buttons and menus. The buttons are used to manipulate the tags and [[iftags]] is used to display the content.

This prevents the display in an easy way…

This could work like the old "talk" option of Wikidot - a parallel category to every page..

my idea is more like - the iftags of the SUO to insert into the OUTPUT block if a ListPages module which is listing/showing the content of the SEPARATE Notices pages/category.
like
[[module ListPages category="notices" parent="%%fullname%%" ]]
[[iftags SUO...
%%content%%
[[/iftags]]
[[/module]]

I'm using tags to track the order status (i.e. _new, _inprocess, _completed). What I'm stuck on right now is that I'd like to somehow create an "administrative notes" field in the form so that the site admins can enter specific notes about the status of the order beyond the tags. I was hoping for some clever use of CSS to hide the field from customers and only display it for site admins when editing the form. Since I wasn't able to figure that out, I ended up using per page comments to accomplish this. With proper permissions and some CSS tweaks I was able to hide the per page comments from customers. This works OK, but I'd really prefer to use a single form field to collect these notes.

As a side note, I came up with a "poor man's captcha" that some may find useful to prevent robots from filling out the forms and submitting them. It uses regular expressions to allow only specific text (e.g. "CONFIRM") and it effectively makes the field required and it won't save until the proper phrase is entered into the text box. I also used it as a means for the users to agree to the terms of the sample program.

  terms: label: Terms type: static value: The terms of the agreement go here... acceptterms: label: Type ACCEPT to agree to these terms type: text width: 10 match: /^ACCEPT/ 

Another thing I learned that I didn't realize is that you can use the [[module css]] inside an [[iftags]] block. There was one element of the comments module I could not hide from just customers (the "Add a New Comment" button), so I used the following code to toggle the display of the comments module #thread-container on and off:

 [[iftags -_notes]] [[module css]] #thread-container { display: none; } [[/module]] [[/iftags]] [[iftags +_notes]] [[module css]] #thread-container { display: block; } [[/module]] [[/iftags]] [[button set-tags +_notes text="Show Order Status Notes" class="tag-buttons"]] [[button set-tags -_notes text="Hide Order Status Notes" class="tag-buttons"]] 

Has anyone run into a need like this and found a solution? Like I said, my current solution works fine, but my primary user would have an easier time editing a single form field for his notes.

I have relaxed permissions so Wikidot user can view page options and the source. My form template pages are here:
http://www.mascot-golf.com/orders:_template
http://www.mascot-golf.com/sample:_template

Thanks!

Therefore it should be possible (and even customary) for a knowl to live in its own page and then to be included (invoked) where needed. This is missing from the present demonstration implementation, which nevertheless seems to show that it is all possible in principle.

This is actually possible. I added it to the demonstration. You can make a separate page and put a code block on it. Then, you can reference it from any page using the general format:

 <a knowl="http://SITENAME.wdfiles.com/local--code/PAGENAME">Text</a> 

David emphasizes another point that I had noticed too, and I repeat it: the primary use for the knowl is as a self-contained piece of text that can be incorporated into multiple other pages. Therefore it should be possible (and even customary) for a knowl to live in its own page and then to be included (invoked) where needed. This is missing from the present demonstration implementation, which nevertheless seems to show that it is all possible in principle.

The knowl is very similar to a link, either within the same wiki or to an external location, and the syntax should probably reflect that. With wikidot we have
[[[some page| custom text]]]
to make the phrase "custom text" an active link to a wikidot page; we have
[[[http://www.example.com | custom text]]]
to link to an external page; and we have
[[[doc#toc1| custom text]]]
to link to an anchor within a wikidot page.

I would say that the Knowls should have a syntax that is close, but not identical. In the spirit of using [[$ … $]] for inline equations from MathJax that spirit the knowl could be denoted by something such as

[[& some page| custom text &]]

(or using whatever symbol is available instead of "&".

Of course I rated up the wish http://feedback.wikidot.com/wish:753 (Implement an easier KNOWL usage)

* [/library-hours Hours] to the top nav bar would be quick and convenient for your visitors.

 [[iftags -open]] [[button set-tags +open text="Set Page Tag to open."]] [[/iftags]] 

Too many variable tags using search? Meh, I don't know off hand if data forms (raw or otherwise) can be used to set a tag but if so that might be the easiest way.

Edit: Check this thread.

Or - is there another good idea like collapsible blocks INLINE (in a line) and NESTED ?