Semantic MediaWiki

\o/  It's finally out! And with a bunch of cool new features, too.


> - You can now add the WikiEditor toolbar to any textarea in the form, if

Two remarks on the WikiEditor: You have to use a fairly recent version.
If in doubt, take the latest available from SVN. And thanks for that
really go to Bernhard Krabina and the KDZ who sponsored it.

Cheers,
Stephan

Guys, you simply rocks. Thanks a lot for your work.

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

Is it working for "free text" input too?

--
Pierre Réveillon

Hi Pierre.

>> - You can now add the WikiEditor toolbar to any textarea in the form, if
> Is it working for "free text" input too?

Yes, it works for the free text, too.

Cheers,
Stephan

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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>

Hi,

Thanks, everyone - I hope you like it!

Bernhard - that sounds bad indeed. Is there a URL where this can be seen?

-Yaron

On Fri, Nov 18, 2011 at 5:39 PM, Krabina Bernhard <krabina@...> wrote:

> 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
> > Semediawiki-user@...
> > 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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>



-- 
WikiWorks · MediaWiki Consulting · http://wikiworks.com

Unfortunately not, I removed the latest version again, because they are live wikis. Does it work for you? Maybe it is an inconsistency with the wikieditor feature in version 2.3?

regards,
Bernhard
-- 
Mag. Bernhard Krabina
KDZ - Zentrum für Verwaltungsforschung
Centre for Public Administration Research
Guglgasse 13, 1110 Wien
Telefon: +43  1 8923492-27, Fax: +43 1 8923492-20
Mobil:   +43 676 849579-27 
mailto:krabina@... - http://www.kdz.or.at

- Plattform Verwaltungskooperation:
  http://www.verwaltungskooperation.at 


KDZ News: Schaffung von Public Value: Aktuelle Studie des KDZ veröffentlicht http://www.kdz.eu/de/schaffung-von-public-value-aktuelle-studie-des-kdz-ver%C3%B6ffentlicht
----- Ursprüngliche Mail -----
> Hi,
> 
> 
> Thanks, everyone - I hope you like it!
> 
> 
> Bernhard - that sounds bad indeed. Is there a URL where this can be
> seen?
> 
> 
> 
> -Yaron
> 
> 
> On Fri, Nov 18, 2011 at 5:39 PM, Krabina Bernhard < krabina@...
> > wrote:
> 
> 
> 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
> > Semediawiki-user@...
> > 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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
> 
> 
> 
> 
> --
> WikiWorks · MediaWiki Consulting · http://wikiworks.com
>

I have a problem using WikiEditor in SF (not only for free text).
It does not work, and I have the javascript error "ext is not defined".
The page source code shows:

<script>			jQuery( jQuery('#input_17').SemanticForms_registerInputInit( ext.wikieditor.init, null ) );</script>
<script>			jQuery( jQuery('#free_text').SemanticForms_registerInputInit( ext.wikieditor.init, null ) );</script>

See http://www.delibris.fr/Sp%C3%A9cial:AjouterDonn%C3%A9es/Auteur/Aaa, 
the "Test" and "Free text" inputs should have wikieditor.

Am I doing something wrong?

Cheers,

--
Pierre

On 18/11/2011 22:34, Stephan Gambke wrote:
> Hi Pierre.
>
>>> - You can now add the WikiEditor toolbar to any textarea in the form, if
>> Is it working for "free text" input too?
> Yes, it works for the free text, too.
>
> Cheers,
> Stephan

> - You can now nest calls to a multiple-instance template within a call
> to another template.

Great news! Any example how to use it?

Thanks,
Van.

On Fri, 2011-11-18 at 13:17 -0500, Yaron Koren wrote:
> 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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user

Hi everyone,

There were two issues with SF version 2.3 that have now been fixed:

- The downloadable files had some errors: they were missing the new CSS
file for WikiEditor handling, and they didn't have the latest version of a
few other files. The .tar.gz and .zip files have now been updated. If you
already downloaded SF 2.3 via one of the files before, please download it
again - sorry about that.

