Last modified: 2013-12-24 02:30:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 21971 - Static, hidden text areas
Static, hidden text areas
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
SemanticForms (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Yaron Koren
http://dungeons.wikia.com/wiki/Form:3...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-30 19:44 UTC by Morgon Kanter
Modified: 2013-12-24 02:30 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Morgon Kanter 2009-12-30 19:44:01 UTC
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.
Comment 1 Yaron Koren 2010-02-02 21:00:45 UTC
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.
Comment 2 Yaron Koren 2013-12-24 02:30:12 UTC
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".

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links