Extension talk:Page Forms

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)


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

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)
 * I've verified this on Scratchpad. Minor edits are not being flagged.  Thorncrag 18:32, 8 September 2010 (UTC)
 * I've verified this on an additional wiki with SF installed. Thorncrag 00:36, 9 September 2010 (UTC)

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)


 * 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)

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)

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)

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)


 * 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)


 * 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)


 * Thank you. That fixed it! --BrettFerguson 04:08, 12 September 2010 (UTC)
 * 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)

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)


 * 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)

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)


 * 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)


 * 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)


 * 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)

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:



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,



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  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,



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)


 * 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)
 * 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)

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)


 * 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)


 * 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)


 * 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)


 * 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)

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:

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:

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

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)

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?

Sincerely

Nico --80.153.59.17 12:17, 14 September 2010 (UTC)

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: --RScheiber 21:07, 14 September 2010 (UTC)


 * 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)

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)


 * 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)


 * Thank you for your fast reply! I will look into Semantic Internal Objects. -- Meera 15 September 2010 (UTC)