- There was a somewhat minor bug where, if a page-name formula consisted of
only "<unique number>", the form didn't create the page - this is now
fixed, in both SVN and the downloadable files.

So SF 2.3 is now re-released. :) If it turns out that there are any
additional problems - if, for instance, the JS issue with WikiEditor that
Pierre wrote about turns out to be an actual bug - the fixes will probably
go into a new version of SF.

Van - to answer your question, see the original email. :)

-Yaron

My JS issue was cause by missing CSS file, it seems to be fixed in this 
new 2.3 package. Thanks!

However, I'm stuck on the same (big) problem Bernhard reported : The 
free text content is not loaded into the form. I downgraded to 2.2.1 
because the users are working on it. It happens on the 2.3 package, and 
also on the svn trunk. No javascript error, no php error...
It's the same if I set editor=wikieditor or not (but if I put 
editor=wikieditor, the textbox has no border, but the wikieditor is not 
here).

I can put the 2.3 back temporary if you want me to test/check things.

Cheers,

--
Pierre

On 20/11/2011 03:49, Yaron Koren wrote:
> Hi everyone,
>
> There were two issues with SF version 2.3 that have now been fixed:
>
> - The downloadable files had some errors: they were missing the new CSS
> file for WikiEditor handling, and they didn't have the latest version of a
> few other files. The .tar.gz and .zip files have now been updated. If you
> already downloaded SF 2.3 via one of the files before, please download it
> again - sorry about that.
>
> - There was a somewhat minor bug where, if a page-name formula consisted of
> only "<unique number>", the form didn't create the page - this is now
> fixed, in both SVN and the downloadable files.
>
> So SF 2.3 is now re-released. :) If it turns out that there are any
> additional problems - if, for instance, the JS issue with WikiEditor that
> Pierre wrote about turns out to be an actual bug - the fixes will probably
> go into a new version of SF.
>
> Van - to answer your question, see the original email. :)
>
> -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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user

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:krabina@...] 
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
> Semediawiki-user@...
> 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
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

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:krabina@...]
> 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
>> Semediawiki-user@...
>> 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
> Semediawiki-user@...
> 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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user

I am sorry, it is not fixed in 2.3. I do not currently have SVN
access, so can not check it in. It is also too large to be sent to the
list as an attachment. Please give Yaron some time to provide fixed
packages.

Cheers,
Stephan

2011/11/21 Pierre Réveillon <pierre@...>:
> 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:krabina@...]
>> 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
>>> Semediawiki-user@...
>>> 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
>> Semediawiki-user@...
>> 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
>> Semediawiki-user@...
>> 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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>

Ok, so it was a total misunderstanding :D
I *only* installed the REL_2_3 tag from the svn and it *did* fix the 
problem. I didn't see (and so not installed) your attached file!

I'm a bit lost, but hey, it works.

On 21/11/2011 17:20, Stephan Gambke wrote:
> I am sorry, it is not fixed in 2.3. I do not currently have SVN
> access, so can not check it in. It is also too large to be sent to the
> list as an attachment. Please give Yaron some time to provide fixed
> packages.
>
> Cheers,
> Stephan
>
> 2011/11/21 Pierre Réveillon<pierre@...>:
>> 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:krabina@...]
>>> 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
>>>> Semediawiki-user@...
>>>> 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
>>> Semediawiki-user@...
>>> 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
>>> Semediawiki-user@...
>>> 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
>> Semediawiki-user@...
>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>>

Hello Van,

It's not an official example at all, but I'm actually testing it on my 
website.
You can see it "working" here:
The form source code: 
http://www.delibris.fr/wiki/index.php?title=Formulaire:Livre&action=edit
The form in action: 
http://www.delibris.fr/wiki/index.php?title=AaaTest&action=formedit
The generated code: 
http://www.delibris.fr/wiki/index.php?title=AaaTest&action=edit
The "subtemplate": 
http://www.delibris.fr/wiki/index.php?title=Mod%C3%A8le:%C3%89dition&action=edit

