Hi,
I looked at your discourse db and what I think I'm after is the 'Options for
this item' functionality on the 'Edit an opinion item' page. There is this
'Add another' button which (as far as I can see) opens a form which when
saved writes a further {{Opinion|...}} template call to the page, which in
turn defines some SMW properties.
So my page ABC would contain none or one or several {{Opinion|...}} calls
and when a button 'Edit with form' is pressed, the existing opinions are
shown and also an 'Add another' button or if possible already an empty form
is displayed. On saving this adds another {{Opinion|...}} call and in that
template the 'new' property is filled and set with the form fields/template
parameters.
So maybe the page ABC should rather be Talk:ABC and on page ABC a button
'Edit Talk:ABC with form' could be placed (if that is possible).
I guess what does the work is the 'for template|opinion' in the item form
and there the 'multiple' parameter which adds the 'Add another' button and
allows more than one opinion.
I'll read and try a bit more to see if I can get it to do what I have in
mind.
Thanks
Gun
Yaron Koren wrote:
>
> Hi,
>
> It sounds like there may be unclarity here on what SF does. It doesn't
> allow
> adding properties to pages per se; it adds and edits wiki pages that
> contain
> template calls which contain property definitions. Does that make sense? I
> think (I hope) that understanding that, and then reviewing the SF
> documentation, will clarify your issues.
>
> -Yaron
>
>
> On Wed, Apr 1, 2009 at 10:37 AM, mbwgu <[email protected]> wrote:
>
>>
>>
>> I'm trying to use SF for the following:
>> Provide a Button/Link on a page ABC to a form in order to allow users to
>> add a SMW property to either the talk page for ABC (Talk:ABC) or a
>> sub-page
>> of ABC (ABC/userproperties) (whatever option is easier to implement).
>>
>> I don't want the user involved on which page the new property is added as
>> this should just depend on the page from which the form is called via the
>> button/link ({{PAGENAME}}). So either {{TALKPAGENAME}} or
>> {{PAGENAME}}/Userproperty should be used.
>> So while #forminput allows to use 'super_page=' for sub-pages it also
>> allows
>> the user to mess with the pagename even if the right one is used as
>> default
>> in the input field. On the other hand #formlink, which avoids the input
>> field for the pagename, doesn't recognize a 'super_page=' value in the
>> query
>> parameter.
>> Adding something like {{{info|page name={{TALKPAGENAME}} }}} to the form
>> causes a blank page after form submission.
>> Is there a way around that?
>>
>> Is it in principle possible to add multiple occurences of the same
>> property
>> on one page? In my test, after the first property was added via a form,
>> calling the form a second time displayed the values of the previously
>> added
>> property in the fields and changing the values modified the existing
>> content
>> rather than adding a second property declaration on the page.
>>
>> Thanks for any tips.
>> Gun
>> --
>> View this message in context:
>> http://www.nabble.com/SF-to-add-multiple-occurences-of-a-SMW-properties-on-one-page--tp22826274p22826274.html
>> Sent from the Semantic Forms mailing list archive at Nabble.com.
>>
>>
>> >
>>
>
> >
>
>
--
View this message in context:
http://www.nabble.com/SF-to-add-multiple-occurences-of-a-SMW-properties-on-one-page--tp22826274p22829536.html
Sent from the Semantic Forms mailing list archive at Nabble.com.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Semantic Forms" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/semantic-forms?hl=en
-~----------~----~----~----~------~----~------~--~---
