Extension talk:Page Forms/Archive September to October 2010

Forms different from when you create and when you edit?

Ok, so far I've made a CreateCharacter and a Character form. CreateCharacter attaches this article template (basically with all the sections needed and the layout but not filled in) but removes the option to edit the text, whereas Character form removes the template and lets you edit with free text. Do I not need to do this?--Technobliterator 10:46, 1 September 2010 (UTC)Reply[reply]

It depends - why are you doing it? Yaron Koren 11:41, 1 September 2010 (UTC)Reply[reply]

Minor edit flag doesn't seem to be passing

I've upgraded to 2.0 and the minor edit flag is not being passed through to MW and the edit is not marked as minor. Tested on several forms. Thorncrag 21:39, 2 September 2010 (UTC)Reply[reply]

I've verified this on Scratchpad. Minor edits are not being flagged. Thorncrag 18:32, 8 September 2010 (UTC)Reply[reply]
I've verified this on an additional wiki with SF installed. Thorncrag 00:36, 9 September 2010 (UTC)Reply[reply]
Thanks for the bug reports - this is fixed now in version 2.0.1. Yaron Koren 15:24, 1 October 2010 (UTC)Reply[reply]

Add parameter 'uploadable' from GUI

When constructing a form, the docs says I should add the parameter 'uploadable' to the field which is to hold a file to be uploaded. And that works - I add the form, edit the source and add the parameter to the field. But how can I do this without having to edit the form source? That's not exactly friendly from a regular user's perspective ;) So what I'm looking for is a checkbox (or an input type?) besides every field. --Tadej Kanižar

Regular users shouldn't be modifying the form in the first place, don't you think? Yaron Koren 07:47, 8 September 2010 (UTC)Reply[reply]
Yes, of course .. but not all of the admins are as skillful. And even if they are, it's still not very friendly.
So, is there a way to do this? --Tadej Kanižar
No, sorry - I fear that admins will actually have to type in the word "uploadable". Yaron Koren 04:07, 12 September 2010 (UTC)Reply[reply]

Edit with form button in .css

what is the edit with form button in ;.css if I want to add an image to it?--Technobliterator 20:54, 6 September 2010 (UTC)Reply[reply]

Fancybox not working.

I got the form correct but everytime i click the upload link, it goes into a new page instead of having it float a fancybox.

What's your MediaWiki version, and browser? Yaron Koren 07:48, 8 September 2010 (UTC)Reply[reply]

Its version 1.16 and firefox browser. Do you think the short url might be the problem?

Having the same issue as well. Fancybox works on previous forms, but any new pages created with a form and FancyBox simply redirects and does not float. --BrettFerguson 01:10, 9 September 2010 (UTC)Reply[reply]
Are you by any chance using the uploadable field in a multi instance template in a form ? I had the same problem in that situation and had to fix a few things in Semantic Forms. --Tadej Kanižar
Yes, I just checked. This issue is only causing problems in multi-instance templates using the uploadable field. --BrettFerguson 01:18, 12 September 2010 (UTC)Reply[reply]
Replace your SemanticForms/includes/SF_FormInputs.php with my version - http://www.ncode.si/mediawiki/SF_FormInputs.php.txt --Tadejkan 03:03, 12 September 2010 (UTC)Reply[reply]
Thank you. That fixed it! --BrettFerguson 04:08, 12 September 2010 (UTC)Reply[reply]
I believe this is fixed now for SF in SVN, using an approach similar to Tadej's. Yaron Koren 13:28, 12 September 2010 (UTC)Reply[reply]

Multiple-instance templates are broken in IE8

Hi Yaron, there seems to be a Problem with the IE 8 (maybe the older ones too), the "Add another" / "Remove" Buttons doesn't work. Try your own Example in the IE. The "Show On Select" Divs are although effected by the same Bug. SBachenberg 13:21, 7 September 2010 (UTC)Reply[reply]

Thanks for letting me know about that - once again, I foolishly forgot to test in IE... the problem was a single excess comma in the FancyBox declaration. The fix is now checked in to SVN. Yaron Koren 05:30, 12 September 2010 (UTC)Reply[reply]
Is "show on select" supposed to be working when used in multiple instance templates? --Dgennaro 19:33, 21 September 2010 (UTC)Reply[reply]
It should be, yes - if it's not working with the latest version of the code, please let me know. Yaron Koren 19:40, 21 September 2010 (UTC)Reply[reply]
It is not working. I have reproduced the error on Discourse DB here. Hope this helps. --Dgennaro 15:31, 22 September 2010 (UTC)Reply[reply]
I upgraded to SF v2.0.1 and I am still unable to get the multiple instance templates working. I have made a sample on Referata Scratchpad. I have been trying on both IE7 and Firefox 3.6.6. Sorry to keep bugging you with the same problem, but I hope this helps. --Dgennaro 16:20, 5 October 2010 (UTC)Reply[reply]
Hi, yes - there's definitely a bug with "show on select" in multiple-instance templates. Unfortunately, it might be difficult to fix, so I can't say if/when it'll work fully. Yaron Koren 16:28, 5 October 2010 (UTC)Reply[reply]
Thanks for the update. I will wait patiently. --Dgennaro 17:15, 5 October 2010 (UTC)Reply[reply]

old state of /branches/REL1_16/extensions/SemanticForms in SVN

I realized that the 1.16 branch in SVN is outdated (includes SemanticForms 1.8.8) is that intentionally? I thaught 1.9.x and 2.0.x fits Mediawiki 1.16 also ... btw also SemanticMediawiki is 6 months old in that branch (RELEASE_NOTES mention version 1.5.? (!!!) ) --RScheiber 16:00, 9 September 2010 (UTC)Reply[reply]

It's generally a bad idea to use the MediaWiki release branch versions of these extensions - if you want to use a tagged version, the directly tagged versions are the way to go; most of the SMW-based extensions are tagged. Yaron Koren 04:13, 12 September 2010 (UTC)Reply[reply]
There is no 2.0 tag in svn ... the Extension page mentions 2.0 as current ... is it finished? When will you set the tag? btw, huge thank you for the great work and the minimal response time on the talk page! RScheiber 21:16, 14 September 2010 (UTC)Reply[reply]
I'll probably skip right to a tag for 2.0.1, since 2.0 has had a bunch of bugs; and that will probably come out in the next week. Yaron Koren 22:07, 14 September 2010 (UTC)Reply[reply]
Now there is the zipped 2.0.1 Release file, there is 2.0.1 in SVN, but the SVN tag is still missing. --RScheiber 15:56, 30 September 2010 (UTC)Reply[reply]
Hi - I just added it. Yaron Koren 02:30, 1 October 2010 (UTC)Reply[reply]

How do you properly create a subpage link in a template?

I have a Property "Has division" of type Page. In a template, I've modified the link to point to a subpage, something like this:

[[Has division::{{PAGENAME}}/{{{Division|}}}|{{{Division|}}}]]

This works as intended, eventually creating a link to a subpage of the parent. However, if such a definition is followed by an enumerated string, a parsing error occurs on the including Form. For example, I have a Property "Has style" of type string with four possible values. If I add it to the above mentioned template like so,

! Division
[[Has division::{{PAGENAME}}/{{{Division|}}}|{{{Division|}}}]]
! Style
| [[Has style::{{{Style|}}}]]