It's just a raw test, for now I don't use/show the values. I'll put the 
different sets of values in an infobox, but I'm not sure what would be 
the cleaner way: make the "Édition" template to show an infobox, or in 
the "Page_Livre" template, make a #ask to get Éditions sets, and call 
the infobox here...

Regards,

--
Pierre

On 19/11/2011 19:18, Van de Bugger wrote:
>> - You can now nest calls to a multiple-instance template within a call
>> to another template.
> Great news! Any example how to use it?
>
> Thanks,
> Van.
>
> On Fri, 2011-11-18 at 13:17 -0500, Yaron Koren wrote:
>> 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
>> Semediawiki-user@...
>> 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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user

Hi.

The wikieditor does not appear for me. Firebug shows the following error 
when I edit with form:
jQuery is not defined
error source line: <script> jQuery( 
jQuery('#input_31')...t.wikieditor.init, null ) );</script>

I'm running SF 2.3 from the svn branch below, MW 1.17, SMW 1.6 and 
WikiEditor 0.3.1 /r103819 (the latest trunk)
/
Any ideas?/
/

Thanks
Neill.

On 21/11/11 16:20, Stephan Gambke wrote:
> I am sorry, it is not fixed in 2.3. I do not currently have SVN
> access, so can not check it in. It is also too large to be sent to the
> list as an attachment. Please give Yaron some time to provide fixed
> packages.
>
> Cheers,
> Stephan
>
> 2011/11/21 Pierre Réveillon<pierre@...>:
>> 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:krabina@...]
>>> 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
>>>> Semediawiki-user@...
>>>> 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
>>> Semediawiki-user@...
>>> 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
>>> Semediawiki-user@...
>>> 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
>> Semediawiki-user@...
>> 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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>

Hmm, if everything is at the latest version it should definitely work.
Could it be an issue with the skin?
On Nov 21, 2011 5:51 PM, "Neill Mitchell" <neill@...> wrote:

> Hi.
>
> The wikieditor does not appear for me. Firebug shows the following error
> when I edit with form:
> jQuery is not defined
> error source line: <script> jQuery(
> jQuery('#input_31')...t.wikieditor.init, null ) );</script>
>
> I'm running SF 2.3 from the svn branch below, MW 1.17, SMW 1.6 and
> WikiEditor 0.3.1 /r103819 (the latest trunk)
> /
> Any ideas?/
> /
>
> Thanks
> Neill.
>
> On 21/11/11 16:20, Stephan Gambke wrote:
> > I am sorry, it is not fixed in 2.3. I do not currently have SVN
> > access, so can not check it in. It is also too large to be sent to the
> > list as an attachment. Please give Yaron some time to provide fixed
> > packages.
> >
> > Cheers,
> > Stephan
> >
> > 2011/11/21 Pierre Réveillon<pierre@...>:
> >> 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:krabina@...]
> >>> 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
> >>>> Semediawiki-user@...
> >>>> 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
> >>> Semediawiki-user@...
> >>> 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
> >>> Semediawiki-user@...
> >>> 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
> >> Semediawiki-user@...
> >> 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
> > Semediawiki-user@...
> > 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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>

Hi.

It was indeed a skin issue. The old SMW+ ontoskin issue once again. This 
was the final straw for it ;) I've rebuilt my skin based on Vector and 
now the editor works. Had the first "oh wow!" from a user less than 10 
minutes later :) This really sorts out one of the top asks :)

Thanks Stefan.

