From: Pierre R. <pi...@br...> - 2011-11-21 15:45:15
|
Hi Kelly, Stephan Gambke fixed it in the svn version available in http://svn.wikimedia.org/svnroot/mediawiki/tags/extensions/SemanticForms/REL_2_3/. It will probably go in a 2.3.1 soon. Cheers, Pierre On 21/11/2011 16:14, Kelly Bowles wrote: > Same Issue here Bernhard. I've thought it was because of WikiEditor but after removing that, it still appears to not load free text into the form. Unfortunately my wiki is behind a firewall and I cannot provide a link. > > Category is defined as using a particular form. > Form is accessed through Edit With Form tab. > > MW 1.17.0 > PHP 5.3.6 > MySQL 5.1.56 > SMW 1.6.1 > SF 2.3 > > -----Original Message----- > From: Krabina Bernhard [mailto:kr...@kd...] > Sent: 18 November 2011 22:40 > To: Yaron Koren > Cc: Semantic MediaWiki users > Subject: Re: [Semediawiki-user] [SF] Version 2.3: Nested template calls, WikiEditor for textareas, image preview, etc. > > Hi Yaron, > > there seems to be a major bug with the latest version: in 2 of my wiki where I installed it, the free text does not get loaded into the form! > > regards, > Bernhard > > ----- Ursprüngliche Mail ----- >> Hi everyone, >> >> Version 2.3 of Semantic Forms has been released. This is a major >> version, with a lot of cool new features, most of them contributed by >> people other than me - which is very good news for the software, and >> also most likely means better code. :) Changes and additions in this >> version include: >> >> - You can now nest calls to a multiple-instance template within a call >> to another template. This is something that people have asked about >> for a while. It helps to solve two problems: the awkwardness of >> putting headers above multiple-instance templates, and excess newlines >> when displaying multiple-instance templates. >> >> As an example, let's say that you have a "Person" page type, that >> holds information about people - including places they've lived and >> companies they've worked at. Until now, the page source had to look >> something >> like: >> >> {{Person >> ... >> }} >> {{Place lived >> ... >> }} >> {{Place lived >> ... >> }} >> {{Company worked at >> ... >> }} >> {{Company worked at >> ... >> }} >> >> But what if you wanted a header that said "Companies" above the list >> of companies? Then you would have to create a template called >> "Companies header" or something, that just contained the header, and >> have the form stick it there in the middle. But now you can instead >> have the form save to a page that looks like: >> >> {{Person >> ... >> |Places lived={{Place lived|...}}{{Place lived|...}}{{Place >> |lived|...}} >> |Companies worked at={{Company worked at|...}}{{Company worked >> |at|...}} >> ... >> }} >> >> The "Person" template can seamlessly take care of the entire display >> - and >> the lack of newlines between instance of the template should make it >> easier to avoid having too much whitespace in the output. >> >> You can accomplish this using the new "embed in field" and "holds >> template" >> parameters for the form definition - in this case, you would add >> "embed in field=Person[Places lived]" to the "for template" tag for >> "Place lived", and add "holds template" to the "Places lived" field >> tag; and do basically the same thing for the company template and >> field. >> >> Thanks to LY Meng for the patch that enabled this cool new feature. >> >> - You can now add the WikiEditor toolbar to any textarea in the form, >> if you have the WikiEditor extension installed ( >> http://www.mediawiki.org/wiki/Extension:WikiEditor). To add it, just >> add the parameter "|editor=wikieditor" to the "field" tag. (And, >> again, make sure you have WikiEditor installed). Thanks to Stephan >> Gambke for this new feature. >> >> - An "image preview" feature was added, so that users can see images >> that were uploaded, within the form itself. To add it, just add >> "|imagepreview" >> to the "field" tag. Thanks to Jeroen De Dauw for this feature. >> >> - A "placeholder=" parameter was added to the text and textarea form >> inputs. Using this parameter, you can set a help value that shows up >> until the user starts typing in the input. It uses the "placeholder" >> HTML attribute, which was added in HTML5 - which turns out to be >> adopted in current browsers quite a bit more than I thought it was. So >> hopefully this is just the beginning of Semantic Forms making use of >> new HTML5 features. >> Thanks to LY Meng for the patch to add this functionality. >> >> - The "remote autocompletion" parameter was added to the #forminput >> parser function. This works the same way as "remote autocompletion" >> within forms - if it's added, the autocomplete values are queried via >> an Ajax call, which means that you can autocomplete on a lot more >> values. >> >> - When autocompleting on multiple values within a form field, values >> after the first one get bolded, when the user is typing - this wasn't >> happening before, due to a bug. >> >> - Handling was fixed for templates whose name contains an apostrophe >> - this >> was apparently not working for a while. >> >> - The "autogrow" parameter for textarea inputs was fixed - before, it >> wasn't working unless the number of columns was set in the form >> definition. >> Now, if "autogrow" is set, the default width of the textarea is set to >> 90 columns, which lets the Javascript work correctly. >> >> - Fields that contain a list of values of type Number, URL or Email >> (as opposed to just one value) no longer get their contents >> "validated" >> when >> the form is submitted - that was causing problems. >> >> - The global variable $sfgCacheFormDefinitions, which lets you cache >> form definitions so that they don't have to be re-parsed every time, >> was introduced a while ago (version 1.8.8), but it had a bunch of >> bugs, and at some point it was disabled. It now fully works and has >> been re-enabled, thanks to an overhaul of the caching system by >> Stephan Gambke. >> >> - Within Special:RunQuery, you can now set a form to be displayed >> above the search results, instead of below it - to do that, you can >> use the new "query form at top" parameter for the {{{info}}} tag, >> within a specific form. >> >> - The display of warning and error messages was changed somewhat, to >> be more in line with MediaWiki's style guidelines. Thanks in part to >> DaSch for this improvement. >> >> - #formlink has a new optional parameter: "tooltip=", which sets text >> that you see if you hover over the link. Thanks in part to Van de >> Bugger for this feature. >> >> - #autoedit and the optional "Save and continue" button for forms now >> set an edit summary when they save a page, for display on the history >> page. >> This feature was added by Stephan Gambke. >> >> - Much greater support was added for the Page Schemas extension ( >> http://www.mediawiki.org/wiki/Extension:Page_Schemas). At some point >> soon, Page Schemas is planned to become a recommended part of the >> Semantic Forms setup. >> >> - There were various other bug fixes, to both the PHP and Javascript >> code, done by Jeroen, Stephan, myself and others, notably including, >> but not limited to, ialex, reedy and nikerabbit. >> >> To read more about Semantic Forms, and download the new version, go >> here: >> http://www.mediawiki.org/wiki/Extension:Semantic_Forms >> >> -Yaron >> ---------------------------------------------------------------------- >> -------- All the data continuously generated in your IT infrastructure >> contains a definitive record of customers, application performance, >> security threats, fraudulent activity, and more. Splunk takes this >> data and makes sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-novd2d >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user |