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