Cheers
Neill.
On 21/11/11 19:13, Stephan Gambke wrote:
>
> Hmm, if everything is at the latest version it should definitely work. 
> Could it be an issue with the skin?
>
> On Nov 21, 2011 5:51 PM, "Neill Mitchell" <neill@... 
> <mailto:neill@...>> wrote:
>
>     Hi.
>
>     The wikieditor does not appear for me. Firebug shows the following
>     error
>     when I edit with form:
>     jQuery is not defined
>     error source line: <script> jQuery(
>     jQuery('#input_31')...t.wikieditor.init, null ) );</script>
>
>     I'm running SF 2.3 from the svn branch below, MW 1.17, SMW 1.6 and
>     WikiEditor 0.3.1 /r103819 (the latest trunk)
>     /
>     Any ideas?/
>     /
>
>     Thanks
>     Neill.
>
>     On 21/11/11 16:20, Stephan Gambke wrote:
>     > I am sorry, it is not fixed in 2.3. I do not currently have SVN
>     > access, so can not check it in. It is also too large to be sent
>     to the
>     > list as an attachment. Please give Yaron some time to provide fixed
>     > packages.
>     >
>     > Cheers,
>     > Stephan
>     >
>     > 2011/11/21 Pierre Réveillon<pierre@...
>     <mailto:pierre@...>>:
>     >> 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:krabina@...
>     <mailto:krabina@...>]
>     >>> 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
>     >>>> Semediawiki-user@...
>     <mailto:Semediawiki-user@...>
>     >>>> 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
>     >>> Semediawiki-user@...
>     <mailto:Semediawiki-user@...>
>     >>> 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
>     >>> Semediawiki-user@...
>     <mailto:Semediawiki-user@...>
>     >>> 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
>     >> Semediawiki-user@...
>     <mailto:Semediawiki-user@...>
>     >> 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
>     > Semediawiki-user@...
>     <mailto:Semediawiki-user@...>
>     > 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
>     Semediawiki-user@...
>     <mailto:Semediawiki-user@...>
>     https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>

> Van - to answer your question, see the original email. :)

Yes, I already found it:

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

But I still want an *example*.

Thanks anyway.


On Sat, 2011-11-19 at 21:49 -0500, Yaron Koren wrote:
> Hi everyone,
> 
> There were two issues with SF version 2.3 that have now been fixed:
> 
> - The downloadable files had some errors: they were missing the new CSS
> file for WikiEditor handling, and they didn't have the latest version of a
> few other files. The .tar.gz and .zip files have now been updated. If you
> already downloaded SF 2.3 via one of the files before, please download it
> again - sorry about that.
> 
> - There was a somewhat minor bug where, if a page-name formula consisted of
> only "<unique number>", the form didn't create the page - this is now
> fixed, in both SVN and the downloadable files.
> 
> So SF 2.3 is now re-released. :) If it turns out that there are any
> additional problems - if, for instance, the JS issue with WikiEditor that
> Pierre wrote about turns out to be an actual bug - the fixes will probably
> go into a new version of SF.
> 
> Van - to answer your question, see the original email. :)
> 
> -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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user

Hi Van,

Ah - by "example" you probably mean "demo". I don't think there's one yet,
unfortunately, but hopefully there will be soon.

-Yaron

On Thu, Nov 24, 2011 at 4:51 PM, Van de Bugger <van.de.bugger@...:

> > Van - to answer your question, see the original email. :)
>
> Yes, I already found it:
>
> > 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.
>
> But I still want an *example*.
>
> Thanks anyway.
>
>
> On Sat, 2011-11-19 at 21:49 -0500, Yaron Koren wrote:
> > Hi everyone,
> >
> > There were two issues with SF version 2.3 that have now been fixed:
> >
> > - The downloadable files had some errors: they were missing the new CSS
> > file for WikiEditor handling, and they didn't have the latest version of
> a
> > few other files. The .tar.gz and .zip files have now been updated. If you
> > already downloaded SF 2.3 via one of the files before, please download it
> > again - sorry about that.
> >
> > - There was a somewhat minor bug where, if a page-name formula consisted
> of
> > only "<unique number>", the form didn't create the page - this is now
> > fixed, in both SVN and the downloadable files.
> >
> > So SF 2.3 is now re-released. :) If it turns out that there are any
> > additional problems - if, for instance, the JS issue with WikiEditor that
> > Pierre wrote about turns out to be an actual bug - the fixes will
> probably
> > go into a new version of SF.
> >
> > Van - to answer your question, see the original email. :)
> >
> > -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
> > Semediawiki-user@...
> > 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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>



