Page MenuHomePhabricator

Static, hidden text areas
Closed, ResolvedPublic

Description

Author: morgon.kanter

Description:
My wiki uses Semantic Forms extensively to create new pages -- for approximately half of our content, it is an excellent newbie-friendly way to add content. However, an issue we have is preventing its use in an additional 25% of cases that we'd really like to use it -- and that is where we really need the ability to define out-of-template text in each form. This includes categories (for a variety of reasons we do not wish to include these in templates, and semantic properties do not cover what we want categories to cover), breadcrumbs, _separation of templates with text_ (this is important, so we can add things like breadcrumbs to a specific part of the page in the first place) and other generally static text that goes on each page.

We can do this with the "free text" input, and in a couple cases we do, but it's not enough: we can only define one free text input, and often times we want the ability to define some static text at various parts of the page, not just one. In addition in almost all cases we want users to actually be able to input free text, and saying "do not edit anything below this line" kills the entire newbie-friendly nature of the form.

Thus, we would really appreciate it if there was some sort of "static text" input type, similar to the "free text" input, that we could define at multiple points in the page and give preloaded text to. This would pretty much solve all our problems with this otherwise wonderful extension.


Version: unspecified
Severity: enhancement
URL: http://dungeons.wikia.com/wiki/Form:3.5e_Deity

Details

Reference
bz21971

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:48 PM
bzimport set Reference to bz21971.

Not going to happen any time soon. If you want to discuss this further, the semediawiki-user mailing list is a good venue for it.

I don't know if you're still involved with Semantic Forms, or still care about this issue, but I would say the "section" tag, introduced in version 2.6, essentially solves this - each section can hold its own free text. I'm marking this as "fixed".