there will be an error when I add this template to Special:CreateForm, not allowing me to choose the radiobutton input type for Has style. If I then edit the form manually, and force it to be of type radiobutton, only one button option appears, "None". (No, I don't have property "Has style" defined incorrectly. If I take {{PAGENAME}}/ out of the template definition for Division, all expected radio buttons appear; but then I'm left with no subpage link.)

I've tried modifying the template definition of Division in several different ways, but nothing seems to work. For example,

[[{{PAGENAME}}/Has division::{{{Division|}}}|{{{Division|}}}]]
[[Has division::/{{{Division|}}}|{{{Division|}}}]]
[[{{PAGENAME}}/[[Has division::{{{Division|}}}]]]]

Any ideas on how to accomplish this successfully? I'm open to suggestions. Thanks.

"Show on select" seems to work only once in a form

Hi! I have build a form with two fields with a "Show on select" option. But only the first field seems to work correctly - in the second one, all divs are shown before the user has selected the value of the field. If I select a value for the second field, however, the form hides the divs that are related to the other values, but only if the second field is of type "dropdown" (with "radiobutton" or "checkbox" it doesn't work at all). The same issue occurs if I set a default value for the second field. I have reproduced the error in Referata Scratchpad here with a very simple example form. Is this a bug or is the "show on select" function designed to be used only once in a form? Or have I made a mistake and don't get it? Regards --Daniel5000 17:19, 10 September 2010 (UTC)Reply[reply]

Are you using the newest Version of Semantic Forms? Try an update with the newest version from SVN. The Funny Thing in you wiki is, that "option 1" always works with all input types. The ShowOnSelect JS sometimes generates null pointer exeptions, because of some missing Value checks maybe thats the Problem. -- SBachenberg
Hi Daniel5000, thanks for reproducing the bug. The problem came about because you had an extra semicolon at the end of one of your "show on select"s - not that that should cause the Javascript to break. I just fixed the bug in SVN. Yaron Koren 04:38, 12 September 2010 (UTC)Reply[reply]
Thank you very much! In Referata now it seems to work, now I will try it in my own wiki. --Daniel5000 06:46, 12 September 2010 (UTC) It works without problems now (revision 72839).--Daniel5000 17:02, 13 September 2010 (UTC)Reply[reply]

No Edit With Form Tab

Hi, I also have trouble with the Edit with Form. I am not getting a tab. I have tried some of the above suggestions, but everything looks ok, commenting out and refreshing didn't help. In my local settings I have these extensions, in this order: cite, recaptcha, SMW, SF, SemanticCompoundQueries, validator, maps, semantic maps. Could the order affect this? I'm using SF 2.0 with 1.16. Here's a test page on my site- http://emswiki.com/index.php/Kjh Thanks,--Aj2479 21:04, 12 September 2010 (UTC)Reply[reply]

Hi - I think there might be some problem in the wiki-text for one of your templates that's confusing the parser. In any case, the recommended way to get an "edit with form" tab on the page is via categories. Yaron Koren 07:13, 13 September 2010 (UTC)Reply[reply]
Here's a simpler page. http://emswiki.com/index.php/Asdfasdf. I just can't think what I am doing wrong, but will keep playing around with it. Thanks, --Aj2479 08:13, 13 September 2010 (UTC)Reply[reply]
Okay, that's very odd - there's something going wrong with Semantic Forms there. Feel free to email me privately about it - it may require having to go into your system, if that's possible. Yaron Koren 08:49, 13 September 2010 (UTC)Reply[reply]
This was resolved by email - the issue was an old version of SMW (1.5h) that was causing problems. Yaron Koren 22:09, 14 September 2010 (UTC)Reply[reply]

No Edit With Form Tab + enforce use of forms?

I might have a similar Problem here. Using MediaWiki 1.16 with SMW 1.5.2 and SF 2.0.1 i cannot get the "Edit with Forms" Tab to show up at all. I tried to follow instructioncs for both, attaching my form "Form:User" to the category "Users" as well as the "MediaWiki:User" namespace. In both cases i added the line: [[Has default form::User]]. This creates a link "User" on the page, which leads to my Form:User with the "Create or Edit" button.

Using the "Vector" Skin as default here, but that doesn't seem to have any influence.

  • Do i have to create the property manually? Didn't see anything about it in the manual, nor about activating the tab feature somewhere.
    • Can i somehow check if the property is actually existent? I don't see it in the list of properties (wiki/index.php/Special:Properties), but i guess that's because its either hidden or unused as of yet.
  • Can i somehow enforce the use of forms, i.e. when it comes to adding/editing user data when clicking the username on the wiki?

Aside from that, thanks for your ongoing support on this great extension. :)

Hi - that sounds bad. When you go to the "Browse properties" link in the sidebar from either the category or namespace page, do you see the "Has default form" there? If not, that's the issue. For the second question, see the 3rd item here. Yaron Koren 16:41, 18 October 2010 (UTC)Reply[reply]
Hey there. I did some more testing but didn't get any better results:
    • Created a Testcategory and attached form "User" to it. After assigning (new) pages to that category, no change to the tabs occured.
    • When klicking "Browse Properties" in the Toolbox, the property appears on each page having the [[Has default form::User]] text inside. Even manually adding it to my (User:Admin) userpage does not change the tab behavior.
    • Could a missing or incorrect form-template be the problem? I recently changed the form to collect more semantic data, but left the templates as is. It's just a separate thing for displaying (a selection of) data, isn't it?
    • I might just try creating a new Wiki and test it again as there is only little to no content on my current testversion. Building up a rather extensive knowledgebase for my company so SMW is a must-have. Using "XAMPP package 1.7.2 here (using PHP 5.3.0 due to the Wiki incompatiblity with 5.3.1).
    • Could $wgContentNamespaces be the problem? I once had an own namespace in the 110+119 Region but disabled the corresponding array and $wgExtraNamespaces[110] lines for SMW.
    • I feel like i'm missing something important here. Just adding the [[Has default form::...]] after creating my form thing seems to be too...easy.

Mike, 07:45, 19 October 2010 (UTC)Reply[reply]

Hi - it sounds like something is wrong; it really should be that easy. :) Maybe it's the namespaces issue, I don't know. Creating a new wiki might be the easiest solution. Yaron Koren 13:27, 19 October 2010 (UTC)Reply[reply]
I'm back with an update. I installed a fresh wiki on my local XAMPP server, new DB with new tables. Versions installed are the exactly same as listed above. To speed things up i just created a Class using the SMF menu and assigned the new form to the Users-Category [[Has default form::User]]. . After editing my own Userpage (Admin) and assigning it to the category "Users" i get no "Edit with form" Tab displayed. My "Localsettings.php" remains unaltered except for the SMW and SF include_once-entries. The extensions seem to run fine otherwiese. The only options left now are:
  • Something is very wrong with my combination of XAMPP and Plugins.
  • I'm just horribliy stupid and forgot something very important to do. I just can't put my finger on it.