-- 
WikiWorks · MediaWiki Consulting · http://wikiworks.com

Hello Pierre,

Can I ask you something about your usage of properties. Looking the code from the Formulaire:Livre, I saw that you can specify a list of Editor with each time a set of properties (Editeur, Collection, ISBN, ...). 
{{{for template|Édition|label=Édition(s)|multiple|embed in field=Page Livre[Éditions]}}}

My question is how this is working, why the "Editor" content doesn't appears on the Livre (properties)? What is the mechanism here. Sorry for the newbies question. 

Olivier
 


On Nov 21, 2011, at 5:35 PM, Pierre Réveillon wrote:

> Hello Van,
> 
> It's not an official example at all, but I'm actually testing it on my 
> website.
> You can see it "working" here:
> The form source code: 
> http://www.delibris.fr/wiki/index.php?title=Formulaire:Livre&action=edit
> The form in action: 
> http://www.delibris.fr/wiki/index.php?title=AaaTest&action=formedit
> The generated code: 
> http://www.delibris.fr/wiki/index.php?title=AaaTest&action=edit
> The "subtemplate": 
> http://www.delibris.fr/wiki/index.php?title=Mod%C3%A8le:%C3%89dition&action=edit
> 
> It's just a raw test, for now I don't use/show the values. I'll put the 
> different sets of values in an infobox, but I'm not sure what would be 
> the cleaner way: make the "Édition" template to show an infobox, or in 
> the "Page_Livre" template, make a #ask to get Éditions sets, and call 
> the infobox here...
> 
> Regards,
> 
> --
> Pierre
> 
> On 19/11/2011 19:18, Van de Bugger wrote:
>>> - You can now nest calls to a multiple-instance template within a call
>>> to another template.
>> Great news! Any example how to use it?
>> 
>> Thanks,
>> Van.
>> 
>> On Fri, 2011-11-18 at 13:17 -0500, Yaron Koren wrote:
>>> 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
>>> Semediawiki-user@...
>>> 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
>> Semediawiki-user@...
>> 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
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user

Hello,

The list of editors is specified by the template "Édition" ({{{for 
template|Édition...).
So, in a Book, page, it will generate different template calls, for 
example in 
http://www.delibris.fr/wiki/index.php?title=Fortune_de_France_3_-_Paris,_ma_bonne_ville&action=edit:

{{Édition
|Édition originale=Oui
|Édition affichée par défaut=Oui
|Éditeur=Plon
|Année de parution=1980
|ISBN=9782259006873
|Est un extrait=Non
}}
{{Édition
|Édition originale=Non
|Édition affichée par défaut=Non
|Est un extrait=Non
}}

The "Édition" template 
(http://www.delibris.fr/wiki/index.php?title=Mod%C3%A8le:%C3%89dition&action=edit) 
sets the properties, using {{#set_internal:}} (provided by the Semantic 
Internal Objects extension, see 
http://www.mediawiki.org/wiki/Extension:Semantic_Internal_Objects)
I'm actually working on this template, because SIO seems to bug when you 
store AND query properties in the same page, so I'll modify this 
template to make it return someting that I can reuse on the page.

But this was working before the last Semantic Forms update, the multiple 
template instances were just appended to the page.
The last update adds the possibility to embed the multiple instances 
INSIDE the template generated by the form.
If you see the page 
http://www.delibris.fr/wiki/index.php?title=Fortune_de_France_3_-_Paris,_ma_bonne_ville&action=edit, 
the {{Édition}} calls are inside the {{Page_Livre}}, this allow me to 
use the editors (when the {{Édition}} template will return something) in 
the page, without querying it.


Hope that helps, don't hesitate if you have more questions!

Cheers,

-- 
Pierre


On 28/11/2011 12:45, Olivier Evalet wrote:
> Hello Pierre,
>
> Can I ask you something about your usage of properties. Looking the code from the Formulaire:Livre, I saw that you can specify a list of Editor with each time a set of properties (Editeur, Collection, ISBN, ...).
> {{{for template|Édition|label=Édition(s)|multiple|embed in field=Page Livre[Éditions]}}}
>
> My question is how this is working, why the "Editor" content doesn't appears on the Livre (properties)? What is the mechanism here. Sorry for the newbies question.
>
> Olivier
>
>
>
> On Nov 21, 2011, at 5:35 PM, Pierre Réveillon wrote:
>
>> Hello Van,
>>
>> It's not an official example at all, but I'm actually testing it on my
>> website.
>> You can see it "working" here:
>> The form source code:
>> http://www.delibris.fr/wiki/index.php?title=Formulaire:Livre&action=edit
>> The form in action:
>> http://www.delibris.fr/wiki/index.php?title=AaaTest&action=formedit
>> The generated code:
>> http://www.delibris.fr/wiki/index.php?title=AaaTest&action=edit
>> The "subtemplate":
>> http://www.delibris.fr/wiki/index.php?title=Mod%C3%A8le:%C3%89dition&action=edit
>>
>> It's just a raw test, for now I don't use/show the values. I'll put the
>> different sets of values in an infobox, but I'm not sure what would be
>> the cleaner way: make the "Édition" template to show an infobox, or in
>> the "Page_Livre" template, make a #ask to get Éditions sets, and call
>> the infobox here...
>>
>> Regards,
>>
>> --
>> Pierre
>>
>> On 19/11/2011 19:18, Van de Bugger wrote:
>>>> - You can now nest calls to a multiple-instance template within a call
>>>> to another template.
>>> Great news! Any example how to use it?
>>>
>>> Thanks,
>>> Van.
>>>
>>> On Fri, 2011-11-18 at 13:17 -0500, Yaron Koren wrote:
>>>> 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
>>>> Semediawiki-user@...
>>>> 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
>>> Semediawiki-user@...
>>> 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
>> Semediawiki-user@...
>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user

Thank you Pierre,
I see the "Edition du livre" SIO instances marked with # char!

Your site is a really good reference for my current database prototyping. I'm trying to convince my team using swm instead of a traditional development with SQL and java. My main task is to implement something that expose the schema and his integrity quality. I don't know what is the way for SMW to keep the "schema integrity" even after some refactoring (and this is a major issue)? I'm trying to "invent" a solution by adding meta properties and categories, even if, and I'm pretty sure, that natives query for maintain already exists. 

Sorry for my bad english!


Cheers,
Olivier


On Nov 28, 2011, at 2:20 PM, Pierre Réveillon wrote:

> Hello,
> 
> The list of editors is specified by the template "Édition" ({{{for template|Édition...).
> So, in a Book, page, it will generate different template calls, for example in http://www.delibris.fr/wiki/index.php?title=Fortune_de_France_3_-_Paris,_ma_bonne_ville&action=edit:
> 
> {{Édition
> |Édition originale=Oui
> |Édition affichée par défaut=Oui
> |Éditeur=Plon
> |Année de parution=1980
> |ISBN=9782259006873
> |Est un extrait=Non
> }}
> {{Édition
> |Édition originale=Non
> |Édition affichée par défaut=Non
> |Est un extrait=Non
> }}
> 
> The "Édition" template (http://www.delibris.fr/wiki/index.php?title=Mod%C3%A8le:%C3%89dition&action=edit) sets the properties, using {{#set_internal:}} (provided by the Semantic Internal Objects extension, see http://www.mediawiki.org/wiki/Extension:Semantic_Internal_Objects)
> I'm actually working on this template, because SIO seems to bug when you store AND query properties in the same page, so I'll modify this template to make it return someting that I can reuse on the page.
> 
> But this was working before the last Semantic Forms update, the multiple template instances were just appended to the page.
> The last update adds the possibility to embed the multiple instances INSIDE the template generated by the form.
> If you see the page http://www.delibris.fr/wiki/index.php?title=Fortune_de_France_3_-_Paris,_ma_bonne_ville&action=edit, the {{Édition}} calls are inside the {{Page_Livre}}, this allow me to use the editors (when the {{Édition}} template will return something) in the page, without querying it.
> 
> 
> Hope that helps, don't hesitate if you have more questions!
> 
> Cheers,
> 
> -- 
> Pierre
> 
> 
> On 28/11/2011 12:45, Olivier Evalet wrote:
>> Hello Pierre,
>> 
>> Can I ask you something about your usage of properties. Looking the code from the Formulaire:Livre, I saw that you can specify a list of Editor with each time a set of properties (Editeur, Collection, ISBN, ...).
>> {{{for template|Édition|label=Édition(s)|multiple|embed in field=Page Livre[Éditions]}}}
>> 
>> My question is how this is working, why the "Editor" content doesn't appears on the Livre (properties)? What is the mechanism here. Sorry for the newbies question.
>> 
>> Olivier
>> 
>> 
>> 
>> On Nov 21, 2011, at 5:35 PM, Pierre Réveillon wrote:
>> 
>>> Hello Van,
>>> 
>>> It's not an official example at all, but I'm actually testing it on my
>>> website.
>>> You can see it "working" here:
>>> The form source code:
>>> http://www.delibris.fr/wiki/index.php?title=Formulaire:Livre&action=edit
>>> The form in action:
>>> http://www.delibris.fr/wiki/index.php?title=AaaTest&action=formedit
>>> The generated code:
>>> http://www.delibris.fr/wiki/index.php?title=AaaTest&action=edit
>>> The "subtemplate":
>>> http://www.delibris.fr/wiki/index.php?title=Mod%C3%A8le:%C3%89dition&action=edit
>>> 
>>> It's just a raw test, for now I don't use/show the values. I'll put the
>>> different sets of values in an infobox, but I'm not sure what would be
>>> the cleaner way: make the "Édition" template to show an infobox, or in
>>> the "Page_Livre" template, make a #ask to get Éditions sets, and call
>>> the infobox here...
>>> 
>>> Regards,
>>> 
>>> --
>>> Pierre
>>> 
>>> On 19/11/2011 19:18, Van de Bugger wrote:
>>>>> - You can now nest calls to a multiple-instance template within a call
>>>>> to another template.
>>>> Great news! Any example how to use it?
>>>> 
>>>> Thanks,
>>>> Van.
>>>> 
>>>> On Fri, 2011-11-18 at 13:17 -0500, Yaron Koren wrote:
>>>>> 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
>>>>> Semediawiki-user@...
>>>>> 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
>>>> Semediawiki-user@...
>>>> 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
>>> Semediawiki-user@...
>>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>

Hi,

Unfortunately, nested templates does not work for me. I use
sophisticated set of forms and templates to provide ability to edit
parts of a page with normal looking "[edit]" links at the section
headings. Something goes wrong and does not work as expected.

It seems http://scratchpad.referata.com/wiki/ has the latest version of
SF, so I will try to recreate my setup there.

Thanks anyway,
Van.

On Fri, 2011-11-25 at 11:56 -0500, Yaron Koren wrote:
> Hi Van,
> 
> 
> Ah - by "example" you probably mean "demo". I don't think there's one
> yet, unfortunately, but hopefully there will be soon.
> 
> 
> -Yaron
> 
> On Thu, Nov 24, 2011 at 4:51 PM, Van de Bugger
> <van.de.bugger@...> wrote:
>         > Van - to answer your question, see the original email. :)
>         
>         
>         Yes, I already found it:
>         
>         > 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.
>         
>         
>         But I still want an *example*.
>         
>         Thanks anyway.
>         
>         
>         
>         On Sat, 2011-11-19 at 21:49 -0500, Yaron Koren wrote:
>         > Hi everyone,
>         >
>         > There were two issues with SF version 2.3 that have now been
>         fixed:
>         >
>         > - The downloadable files had some errors: they were missing
>         the new CSS
>         > file for WikiEditor handling, and they didn't have the
>         latest version of a
>         > few other files. The .tar.gz and .zip files have now been
>         updated. If you
>         > already downloaded SF 2.3 via one of the files before,
>         please download it
>         > again - sorry about that.
>         >
>         > - There was a somewhat minor bug where, if a page-name
>         formula consisted of
>         > only "<unique number>", the form didn't create the page -
>         this is now
>         > fixed, in both SVN and the downloadable files.
>         >
>         > So SF 2.3 is now re-released. :) If it turns out that there
>         are any
>         > additional problems - if, for instance, the JS issue with
>         WikiEditor that
>         > Pierre wrote about turns out to be an actual bug - the fixes
>         will probably
>         > go into a new version of SF.
>         >
>         > Van - to answer your question, see the original email. :)
>         >
>         > -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
>         > Semediawiki-user@...
>         >
>         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
>         Semediawiki-user@...
>         https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>         
> 
> 
> 
> 
> -- 
> WikiWorks · MediaWiki Consulting · http://wikiworks.com
>

Hi,

I created an example page:

http://scratchpad.referata.com/wiki/Sectioned_example_(1)

I think it is an interesting example how to split large form into
separate sections.

Need help: I want to convert multi-instance template `Sectioned example
(Personnel)' into nested template (a new feature of SF 2.3). 

Thanks,
Van.

On Tue, 2011-11-29 at 02:24 +0400, Van de Bugger wrote:
> Hi,
> 
> Unfortunately, nested templates does not work for me. I use
> sophisticated set of forms and templates to provide ability to edit
> parts of a page with normal looking "[edit]" links at the section
> headings. Something goes wrong and does not work as expected.
> 
> It seems http://scratchpad.referata.com/wiki/ has the latest version of
> SF, so I will try to recreate my setup there.
> 
> Thanks anyway,
> Van.
> 
> On Fri, 2011-11-25 at 11:56 -0500, Yaron Koren wrote:
> > Hi Van,
> > 
> > 
> > Ah - by "example" you probably mean "demo". I don't think there's one
> > yet, unfortunately, but hopefully there will be soon.
> > 
> > 
> > -Yaron
> > 
> > On Thu, Nov 24, 2011 at 4:51 PM, Van de Bugger
> > <van.de.bugger@...> wrote:
> >         > Van - to answer your question, see the original email. :)
> >         
> >         
> >         Yes, I already found it:
> >         
> >         > 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.
> >         
> >         
> >         But I still want an *example*.
> >         
> >         Thanks anyway.
> >         
> >         
> >         
> >         On Sat, 2011-11-19 at 21:49 -0500, Yaron Koren wrote:
> >         > Hi everyone,
> >         >
> >         > There were two issues with SF version 2.3 that have now been
> >         fixed:
> >         >
> >         > - The downloadable files had some errors: they were missing
> >         the new CSS
> >         > file for WikiEditor handling, and they didn't have the
> >         latest version of a
> >         > few other files. The .tar.gz and .zip files have now been
> >         updated. If you
> >         > already downloaded SF 2.3 via one of the files before,
> >         please download it
> >         > again - sorry about that.
> >         >
> >         > - There was a somewhat minor bug where, if a page-name
> >         formula consisted of
> >         > only "<unique number>", the form didn't create the page -
> >         this is now
> >         > fixed, in both SVN and the downloadable files.
> >         >
> >         > So SF 2.3 is now re-released. :) If it turns out that there
> >         are any
> >         > additional problems - if, for instance, the JS issue with
> >         WikiEditor that
> >         > Pierre wrote about turns out to be an actual bug - the fixes
> >         will probably
> >         > go into a new version of SF.
> >         >
> >         > Van - to answer your question, see the original email. :)
> >         >
> >         > -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
> >         > Semediawiki-user@...
> >         >
> >         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
> >         Semediawiki-user@...
> >         https://lists.sourceforge.net/lists/listinfo/semediawiki-user
> >         
> > 
> > 
> > 
> > 
> > -- 
> > WikiWorks · MediaWiki Consulting · http://wikiworks.com
> > 
>