Just to make sure I will re-download the SMW and SF extensions and conduct some further testing on Monday. After that i'm outta ideas! The last way would be to "MANUALLY" add the "Edit with forms" Button to the Wiki, probably using a hack. :/ Mike, -- 14:42, 22 October 2010 (UTC) (Ironically, i work as a Softwaretester)Reply[reply]
EDITEDIT: Works now. Obviously the SMW snapshot was the problem. Displaying as 1.5.2 Trunk i was assuming that this is a stable and working version. The SourceForge-Version however is 1.5.2 as well, but showing a "Edit with Form" Tab. God i feel so DUMB!. Then again i wonder why they dislay the "Snapshot" in bold letters. I was assuming that snapshots are stable versions for people without access to SVN - and not suspicious nightly builds.

Anyways, thanks for the support. Problem resolved - User Error! ;)

Pivot and combine multiple instance template tables on final saved page

I want to modify the way the final page looks for multiple-instance templates. Specifically, I would like multiple-instance templates to be pivoted and flattened, so that the property labels become column names and each template instance is a row in the table.

For example, I have a template "Template:Event_Date" that consists of a date and a venue:

{{Event Date

In the including form, I selected the "Allow for multiple (or zero) instances of this template in the created page" check box. On the final, saved page, each instance of this data is stored in its own table:

{{Event Date
|Date=January 1, 2010
|Venue=Madison Square Garden
{{Event Date
|Date=January 2, 2010
|Venue=Empire State Building

I want the final page output in a single table, like this:

January 1, 2010 Madison Square Garden
January 2, 2010 Empire State Building

I don't think this is possible just by modifying Template:Event_Date, but maybe I'm wrong? If I need to modify PHP to get this to work, I will. Just point me in the right direction. Thanks.

Hi - you can definitely do this; you just need to use a "header" and "footer" template above and below that multiple-instance template, to handle the top and bottom of the table. You can easily include templates without any fields into the form, just by using "for template" and "end template" with nothing in between. By the way, I would also recommend storing the data, using #set_internal from the Semantic Internal Objects extension, so that you can query and display a similar table of that data from any other page. Yaron Koren 21:49, 13 September 2010 (UTC)Reply[reply]
Yaron, Is it possible to show on the form the multiple instances of a template in tabular format? The template is a semantic internal object repeated 0 or more times. The goal is for the form to display the multiple instances in one "formtable" with the property names appearing at the top as column labels. Otherwise, the form becomes cluttered with the property names/labels repeated every time the user "Add Another". Maybe something similar to the following. Paul Ramer 9:45pm, 30 September 2010 (MST)
January 1, 2010 Madison Square Garden
January 2, 2010 Empire State Building
I don't understand - isn't this the same question as above? Yaron Koren 12:34, 1 October 2010 (UTC)Reply[reply]
I was afraid of that. How does one make the header and footer templates in the form? This is what I have so far, but I don't think it is quite what you intended in your explanation. -Paul Ramer 7:40 AM, 1 October 2010 MST

{{{for template}}}
{| class="formtable"
!Completed !! Due Date !! Subject |}
{{{end template}}}

{{{for template|Status Report|label=Status Report|multiple}}}
{{{field|Completed|input type=checkbox}}} {{{field|Due Date}}}  {{{field|Comments}}}
{{{end template}}}

You're close - just put those two lines of wiki text into their own template, called, say, "Template:Status Report Header", and then change that part of the form definition to:

{{{for template|Status Report Header}}}
{{{end template}}}

...and then you should have something similar for the footer, of course. Yaron Koren 15:11, 1 October 2010 (UTC)Reply[reply]

Actually, I think I might be asking a different question. Most of the discussion seems focused on the display of multiple templates on a page after it is saved (the stuff people see when they first navigate to a wiki page). The combination of a SIO to store each instance of a multiple instance template and the use of queries to control the final display of the data seems quite effective for that purpose. I am trying to control the appearance of the form (edit with form tab) where the multiple instance template is generated. If I understand the forms, they are typically set up as a 'formtable' with labels and fields where users enter data. Upon saving the page, the form in effect inserts the template along with the data into the wiki page (what is seen on the 'edit' tab). I would like to have one set of column labels in the form itself instead of new labels and new fields every time I 'Add Another'. If I am still missing the point, I apologize and will just need to think about this further. Paul Ramer -- 20:21, 1 October 2010 (UTC)Reply[reply]
Just to clarify - you're only asking about making the form itself look nicer, not the pages created by the form? Yaron Koren 04:37, 3 October 2010 (UTC)Reply[reply]
Yes. Paul Ramer -- 21:33, 4 October 2010 (UTC)Reply[reply]
Okay - such a thing is unfortunately not possible, but there's a long-term plan in place to enable it. Yaron Koren 22:19, 4 October 2010 (UTC)Reply[reply]

default=current user does not work as expected

Hi Yaroen,

thanks for your great work!

Using a text input for a string with default=current user I would expect e.g. John Doe. Instead, I get User:John Doe. This annoys me especcially, as I want to use this parameter for the definition of the page name, which thus is in another namespace...

Do you see a solution for this?


Nico -- 12:17, 14 September 2010 (UTC)Reply[reply]

Hi - I can't reproduce this problem; for me it's always the username without "User:". Could you try replicating it on a public wiki, like scratchpad.referata.com? Yaron Koren 20:48, 15 September 2010 (UTC)Reply[reply]
Hi Yaron, I could not reproduce it on scratchpad. These are the versions I use, do you have any suggestions where to look at for the problem?
  • MediaWiki 1.15.5
  • PHP 5.2.10-2ubuntu6.4 (cgi-fcgi)
  • MySQL 5.1.41-3ubuntu12.6
  • Semantic MediaWiki (Version 1.5.2)
  • Semantic Forms (Version 1.9.1_1)
  • Data Import Extension (Version 1.4.0_2)
  • External Data (Version 1.0.1)
  • ParserFunctions (Version 1.1.1)
  • ScriptManager Extension (Version 1.0.0_0)
  • Semantic Internal Objects (Version 0.6)
  • SMWHalo Extension (Version 1.5.1_1-for-SMW-1.5.1 [B59])
  • StringFunctions (Version 2.0.3)
  • [ URL Arguments] (Version 1.0)
  • Variables (Version 1.3)
  • HaloACL (Version 1.2.0_0)
  • IAI (Version 0.1)
  • LinkedData (Version Template:$VERSION)
  • Semantic Gardening extension v1.3.2_1
  • Semantic Result Formats (Version 1.5.0_1)
Quite a lot, I know. I used the deployment framwework of ontoprise. In case you dont have a clue, I would try to redeploy it with fewer extensions. Obviously, there are non obvious dependencies concerning the order of deployment... ;o)
Thanks for your assistance! Nico -- 16:23, 22 September 2010 (UTC)Reply[reply]
Ah, that explains it - you're using the modified version of Semantic Forms that comes with SMW+. I would talk to ontoprise about it - it looks like there's some sort of bug in their version. Yaron Koren 16:36, 22 September 2010 (UTC)Reply[reply]

Required Versions of MW and SMW not mentioned on Extension Page

The required versions of MW and SMW for SF 2.0 are not mentioned on the page. Putting a small table in the Version section or a new requirements section would be great, which includes the required minimal version of both and perhaps a recommended version. EX:

Semantic Forms version required Mediawiki Version required Semantic Mediawiki Version
2.0 xx.y 1.z

--RScheiber 21:07, 14 September 2010 (UTC)Reply[reply]

The requirements are both there on the page, although you have to look carefully - MW 1.12, SMW 1.4. And the "Version history" page gives some more information on when support for previous versions has dropped... I hope that's enough. Yaron Koren 22:12, 14 September 2010 (UTC)Reply[reply]

Order of multiple-instance items and collapsing?

I want to change the order of the instances, so that they are ordered from newest to oldest on the resulting page. In the archieve I read the question about drag and drop ordering while editing a form, but maybe reversing the order is simpler than drag and drop while editing the form. Is there a way to achieve this? If I have to edit code could you please give me a hint where to look for it? I also would like the ability to collapse the instances in the form, that sounds more complicated though. -- Meera 11:50, 15 September 2010 (UTC)Reply[reply]

Neither one is possible, unfortunately. Adding the first to SF is difficult enough that I wouldn't encourage anyone to try it unless they 100% knew what they were doing. Instead, I would recommend to not actually display those templates on the page, but rather to store their values using #set_internal from Semantic Internal Objects, and then query the data on that same page - that way you have complete control over sorting. Yaron Koren 12:19, 15 September 2010 (UTC)Reply[reply]
Thank you for your fast reply! I will look into Semantic Internal Objects. -- Meera 15 September 2010 (UTC)

Downgraded from MediaWiki 1.17 trunk to 1.16 branch and lost Edit with Form Tab

I had the Edit with Form tab via the recommended Category configuration. I downgraded everything to 1.16 branch to get a theme to work, now I've lost the Edit with Form tab. I've run a full reinstall of Semantic MediaWiki without luck. Any ideas? --Brimstone 02:49, 16 September 2010 (UTC)Reply[reply]

What versions of SMW and SF are you using? Yaron Koren 06:07, 16 September 2010 (UTC)Reply[reply]
I'm using SMW Version 1.5h-SVN, SF: Version 1.8.8 from r73018 at http://svn.wikimedia.org/svnroot/mediawiki/branches/REL1_16. Thanks for taking the time to look into this. --Brimstone 15:50, 16 September 2010 (UTC)Reply[reply]
Ah, that's it! There's been a spate recently of people using the "REL1_16" branch recently and, inevitably, having problems. As I said in a response above, those branches should almost never be used for extensions - they're old and basically random snapshots of the code. If you upgrade to the latest SMW and SF, it should work. Yaron Koren 17:45, 16 September 2010 (UTC)Reply[reply]
That was it, thanks! -- 18:04, 16 September 2010 (UTC)Reply[reply]

Position of partial forms

I would like to add partial forms to existing mediawiki pages. My problem is that the results of partial forms after entering data are alway shown at the top of the page - but I would like to include them after a section title. Please have a look at http://www.stomatocysts.unibe.ch/wiki/Pla:S001 there the results after entering the data should occur after section title 'ECOLOGY'. Any help would be highly appreciated! Christian

Hi - it's for that reason that I don't usually recommend using partial forms; actually, I've been thinking of getting rid of them for a long time. An alternate solution is to create a new form that looks like a partial form, by holding all the same templates as the regular form but having only the specific inputs that you need. That one should work a lot better. Yaron Koren 08:59, 23 September 2010 (UTC)Reply[reply]
The trick, passed on to me by several people, is to include the full form in the partial form so that the additional results are placed where you intended. The easiest way to do this is to just make the partial form the full form and hide the non-partial portion with
<div style="display:none"> non-partial form sections </div>
That said, if Yaron does get rid of them, the same form page could be used, with variable-based switching used to display one part or another of the total form. I was able to do this using Extension:UrlGetParameters. Leveraging a single form for both operations makes updates easier, especially if those updates involve adding a new template. --Skew 18:39, 24 October 2010 (UTC)Reply[reply]

Mandatory date field for multiple instance item

Setting a date field for a multiple instance item to mandatory causes the form to report all mandatory field inputs missing (regardless if they are empty or not). It is also not possible to save the form even if no instance of the item is added. I reproduced this on the scratchpad: MandatoryDateTest. --Meera 10:24, 20 September 2010 (UTC)Reply[reply]

Autocomplete for internal object properties?

Is it possible to configure autocomplete for a field based on the values of an attribute of a semantic internal object? --Meera 13:55, 20 September 2010 (UTC)Reply[reply]

Hi, definitely - you just need to explicitly connect the form field to the property by adding "|property=property name" to the field tag in the form definition. Yaron Koren 10:57, 21 September 2010 (UTC)Reply[reply]

fancybox errors...

   <script type="text/javascript">
   jQuery(document).ready(function() {
   Uncaught TypeError: Object #<an Object> has no method 'fancybox'
'width'  : '75%', 'height'  : '75%', 'autoScale' : false, 'transitionIn'  : 'none', 'transitionOut' : 'none', 'type'  : 'iframe', 'overlayColor'  : '#222', 'overlayOpacity' : '0.8', }); });

Uncaught TypeError: Object #<an Object> has no method 'fancybox'
(anonymous function)page:88
(anonymous function)jquery.min.js:308
(anonymous function)

--Kraziboi428 07:05, 23 September 2010 (UTC)Reply[reply]

Hi, yes - I believe this problem is just caused by the comma at the end of the 'overlayCapacity' line, which shouldn't be there. I already fixed that problem in SVN, and I plan to release a new version with the fix soon. Yaron Koren 08:54, 23 September 2010 (UTC)Reply[reply]

Hi, i just updated the file adding the comma, im still getting the same error.--Kraziboi428 17:15, 23 September 2010 (UTC)Reply[reply]

What versions of MW and SMW are you using, and are you using either Halo or the GuMax skin? Yaron Koren 17:53, 23 September 2010 (UTC)Reply[reply]

MW 1.16 and 1.5.2. GuMax Skin... i just updated the Jquery to the latest on the Gumax Skin.

Ah, I bet that's it - SF doesn't work with the GuMax skin any more, due to a Javascript conflict. Try switching to a different skin and see if that solves the problem. If so, I believe taking out the line in the GuMax skin that includes jQuery itself might fix the problem. Yaron Koren 19:09, 23 September 2010 (UTC)Reply[reply]

Good tip. It works now thanks Yaron!--Kraziboi428 20:37, 23 September 2010 (UTC)Reply[reply]

Alright, cool - I just added a note about it to the "Common problems" section. Yaron Koren 21:26, 23 September 2010 (UTC)Reply[reply]

Template misses its parameter when containing a link with "=" character in the URL

What is the solution for this bug with for template form markup language?

My workaround was to insert 1=http://www.myurl_with_equal_sign.org/ in the user interface form field, but its gone when re-editing the form. Anyway, this solution is non-intuitive for a regular user. Trying to save one more time the form, the link parameter won't even appear in the form field (it's blank).

Any advice would be greatly appreciated.--EuroDomenii 22:19, 23 September 2010 (UTC)Reply[reply]

Hi - I don't actually know what you mean; I haven't experienced problems with an equals sign in a template/form field. Could you reproduce the problem on a public wiki, like scratchpad.referata.com? Yaron Koren 23:55, 23 September 2010 (UTC)Reply[reply]

Thank your for this opportunity. Examples articles: http://scratchpad.referata.com/wiki/Link_equal_sample, http://scratchpad.referata.com/wiki/Link_equal_sample_no_form based on http://scratchpad.referata.com/wiki/Template:Linkequal

Oh - now I get it, thanks. I don't think there's any good solution - the only thing I can really suggest is to give those parameters names, or, as you note, to have things like "1=". Yaron Koren 20:11, 24 September 2010 (UTC)Reply[reply]

ask query in ask-query-template not working for pages created by Semantic Forms

First: thanks for your extensions and your answers to all questions!
I got the form and all working well. I have a page which creates statistics about wiki pages using semantic attributes. For this I use an ask-query with a custom table-template. That table-template uses other templates, parser functions and ask queries to get the desired information. The problem I ran into is: queries in the table-template for pages edited by semantic forms work fine, but queries in the table-template for pages which were created by semantic forms return nothing.
Thanks in advance. --Meera 09:17, 24 September 2010 (UTC)Reply[reply]

The way in which the page was created shouldn't have any effect on its semantic data. I'm almost sure the issue is something else, though I don't know what. Yaron Koren 15:05, 24 September 2010 (UTC)Reply[reply]
You were right, the problem was the internal object which was inserted by the form. With the newest version of Semantic Internal Objects (0.6.1 instead of 0.6) creating new pages works for the ask-queries! --Meera 11:13, 28 September 2010 (UTC)Reply[reply]

Preview won't work acceptably in Chrome and IE, but does in Firefox

I pulled this earlier since I was using questionable versions of some packages. Now I'm using a clean install of all extensions with my database:

MediaWiki 1.16.0
PHP 5.3.2-1ubuntu4.5 (apache2handler)
MySQL 5.1.41-3ubuntu12.6
Semantic MediaWiki 1.5.2
Semantic Forms 2.0.1
UsabilityInitiative Version 0.1.1 (but it happens with and without it loaded using monobook or vector)

Partial continuation of the discussion from July 9, 2010.
I also had the problem of hitting Show Preview during a form-based edit and not getting the right results. More specifically,

  • Chrome 6.0.472.63
    • Never saw it come back, let it sit there for an hour
  • Internet Explorer 8.0.6001.18702
    • Renders reasonably fast
    • I'm using <headertabs />, the tabs are showing, but they don't work
    • All of the tab contents are laid out consecutively as if no headertabs were present
  • Firefox 3.6.10
    • Renders reasonably fast
    • Tabs in the preview and the bottom form are intact at the bottom, but there's a huge vertical blank area between the preview and the form (about 20 screens)
    • If I change
<div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div>
<div id="wikiPreview" style="display: none;"></div>
the blank space is eliminated.

If I pull the "wikiPreview" line out,

  • Chrome shows the preview and the tabs fine
  • Firefox shows the preview and the tabs fine
  • IE shows the preview the no working headertabs and a sequential page

and all of them replace my form-based edit session with the standard edit box.

I really need to make this work with preview, and preferably on more than just Firefox.

  • Has anyone hit this problem and gotten it to work?
  • Could this be a database problem? I'll try a test install tomorrow with a new database just to see if empirically that could be the problem, but if anyone knows the fix and could let me know, I'd appreciate it.
  • Is there a caveat sheet on things that happen with the different browsers?

Thanks for reading. --Skew 05:45, 30 September 2010 (UTC)Reply[reply]

Hi - I would just take the "wikiPreview" line out; it was really only meant as a convenience, and if it causes problems I don't think it's worth worrying about too much. It's strictly a Javascript issue, by the way. Yaron Koren 12:44, 30 September 2010 (UTC)Reply[reply]
For my audience, it's a great convenience, but because of this problem, leaving out wikiPreview is what I'm doing now. Is this a known javascript issue? I looked for javascript / mediawiki incompatibilities... if someone who has this working (under Windows) could let me know what version of java they're running, I could have my users install that one. -- 14:14, 30 September 2010 (UTC)Reply[reply]
The Javascript being used is custom Javascript contained within SF, so it's not surprising that it would contain some bugs - see here. Yaron Koren 15:18, 30 September 2010 (UTC)Reply[reply]
Yaron, would it be difficult to open the preview in a new window and keep the current form intact? Most of that question comes from my ignorance regarding how things work under the hood, I'm still coming up to speed on these things. But is it doable? --Skew 20:52, 9 October 2010 (UTC)Reply[reply]
I actually have no idea - I didn't write any of that code. My guess is that it's doable, but it wouldn't make much of a difference. By the way, Java and Javascript are two wholly different languages. Yaron Koren 22:15, 10 October 2010 (UTC)Reply[reply]

including 'free text' content in the results of a semantic query

I'm not sure this is the right place to post this, but ...

Is there a way to include the contents of the semantic form's ‘free text’ section (of a page) in the results produced by a semantic query? I couldn't find anything re: this in the SMW documentation.

Thanks --Ted 20:54, 30 September 2010 (UTC)Reply[reply]

Hi - it's not possible, unfortunately, but you can get around it by making the "free text" field be not actually free text, but rather a field in the template, and then having a property for that field. It's even possible to get this field to be displayed as free text, by putting it outside of the table within the template. Yaron Koren 21:42, 30 September 2010 (UTC)Reply[reply]

No "Edit with Form" tab

I just upgraded to mediawiki 1.16, use Semantic Forms 2.0.1, and the GuMaxdd 1.3 skin. My Edit with form tabs have completed vanished, and I can't for the life of me work out what needs to be done to get them back. If someone could help me, I would be greatful. 19:53, 1 October 2010 (UTC) In case someone might wish to see my full configuration, the website is HERE. Kitsufox 03:30, 2 October 2010 (UTC)Reply[reply]

I would upgrade your version of SMW - it looks like you're using an unstable version, which could be the problem. Yaron Koren 04:35, 3 October 2010 (UTC)Reply[reply]
Stellar. *snicker* I figured I'd be the weak link, not the software. That's almost always the case. Thank you very very much for looking into that. By pulling the stable release (I didn't even realize the release I'd pulled was unstable) and replacing the files it was sorted out so quickly. The only thing I can suggest is a better set of instructions as to what is and isn't stable. I expected the snapshot version to be stable (shows how much I know some days). Kitsufox 14:40, 3 October 2010 (UTC)Reply[reply]
Cool. By "snapshot version" do you mean the REL1_16 version? Those tags are made by MediaWiki people, and not by SMW developers, and I really wish they wouldn't make them at all - they're random snapshots and they just confuse people. Yaron Koren 00:30, 4 October 2010 (UTC)Reply[reply]
I downloaded it from the "Download Snapshot" link on the Mediawiki.org page. To get the right version I ended up going to the SMW site and then that led me to Sourceforge where I was able to get a numbered one and verify that I had a stable version. Kitsufox 12:20, 4 October 2010 (UTC)Reply[reply]

dropdown values populated via inline query

Is there a way to populate a set dropdown values from an inline query?

{{{ field | Foo | values={{#ask:[[Category:Foos]]|?Has foo|format=list}} }}}

In this example, the query itself shows up in the dropdown, not the query results. --Hermhut 20:41, 5 October 2010 (UTC)Reply[reply]

You can't do that directly, but you can create an SMW "concept" with that query, and then use "values from concept". Yaron Koren 12:33, 6 October 2010 (UTC)Reply[reply]
Thanks Yaron, but what I'm specifically trying to do is populate a dropdown in a subpage with values from its parent page. Those values vary from parent page to parent page, meaning I would need a corresponding concept page for every parent page on my wiki. So, unless I can somehow pass BASEPAGENAME into the concept from the subpage, I don't think concepts will work. Can you think of a different solution? Maybe it's possible to use "autocomplete from url", where the URL is an api.php query to the parent page? That seems difficult as well because the $sfgAutocompletionURLs array would also need to have one entry per (parent) page on my wiki. Maybe there's a way I can use Extension:UrlGetParameters and pass BASEPAGENAME into a Concept to achieve the list that I need? Any thoughts? --Hermhut 21:14, 7 October 2010 (UTC)Reply[reply]
Ah, I get it. No, unfortunately I don't believe there's any way to do that, either hackish or not. What about just autocompleting on all the property's values, though? Are the values really that distinct from one page to another? Yaron Koren 03:06, 8 October 2010 (UTC)Reply[reply]

CSS styling of forminput

Hi Yaron

A small suggestion for future versions of SF.

It would be nice to give CSS classes to 'forminput' element for better styling - something like the 'class' parameter from fields. As they are now, forminput forms cannot easily be styled to match the site they are embedded in.

- Laurent Alquier

This has now been added in version 2.0.3 - they have the "formInput" class. Yaron Koren 18:21, 1 November 2010 (UTC)Reply[reply]

remote autocompletion document

Where can I find document with regards to remote autocompletion?


Search for "remote autocompletion" in the documentation. If there's anything you want to know beyond that, you can just ask me. Yaron Koren 12:37, 6 October 2010 (UTC)Reply[reply]
Hi, Yaron. I'd like to know what I need to supply in the form field definition and what I should setup in server corresponding to enable the whole remote autocompletion. Since there is anything in the documentation, I have no clue how it works.
All you need to do is add "|remote autocompletion" in the field tag, within the form definition - SF should (in theory) take care of the rest. Assuming it works, the interface will look the same - the difference will be that the set of autocompletion values won't appear in the HTML source. Yaron Koren 23:31, 13 October 2010 (UTC)Reply[reply]
I get it. remote autocompletion specifies that other "autocompletion from" should be done remotely. I thought remote autocompletion can perform a custom ajax call. Since you already have the remote autocompletion in place. You can easily support this by adding one autocompletion from function=function name. The function name is one function written by other developer. By this way, the end user can have values from many sources.
Well, see the "autocomplete from url" parameter - that sort of matches what you're talking about. Yaron Koren 12:51, 14 October 2010 (UTC)Reply[reply]

"Add another" - Help or Feature Request ?

Hi, we have some Stupid users that doesn't really understand these fancy "Add another"-Buttons. Is it possible to have One of these "Add another" Fields always open. So that the user can see all the Fields with out pressing the "Add another" Button. SBachenberg 07:54, 6 October 2010 (UTC)Reply[reply]

You can preload the form so that, when it creates a new page, it'll always have one instance of that template... I wouldn't say that's a good idea, though. Maybe some more help text in the form would help solve the problem. And don't forget the "label=" parameter, if you're not using it. Yaron Koren 12:35, 6 October 2010 (UTC)Reply[reply]

Customize Semantic forms's output

A p tag is added after every table rendered by a Semantic Form's form. Is there a way to stop semantic form from adding that paragraph after every rendered table? Thanks in advance, (also because Semantic Forms is awesome).

:) Just to clarify, are you talking about the forms themselves, or about pages created by the forms? Yaron Koren 01:47, 8 October 2010 (UTC)Reply[reply]
I'm talking about pages created by the forms. Cbesozzi 11:11, 9 October 2010 (UTC)Reply[reply]
In that case, this probably isn't a Semantic Forms issue per se. Assuming that the source wiki-text of the relevant pages looks alright, the problem is probably that the templates themselves are adding some stray newlines. Yaron Koren 15:37, 11 October 2010 (UTC)Reply[reply]

Checkbox - default checked

Is there a way to defualt a checkbox as checked? --Dgennaro 17:50, 8 October 2010 (UTC)Reply[reply]

Yeah - add "|default=yes". Yaron Koren 18:05, 8 October 2010 (UTC)Reply[reply]
Thanks Yaron. You rock! --Dgennaro 13:40, 12 October 2010 (UTC)Reply[reply]

URLs entered into forms

I'm looking for a solution for long URLs that break the style of infoboxes in certain browsers. Is there documentation about how to handle this with SF, such displaying a link name rather than URL? Thanks--Aj2479 22:47, 10 October 2010 (UTC)Reply[reply]

Sure, a link name would work; so would this (used with the Widgets extension). Yaron Koren 01:36, 11 October 2010 (UTC)Reply[reply]

Nested forms

Is there a way to nest forms inside forms ?

For example, for a Town template that goes like that:

|town_name=new york
|town_population= 1254
|town_description= desc
|town_mayors= {{mayor|name=bob|year=1956}} {{mayor|name=ted|year=1976}}
|town_history=history facts
|town_politics=politics facts
|town_events={{event|name=halloween|attendance=4546454}} {{event|name=new year|attendance=90054}}

town_mayors and town_events are fields that would be populated by multiple templates instances. Right now, it doesn't seem there is a way to declare a global form for "Town" and have multiple form instances for town_mayors or town_events in the middle of the form when editing.

The only current ways to handle that:

1. just declare these fields as text, and put the template text

 "{{mayor|name=bob|year=1956}} {{mayor|name=ted|year=1976}}" 

inside it. Works of course, but the point is to try to use forms as much as possible.

2. split the Town template in multiple parts and build your form accordingly. The form would be

<for template=Town_header>..</end template>
<for template=Town_mayors|multiple>..</end template>
<for template=Town_first_part>..</end template> //history+politics
<for template=Town_events|multiple>..</end template>
<for template=Town_footer>..</end template>

and would generate something like that

{{Town header|town_name=new york|town_population= 1254|town_description= desc}}
{{Town mayor|name=bob|year=1956}}
{{Town mayor|name=ted|year=1976}}
{{Town_first_part|town_history=history facts|town_politics=politics facts}}
{{Town town_event|name=halloween|attendance=4546454}}
{{Town town_event|name=new year|attendance=90054}}
{{Town footer|town_location=coordinates}}

Not a great solution, since if you want to just change the orders of the sections on a Town page, it would become a pain to deal with all the split templates, while it is really easy with only one template.

3. Somehow store the multiple instance templates in semantic data objects and have a query in the town template that calls these objects. Issues: On the form page, the multiple templates would have to be either before or after the general Town form, ergonomically that's not a good end user experience, the form should give them a structure similar to what they get on the actual pages. Also, using a request to query objects that are already on the same page seems like a waste of server resources.

4. Well the right way from my point of view would be to have something like

 <for template=Town>
**input declarations**
<for template=mayor|multiple>**own inputs</end template>
**more input declarations
<for template=event|multiple>**own inputs</end template>
</end template>

The nested multi instance templates would be included in the general form and adding new instances would add that inside too. On submission, the concatenated code from these templates would be put ine the appropriate field.

5. Is there an another option ? A solution that would solve that ?

Hi - no, there's no way to do nested forms. What you list as option 2 is the only real approach. Yaron Koren 12:25, 12 October 2010 (UTC)Reply[reply]

Combobox with Values from Values

Hi Yaron, is it possible to create a Combobox with all values from the "Values=" Attribute instead of autocompletion Values ? SBachenberg 09:25, 12 October 2010 (UTC)Reply[reply]

Unfortunately, no. I'm planning to make some changes in the next version of SF that will allow for that sort of thing, though. Yaron Koren 12:27, 12 October 2010 (UTC)Reply[reply]

Templates in fields cause strange parsing

When I insert into a form field {{some template}} it renders wrong and crashes the input to �{some template}� whereat � is HTML-escaped &iuml;&iquest;&frac12;. I figured out that this is caused by the {}-characters. Is there any work around or setting I missed? The parameter $smwgLinksInValues = true; does not have a positive effect on this. I work with SF 2.0 on a German Wiki. Thanks for any Help. See also http://scratchpad.referata.com/wiki/Encoding_problems_with_partial_forms --Andreas Plank 09:47, 12 October 2010 (UTC)Reply[reply]

Some more details: this phenomena appears only when the form is set to a partial form with {{{info|partial form|...}}}. All in all it looks like an encoding problem. I hope not that it is caused by copied SF-files. --Andreas Plank 12:00, 12 October 2010 (UTC)Reply[reply]

Multiple instance templates - button label

Is there a way to alter the "Add another" text on the button when using multiple instance templates? Thanks in advance. --Dgennaro 16:28, 13 October 2010 (UTC)Reply[reply]

You can change it across the wiki by changing the text in the page MediaWiki:sf_formedit_addanother ; but you can't set it per template, unfortunately. Yaron Koren 19:32, 13 October 2010 (UTC)Reply[reply]
Thanks for the help. --Dgennaro 19:37, 14 October 2010 (UTC)Reply[reply]

More examples in documentation would be great

While I really appreciate the extensive documentation of Semantic Forms, I often run into problems when trying to solve some special cases. E.g. for Extension:Semantic_Forms#Adding_data or Extension:Semantic_Forms#Preloading_data, some definition such as Specify a "preload" page for the "free text" input, which will preload the free text field with the contents of that page. are not clear enough to just make them work.

It would be great to have either

--Hhappel 09:45, 14 October 2010 (UTC)Reply[reply]


Hey there. Currently i'm setting up a wiki using XAMPP on my local machine. Everything in the Wiki works fine thus far, including Semantic Forms. The problem however is:

  • i intend to use the wiki in an offline mode for intranet-only documentation purposes. This brings up a problem:
  • creating pages with forms makes my wiki access to "yui.yahooapis.com" - is this a definitive requirement for the forms-extension to work?

Is there any solution to this, as in copying the needed apis to someplace else? Greetings, Mike

Hi - as of version 2.0, Semantic Forms no longer uses YUI; it uses jQuery. Assuming you're using an old version, you should upgrade. Yaron Koren 15:43, 15 October 2010 (UTC)Reply[reply]
Thanks a lot, that solved the problem! I really have to get SVN working at my company because missing important updates like this one sucks greatly. ;-)

Using FormInput to Add Instance of Multiple Instanced Template

Hi, I have a form that uses a multiple-instanced template to make a list of items, and I would like to use a forminput button from another page that will let the user add that item to one of the existing lists. It doesn't seem to work, either because it won't preload an existing template input, or because it doesn't recognize that an additional input should be added unless the "Add Another" button is physically clicked from within the form. Is there a workaround for this? Thanks! --Klh5u 19:27, 18 October 2010 (UTC)Reply[reply]

I don't think so... maybe it's worth turning each of those instances into a separate page? Yaron Koren 21:44, 18 October 2010 (UTC)Reply[reply]
Thanks for the idea, but that wouldn't work in my case. We want to let users make recommended reading lists out of things in a "book" category. What I did instead was make a semantic result format that displayed each possible list along with a button that had an onclick event that would redirect to a new special page and pass the current page and the chosen list as parameters. I then used the special page to edit and redirect to the chosen list. A bit more complicated than I was hoping, but it gets the job done! Thanks again for your help, I really appreciate the quick response whenever I have asked a question here! --Klh5u 22:17, 18 October 2010 (UTC)Reply[reply]

Using multiple multiple instance templates with HeaderTabs

I have a form with a number of tabs. I can get multiple instance templates working in the last tab (by placing the headertabs tag in the article itself, not the template). I'm wondering if it is possible to put multiple instance templates in other tabs, and hence have multiple multiple instance templates, each on a different tab? - Borofkin 03:33, 20 October 2010 (UTC)Reply[reply]

Definitely. You shouldn't put any of the Header Tabs stuff directly in the article - instead, you should create small "header" and "footer" templates, with no arguments, that are responsible for just those little snippets of wiki-text, and add those to the form. Yaron Koren 12:31, 20 October 2010 (UTC)Reply[reply]
At the moment the contents of most tabs are in one template. Should I split each tab into a template of its own? Is there a publically available example of a setup like this? - Borofkin 22:16, 20 October 2010 (UTC)Reply[reply]
Should I be using partial forms? - Borofkin 22:45, 20 October 2010 (UTC)Reply[reply]
You don't need to split each tab into its own template - only where it's necessary, due to multiple-instance templates. I can't think of a public example. Yaron Koren

any idea on uploading picture through form?

When I tried to upload a picture through a form. Everything is fine and the image was uploaded. However, the picture isn't showing up on the wiki page it created. All the parameters are correct and everything seems to be running fine. I see that the picture I uploaded is on the server but somehow its not showing up on the wiki. Any tips on this problem?

Does the name of the image show up in the template call, in the page's source text? If so, the problem is just that the template isn't displaying the image correctly. Yaron Koren 06:31, 24 October 2010 (UTC)Reply[reply]
I went to the source to check, its not there. All the texts in the form show up when entered, but when it comes to the picture it doesnt.
Alright. Did you get your copy of SF from SVN recently? If so, you might be seeing a bug that was in there recently; I'd recommend updating your code and trying it again. If not, what versions of SF and MW are you using? Yaron Koren 19:02, 24 October 2010 (UTC)Reply[reply]
Yeah I have the latest version and everything. The image still doesnt show up.
Well, let me offer my usual suggestion, which is to try to reproduce the problem on a public wiki like scratchpad.referata.com, and link to it from here. Yaron Koren 05:43, 27 October 2010 (UTC)Reply[reply]
Alright here we go [about:blank Link] I reproduced it on a test server. I managed to get the image file name to show up on the wiki. But however its not triggering the wiki to show the picture.

If the image name does show up in the wiki-text, then it's a totally different problem. But I fixed that one on your wiki. Yaron Koren 02:19, 1 November 2010 (UTC)Reply[reply]

Thanks Yaron, can I ask what did you fix?
See the "Recent changes" page. Yaron Koren 19:45, 1 November 2010 (UTC)Reply[reply]

Woohoo! Thanks again Yaron. I saw what you did.Anton

Case Insensitive Search in Special:RunQuery Forms

Hi Yaron, is tried your Special:RunQuery Examples and i love the functionality, its great! But is there a way to make the Search not Casesensitive ? SBachenberg 09:43, 26 October 2010 (UTC)Reply[reply]

It's great to hear that you like RunQuery. This isn't really a Semantic Forms question, though - it's a Semantic MediaWiki question, since that's what's handling the actual query. I think the answer is "no", though - based on limitations in MySQL. I'm not 100% sure. Yaron Koren
I know. I found a old mail from you to the SMW Mailing list asking for the Functionality and thought you got an answer how to do it :-) Do you know where i have to look in the SMW Code for making a hack ? SBachenberg 07:11, 27 October 2010 (UTC)Reply[reply]
Hi Yaron, I found an interesting article about case sensitivity in the MySQL Manual Its seams that the Character Set of the Database Causes Case Sensitivity or Not. SBachenberg 06:49, 28 October 2010 (UTC)Reply[reply]
Ah - that would definitely explain some of the behavior I've seen. That's good to know. (Though, again, it's not related to SF. :) ) Yaron Koren 02:20, 1 November 2010 (UTC)Reply[reply]

Conditional Templates

Is there some easy way to use certain "sub-templated" elements in the form's output template? My following Use Cases apply:

    1. User Edits his user page (form:user), adds one or multiple "Projects" he's been involved in. The output on the userpage should display a list of "colored" badge-templates, with each showing the current project data and knowledge state for that user. Each template should have an own color (or design) based on his property "ProjectExperience" provided with the form. Think of it as kind of a "medal" system (or tables with different shading) that greatly increases readability with huge amounts of data involved.
    2. People "edit with form" any article and can set a "ReviewState" Property for the content displayed. According to the review state a small templated hintbox is shown on top of the content: Draft, Ready for Review, Released (No TemplateBox added in this case). I know there's a separate Review-Extension for this but i rather like my Wiki to use as few Extensions as possible. Also, there are very few users involved with no real need for "Reviewer-Roles" or more than 3 Page-States.
    3. Other ways to use this could be thought of, i.e. making it clearly visible if a page is based on PageContentProperty "Concept, Tutorial, Manual" - each using a different template when you change one small setting.

Based on my current knowledge this can't be done with basic SMW or SF Syntax, can it? The only possible solution i found thus far would be the small "Conditionals" section in the SMW manual which involves a separate (and rather complex-looking) Extension. (Mike)

All of these can be done, and yes, you need the #if call in ParserFunctions to do it. ParserFunctions isn't that complex, and I'd say it's indispensable. Yaron Koren 16:18, 26 October 2010 (UTC)Reply[reply]
Sorry to ask again, but 3h of fruitless googling and checking mailing lists and no anwer on the ParserFunction Site brought me back here. Haven't found any examples involving both semantic properties and ParserFunction calls. After reading through the different PF-calls i'm unsure if i can use #if or do a #switch. Something like:
{{#switch:PageStatus::{{{PageStatus}}} //Switch depending on Page-Status set in the Form:
| Draft = {{{DraftBox}}}
| Review = {{{ReviewBox}}} 
| Release = // show nothing
  • How do i properly check the mere existance of a semantic property value (if it is provided on the current page)?
  • How can i simply display the current semantic value stored on the current page (assuming that there's only one value per property per page stored)? I assume it's an inline query using #ask but i haven't seen any examples of just displaying just a property value within the normal wiki text. The "Browse Properties" page didn't give me any good hints.

Siedenote: Sorry to ask stuff this frequently. I'm not a programmer but a Technical Writer + i'm relatively new to MediaWiki. If i can somehow return the favor and help by improving any manuals or designs in general, please let me know. --Fennyface 08:52, 28 October 2010 (UTC) (mike)Reply[reply]

I'm not aware of a #switch function, so as far as I know you have to use #if. And I know there are many examples of #if being used within SMW-using templates; though I can't think of any specifically. Yaron Koren

Uploading files using FancyBox to the category. Is it real?

I used the extension called "CategoryOnUpload" to add a combobox for choosing the category of the uploadable file. It works fine. But how can I do the same on the FancyBox upload form? Or how can I put the uploaded through it image into the default category? --Tarasius.ua 14:42, 27 October 2010 (UTC)Reply[reply]

I don't think there's any way to do that currently in SF. Yaron Koren 14:55, 27 October 2010 (UTC)Reply[reply]
Maybe there is another way to upload image, without using FancyBox? For example, default upload page. Or somehow check if there is no one category in file, and add one.--Tarasius.ua 15:26, 27 October 2010 (UTC)Reply[reply]
The issue isn't FancyBox - it's that Semantic Forms itself doesn't support this feature. You can, of course, upload files in any way. Yaron Koren 16:09, 27 October 2010 (UTC)Reply[reply]
What should I change in the FancyBox upload form code to show the default text in the field "Description"? I can write there my category.

--Tarasius.ua 13:03, 29 October 2010 (UTC)Reply[reply]

I don't quite understand the question, but again I should note that this is just not possible currently in SF. If you're asking about how to modify the PHP code to get it working, I don't know. Yaron Koren 02:16, 1 November 2010 (UTC)Reply[reply]

Image display problems and textbox problems

When I upload an image it is displayed as just the filename and not the image itself, what code do I need to put in to change that? also what code do I put in to make it display at a set size?

Secound when selecting text box, some of them are showing up as text areas regardless?


Thanks in advance Redeye 02:15, 28 October 2010 (UTC)Reply[reply]

You need to have something like "[[File:{{Image name}}]]" in the template - look it up in the MediaWiki documentation for the specific display parameters. I didn't understand the last question - can you point to an example? Yaron Koren 07:07, 29 October 2010 (UTC)Reply[reply]

I use this code for infoboxes that dont use the forms [[Image:{{{image|placeholder.png}}}|{{{imagesize|220}}}px]] but when I try to make that work in the forms with this code [[{{{field|Image|uploadable|autocomplete on namespace=Image}}}|{{{imagesize|220}}}px]] what am i doing wrong?

As for the secoud issue if you go to the following link http://www.ukairsoftwiki.co.uk/wiki/mediawiki-1.16.0/index.php?title=Form:Airsoft_Team and create a mock team you will see that there are lots of text areas, the only fields that should be text boxes should be "battles" and "Free Text" -- Redeye 08:38, 29 October 2010 (UTC)Reply[reply]

Ok Ive fixed the Image display problem and the box problems I can live with. Thanks for you help Redeye 03:46, 30 October 2010 (UTC)Reply[reply]

Hey Redeye how did you fix it?
Redeye - textareas show up by default for any property of type "Text". If you want them to be one-row text inputs, you could just change the properties to be of type "String". Yaron Koren 02:25, 1 November 2010 (UTC)Reply[reply]

To get the image upload and display to work I used the following code in the form:

! Image:
| {{{field|image|uploadable|autocomplete on namespace=image}}}
! Image Size:
| {{{field|imagesize}}} for example (100px)

And the following code in the Template:

! style="text-align: center;" colspan="2" |[[Image:{{{image|Wiki.png}}}|{{{imagesize|135}}}px]]

As for the text box not appearing where I wanted it, I forgot to put |- to create a new line lol Redeye 23:47, 3 November 2010 (UTC)Reply[reply]

Return to "Page Forms/Archive September to October 2010" page.