From: Ben P. <bp...@gm...> - 2012-08-10 21:30:05
|
Folks, I've got a template within which I'm putting a #formlink like this: {{#formlink:form=Secondary_Form |link text=Add New Entry |link type=button |Secondary_Template[First_Property]={{BASEPAGENAME}} |Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}} |Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} }} I get a button, which does open the correct form. Unfortunately, none of the specified values get passed to the form when it opens. I've recently added the additional two query string params. This used to work when I had it like this: {{#formlink:form=Secondary_Form |link text=Add New Entry |link type=button |Secondary_Template[First_Property]={{BASEPAGENAME}} }} The {{BASEPAGENAME}} value from the page calling the primary template was passed into the form as the value of First_Property. Now, however, even that value doesn't get passed into the form, so long as I have these properties in the #formlink. One more note: I tried using this syntax as well, however this gave me a button that did nothing when clicked: {{#formlink:form=Secondary_Form |link text=Add New Entry |link type=button |query string=Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} }} I can confirm that the Local_Template_Property_A and Local_Template_Property_B are valid, as those params are referenced earlier in the template, and they do work. I have another template which uses something similar, but which is working correctly: {{#formlink:form=Yet_Another_Form |link type=button |link text=New Entry |query string=Yet Another_Template[Property Name 1]={{{Local Property Name 1|}}}&Yet_Another_Template[Property Name 2]={{{Local List Property 1|}}},%20{{{Local List Property 2|}}} }} I can confirm that in the one that's not working that the form name, the template name, and the property names are all correct. I can also confirm that in the local template where this #formlink is called from, the properties being passed are valid and have values. Any thoughts would be greatly appreciated. Thanks. -Ben Pitzer |
From: Bruce W. <bwh...@fu...> - 2012-08-11 08:26:30
|
Hello all, I understand that it is common for Semantic Web and Linked Data applications to use content negotiation to return either RDF or HTML depending on the requesting agent. I looked into this and found one article from a while back where this was proposed for Wikipedia to redirect to Dbpedia. There wasn't any response to it. There is the RDFa extension that is no longer being supported and there are 3 versions of this. There is nothing that really tells you why you would use one or the other version. The third version seems to allow for generating triples from a page. I couldn't get this extension to work. I had commented out the RDFa_extractor link and it seemed to work until I asked for a certain page and it then gave me an error. I have quite a bit of data and have some of it in a triple store, Fuseki, which is based on the Jena (Java) project. We never could get the triple store to serve as the data source for the wiki. I have MediaWiki version 1.17.0 and SMW (1.6.1). I had a developer working with me who suggested against upgrading everything. So far, the only option, I've found is to add a link on a page for generating the Special:ExportRDF version of the page. It is taking a long time, so maybe I need to change backlinks to false. Even though for Linked Data purposes it is better for it to be true. Any suggestions on this? I mean the ability to use content negotiation? Thanks, Bruce |
From: Yaron K. <ya...@wi...> - 2012-08-13 19:20:37
|
Hi Ben, Obviously, that shouldn't happen. Is this happening on a public wiki? If not, could you try to replicate it on a public wiki, like http://scratchpad.referata.com ? -Yaron On Fri, Aug 10, 2012 at 5:29 PM, Ben Pitzer <bp...@gm...> wrote: > Folks, > > I've got a template within which I'm putting a #formlink like this: > > {{#formlink:form=Secondary_Form > |link text=Add New Entry > |link type=button > |Secondary_Template[First_Property]={{BASEPAGENAME}} > |Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}} > |Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} > }} > > I get a button, which does open the correct form. Unfortunately, none of > the specified values get passed to the form when it opens. I've recently > added the additional two query string params. This used to work when I had > it like this: > > {{#formlink:form=Secondary_Form > |link text=Add New Entry > |link type=button > |Secondary_Template[First_Property]={{BASEPAGENAME}} > }} > > The {{BASEPAGENAME}} value from the page calling the primary template was > passed into the form as the value of First_Property. Now, however, even > that value doesn't get passed into the form, so long as I have these > properties in the #formlink. > > One more note: I tried using this syntax as well, however this gave me a > button that did nothing when clicked: > > {{#formlink:form=Secondary_Form > |link text=Add New Entry > |link type=button > |query > > string=Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} > }} > > I can confirm that the Local_Template_Property_A > and Local_Template_Property_B are valid, as those params are referenced > earlier in the template, and they do work. I have another template which > uses something similar, but which is working correctly: > > {{#formlink:form=Yet_Another_Form > |link type=button > |link text=New Entry > |query string=Yet Another_Template[Property Name 1]={{{Local > Property Name 1|}}}&Yet_Another_Template[Property Name 2]={{{Local List > Property 1|}}},%20{{{Local List Property 2|}}} > }} > > I can confirm that in the one that's not working that the form name, the > template name, and the property names are all correct. I can also confirm > that in the local template where this #formlink is called from, the > properties being passed are valid and have values. > > Any thoughts would be greatly appreciated. Thanks. > > -Ben Pitzer > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Ben P. <bp...@gm...> - 2012-08-13 21:20:48
|
Yaron, I think I figured out most of the issue. The big problem is that the contents of {{{Local_Template_Property_B|}}} are a text field with a wiki-formatted list. Thus, the query string now has # symbols in it when the passed property is expanded in the HTML. Unfortunately, that is a problem. I've tried formatting that field differently, using plaintext, even, but that doesn't see to help either. I suspect that I must somehow #urlencode that field's contents before they can be passed to the Secondary_Template's form field. Unfortunately, it doesn't work (apparently) to try this: {{#formlink:form=Secondary_Form |link text=Add New Entry |link type=button |Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{#urlencode:{{{Local_Template_Property_B|}}} }} }} Any thoughts on how to pass this along would be appreciated. As it is, it appears to be passing the first 2 properties when I put them together, and leave the Third_Property in a different line, or else leave it out altogether. Thanks. -Ben Pitzer On Mon, Aug 13, 2012 at 3:20 PM, Yaron Koren <ya...@wi...> wrote: > Hi Ben, > > Obviously, that shouldn't happen. Is this happening on a public wiki? If > not, could you try to replicate it on a public wiki, like > http://scratchpad.referata.com ? > > -Yaron > > On Fri, Aug 10, 2012 at 5:29 PM, Ben Pitzer <bp...@gm...> wrote: > >> Folks, >> >> I've got a template within which I'm putting a #formlink like this: >> >> {{#formlink:form=Secondary_Form >> |link text=Add New Entry >> |link type=button >> |Secondary_Template[First_Property]={{BASEPAGENAME}} >> |Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}} >> |Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} >> }} >> >> I get a button, which does open the correct form. Unfortunately, none of >> the specified values get passed to the form when it opens. I've recently >> added the additional two query string params. This used to work when I >> had >> it like this: >> >> {{#formlink:form=Secondary_Form >> |link text=Add New Entry >> |link type=button >> |Secondary_Template[First_Property]={{BASEPAGENAME}} >> }} >> >> The {{BASEPAGENAME}} value from the page calling the primary template was >> passed into the form as the value of First_Property. Now, however, even >> that value doesn't get passed into the form, so long as I have these >> properties in the #formlink. >> >> One more note: I tried using this syntax as well, however this gave me a >> button that did nothing when clicked: >> >> {{#formlink:form=Secondary_Form >> |link text=Add New Entry >> |link type=button >> |query >> >> string=Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} >> }} >> >> I can confirm that the Local_Template_Property_A >> and Local_Template_Property_B are valid, as those params are referenced >> earlier in the template, and they do work. I have another template which >> uses something similar, but which is working correctly: >> >> {{#formlink:form=Yet_Another_Form >> |link type=button >> |link text=New Entry >> |query string=Yet Another_Template[Property Name 1]={{{Local >> Property Name 1|}}}&Yet_Another_Template[Property Name 2]={{{Local List >> Property 1|}}},%20{{{Local List Property 2|}}} >> }} >> >> I can confirm that in the one that's not working that the form name, the >> template name, and the property names are all correct. I can also confirm >> that in the local template where this #formlink is called from, the >> properties being passed are valid and have values. >> >> Any thoughts would be greatly appreciated. Thanks. >> >> -Ben Pitzer >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> > > > > -- > WikiWorks · MediaWiki Consulting · http://wikiworks.com > |
From: Ben P. <bp...@gm...> - 2012-08-13 21:50:11
|
Another quick update on my progress: {{urlencode:{{{Local_Template_Property_B|}}} }} does work, however it replaces all of the spaces with a + character in the form that gets opened, which is less than ideal. Still playing with this. -Ben Pitzer On Mon, Aug 13, 2012 at 5:20 PM, Ben Pitzer <bp...@gm...> wrote: > Yaron, > > I think I figured out most of the issue. The big problem is that the > contents of {{{Local_Template_Property_B|}}} are a text field with a > wiki-formatted list. Thus, the query string now has # symbols in it when > the passed property is expanded in the HTML. Unfortunately, that is a > problem. I've tried formatting that field differently, using plaintext, > even, but that doesn't see to help either. I suspect that I must somehow > #urlencode that field's contents before they can be passed to the > Secondary_Template's form field. Unfortunately, it doesn't work > (apparently) to try this: > > {{#formlink:form=Secondary_Form > |link text=Add New Entry > |link type=button > > |Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{#urlencode:{{{Local_Template_Property_B|}}} > }} > }} > > Any thoughts on how to pass this along would be appreciated. As it is, it > appears to be passing the first 2 properties when I put them together, and > leave the Third_Property in a different line, or else leave it out > altogether. Thanks. > > -Ben Pitzer > > On Mon, Aug 13, 2012 at 3:20 PM, Yaron Koren <ya...@wi...> wrote: > >> Hi Ben, >> >> Obviously, that shouldn't happen. Is this happening on a public wiki? If >> not, could you try to replicate it on a public wiki, like >> http://scratchpad.referata.com ? >> >> -Yaron >> >> On Fri, Aug 10, 2012 at 5:29 PM, Ben Pitzer <bp...@gm...> wrote: >> >>> Folks, >>> >>> I've got a template within which I'm putting a #formlink like this: >>> >>> {{#formlink:form=Secondary_Form >>> |link text=Add New Entry >>> |link type=button >>> |Secondary_Template[First_Property]={{BASEPAGENAME}} >>> |Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}} >>> |Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} >>> }} >>> >>> I get a button, which does open the correct form. Unfortunately, none of >>> the specified values get passed to the form when it opens. I've recently >>> added the additional two query string params. This used to work when I >>> had >>> it like this: >>> >>> {{#formlink:form=Secondary_Form >>> |link text=Add New Entry >>> |link type=button >>> |Secondary_Template[First_Property]={{BASEPAGENAME}} >>> }} >>> >>> The {{BASEPAGENAME}} value from the page calling the primary template was >>> passed into the form as the value of First_Property. Now, however, even >>> that value doesn't get passed into the form, so long as I have these >>> properties in the #formlink. >>> >>> One more note: I tried using this syntax as well, however this gave me a >>> button that did nothing when clicked: >>> >>> {{#formlink:form=Secondary_Form >>> |link text=Add New Entry >>> |link type=button >>> |query >>> >>> string=Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} >>> }} >>> >>> I can confirm that the Local_Template_Property_A >>> and Local_Template_Property_B are valid, as those params are referenced >>> earlier in the template, and they do work. I have another template which >>> uses something similar, but which is working correctly: >>> >>> {{#formlink:form=Yet_Another_Form >>> |link type=button >>> |link text=New Entry >>> |query string=Yet Another_Template[Property Name 1]={{{Local >>> Property Name 1|}}}&Yet_Another_Template[Property Name 2]={{{Local List >>> Property 1|}}},%20{{{Local List Property 2|}}} >>> }} >>> >>> I can confirm that in the one that's not working that the form name, the >>> template name, and the property names are all correct. I can also >>> confirm >>> that in the local template where this #formlink is called from, the >>> properties being passed are valid and have values. >>> >>> Any thoughts would be greatly appreciated. Thanks. >>> >>> -Ben Pitzer >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> Semediawiki-user mailing list >>> Sem...@li... >>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >>> >> >> >> >> -- >> WikiWorks · MediaWiki Consulting · http://wikiworks.com >> > > |
From: Ben P. <bp...@gm...> - 2012-08-24 15:29:32
|
Folks, Since I hate seeing questions on mailing lists which ask a question that I'm having trouble with, but which fall off and never explain how it was resolved, I thought I'd follow up on this post with what caused and ultimately semi-resolved my issue. As I noted, the fact that {{{Local Template Property B|}}} contained a wiki list was the problem. It was apparently choking on things like the # characters, which of course have specific meanings in URLs. Thus, the link was treating my property contents like part of the URL, rather than the contents of a value being passed in that URL. The answer is very similar to what I had put in here earlier, but instead of using the string function {{#urlencode:foo}}, I used the magic word {{urlencode: foo}} which apparently works better for this particular problem. Unfortunately, any spaces that I have in my list show up in Form:Secondary_Form as a + instead of a space. Unfortunately, however, there's no way to {{urldecode}} those contents in the form, so far as I'm aware. The presence of a + sign instead of a space isn't too big an issue for now, but some day it could be more of a problem. I haven't yet seen if any other special characters get odd representation in the form. I should probably test that. In the meantime, if anybody has any ideas on how I could do a better job of passing the contents of that local template field in the {{#formlink}} to the second form, I would be glad to hear them. Thanks. Answer syntax: {{#formlink:form=Secondary_Form |link text=Add New Entry |link type=button |Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{urlencode:{{{Local_Template_Property_B|}}} }} }} -Ben Pitzer On Mon, Aug 13, 2012 at 5:50 PM, Ben Pitzer <bp...@gm...> wrote: > Another quick update on my progress: > {{urlencode:{{{Local_Template_Property_B|}}} }} does work, however it > replaces all of the spaces with a + character in the form that gets opened, > which is less than ideal. Still playing with this. > > -Ben Pitzer > > > On Mon, Aug 13, 2012 at 5:20 PM, Ben Pitzer <bp...@gm...> wrote: > >> Yaron, >> >> I think I figured out most of the issue. The big problem is that the >> contents of {{{Local_Template_Property_B|}}} are a text field with a >> wiki-formatted list. Thus, the query string now has # symbols in it when >> the passed property is expanded in the HTML. Unfortunately, that is a >> problem. I've tried formatting that field differently, using plaintext, >> even, but that doesn't see to help either. I suspect that I must somehow >> #urlencode that field's contents before they can be passed to the >> Secondary_Template's form field. Unfortunately, it doesn't work >> (apparently) to try this: >> >> {{#formlink:form=Secondary_Form >> |link text=Add New Entry >> |link type=button >> >> |Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{#urlencode:{{{Local_Template_Property_B|}}} >> }} >> }} >> >> Any thoughts on how to pass this along would be appreciated. As it is, >> it appears to be passing the first 2 properties when I put them together, >> and leave the Third_Property in a different line, or else leave it out >> altogether. Thanks. >> >> -Ben Pitzer >> >> On Mon, Aug 13, 2012 at 3:20 PM, Yaron Koren <ya...@wi...> wrote: >> >>> Hi Ben, >>> >>> Obviously, that shouldn't happen. Is this happening on a public wiki? If >>> not, could you try to replicate it on a public wiki, like >>> http://scratchpad.referata.com ? >>> >>> -Yaron >>> >>> On Fri, Aug 10, 2012 at 5:29 PM, Ben Pitzer <bp...@gm...> wrote: >>> >>>> Folks, >>>> >>>> I've got a template within which I'm putting a #formlink like this: >>>> >>>> {{#formlink:form=Secondary_Form >>>> |link text=Add New Entry >>>> |link type=button >>>> |Secondary_Template[First_Property]={{BASEPAGENAME}} >>>> >>>> |Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}} >>>> |Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} >>>> }} >>>> >>>> I get a button, which does open the correct form. Unfortunately, none >>>> of >>>> the specified values get passed to the form when it opens. I've >>>> recently >>>> added the additional two query string params. This used to work when I >>>> had >>>> it like this: >>>> >>>> {{#formlink:form=Secondary_Form >>>> |link text=Add New Entry >>>> |link type=button >>>> |Secondary_Template[First_Property]={{BASEPAGENAME}} >>>> }} >>>> >>>> The {{BASEPAGENAME}} value from the page calling the primary template >>>> was >>>> passed into the form as the value of First_Property. Now, however, even >>>> that value doesn't get passed into the form, so long as I have these >>>> properties in the #formlink. >>>> >>>> One more note: I tried using this syntax as well, however this gave me >>>> a >>>> button that did nothing when clicked: >>>> >>>> {{#formlink:form=Secondary_Form >>>> |link text=Add New Entry >>>> |link type=button >>>> |query >>>> >>>> string=Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} >>>> }} >>>> >>>> I can confirm that the Local_Template_Property_A >>>> and Local_Template_Property_B are valid, as those params are referenced >>>> earlier in the template, and they do work. I have another template >>>> which >>>> uses something similar, but which is working correctly: >>>> >>>> {{#formlink:form=Yet_Another_Form >>>> |link type=button >>>> |link text=New Entry >>>> |query string=Yet Another_Template[Property Name 1]={{{Local >>>> Property Name 1|}}}&Yet_Another_Template[Property Name 2]={{{Local List >>>> Property 1|}}},%20{{{Local List Property 2|}}} >>>> }} >>>> >>>> I can confirm that in the one that's not working that the form name, the >>>> template name, and the property names are all correct. I can also >>>> confirm >>>> that in the local template where this #formlink is called from, the >>>> properties being passed are valid and have values. >>>> >>>> Any thoughts would be greatly appreciated. Thanks. >>>> >>>> -Ben Pitzer >>>> >>>> ------------------------------------------------------------------------------ >>>> Live Security Virtual Conference >>>> Exclusive live event will cover all the ways today's security and >>>> threat landscape has changed and how IT managers can respond. >>>> Discussions >>>> will include endpoint security, mobile security and the latest in >>>> malware >>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>> _______________________________________________ >>>> Semediawiki-user mailing list >>>> Sem...@li... >>>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >>>> >>> >>> >>> >>> -- >>> WikiWorks · MediaWiki Consulting · http://wikiworks.com >>> >> >> > |
From: Yaron K. <ya...@wi...> - 2012-08-24 15:42:55
|
Hi Ben, One option, if I understand the issue correctly, is to have the values {{{Local Template Property B|}}} just separated by commas, instead of using the "#" syntax. I'm pretty sure you could have the template then use #arraymap to display the values as a bulleted list. -Yaron On Fri, Aug 24, 2012 at 11:29 AM, Ben Pitzer <bp...@gm...> wrote: > Folks, > > Since I hate seeing questions on mailing lists which ask a question that > I'm having trouble with, but which fall off and never explain how it was > resolved, I thought I'd follow up on this post with what caused and > ultimately semi-resolved my issue. > > As I noted, the fact that {{{Local Template Property B|}}} contained a > wiki list was the problem. It was apparently choking on things like the # > characters, which of course have specific meanings in URLs. Thus, the link > was treating my property contents like part of the URL, rather than the > contents of a value being passed in that URL. The answer is very similar > to what I had put in here earlier, but instead of using the string function > {{#urlencode:foo}}, I used the magic word {{urlencode: foo}} which > apparently works better for this particular problem. Unfortunately, any > spaces that I have in my list show up in Form:Secondary_Form as a + instead > of a space. Unfortunately, however, there's no way to {{urldecode}} those > contents in the form, so far as I'm aware. The presence of a + sign > instead of a space isn't too big an issue for now, but some day it could be > more of a problem. I haven't yet seen if any other special characters get > odd representation in the form. I should probably test that. In the > meantime, if anybody has any ideas on how I could do a better job of > passing the contents of that local template field in the {{#formlink}} to > the second form, I would be glad to hear them. Thanks. > > Answer syntax: > > {{#formlink:form=Secondary_Form > |link text=Add New Entry > |link type=button > > |Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{urlencode:{{{Local_Template_Property_B|}}} > }} > }} > > -Ben Pitzer > > > On Mon, Aug 13, 2012 at 5:50 PM, Ben Pitzer <bp...@gm...> wrote: > >> Another quick update on my progress: >> {{urlencode:{{{Local_Template_Property_B|}}} }} does work, however it >> replaces all of the spaces with a + character in the form that gets opened, >> which is less than ideal. Still playing with this. >> >> -Ben Pitzer >> >> >> On Mon, Aug 13, 2012 at 5:20 PM, Ben Pitzer <bp...@gm...> wrote: >> >>> Yaron, >>> >>> I think I figured out most of the issue. The big problem is that the >>> contents of {{{Local_Template_Property_B|}}} are a text field with a >>> wiki-formatted list. Thus, the query string now has # symbols in it when >>> the passed property is expanded in the HTML. Unfortunately, that is a >>> problem. I've tried formatting that field differently, using plaintext, >>> even, but that doesn't see to help either. I suspect that I must somehow >>> #urlencode that field's contents before they can be passed to the >>> Secondary_Template's form field. Unfortunately, it doesn't work >>> (apparently) to try this: >>> >>> {{#formlink:form=Secondary_Form >>> |link text=Add New Entry >>> |link type=button >>> >>> |Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{#urlencode:{{{Local_Template_Property_B|}}} >>> }} >>> }} >>> >>> Any thoughts on how to pass this along would be appreciated. As it is, >>> it appears to be passing the first 2 properties when I put them together, >>> and leave the Third_Property in a different line, or else leave it out >>> altogether. Thanks. >>> >>> -Ben Pitzer >>> >>> On Mon, Aug 13, 2012 at 3:20 PM, Yaron Koren <ya...@wi...>wrote: >>> >>>> Hi Ben, >>>> >>>> Obviously, that shouldn't happen. Is this happening on a public wiki? >>>> If not, could you try to replicate it on a public wiki, like >>>> http://scratchpad.referata.com ? >>>> >>>> -Yaron >>>> >>>> On Fri, Aug 10, 2012 at 5:29 PM, Ben Pitzer <bp...@gm...> wrote: >>>> >>>>> Folks, >>>>> >>>>> I've got a template within which I'm putting a #formlink like this: >>>>> >>>>> {{#formlink:form=Secondary_Form >>>>> |link text=Add New Entry >>>>> |link type=button >>>>> |Secondary_Template[First_Property]={{BASEPAGENAME}} >>>>> >>>>> |Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}} >>>>> >>>>> |Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} >>>>> }} >>>>> >>>>> I get a button, which does open the correct form. Unfortunately, none >>>>> of >>>>> the specified values get passed to the form when it opens. I've >>>>> recently >>>>> added the additional two query string params. This used to work when >>>>> I had >>>>> it like this: >>>>> >>>>> {{#formlink:form=Secondary_Form >>>>> |link text=Add New Entry >>>>> |link type=button >>>>> |Secondary_Template[First_Property]={{BASEPAGENAME}} >>>>> }} >>>>> >>>>> The {{BASEPAGENAME}} value from the page calling the primary template >>>>> was >>>>> passed into the form as the value of First_Property. Now, however, >>>>> even >>>>> that value doesn't get passed into the form, so long as I have these >>>>> properties in the #formlink. >>>>> >>>>> One more note: I tried using this syntax as well, however this gave >>>>> me a >>>>> button that did nothing when clicked: >>>>> >>>>> {{#formlink:form=Secondary_Form >>>>> |link text=Add New Entry >>>>> |link type=button >>>>> |query >>>>> >>>>> string=Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} >>>>> }} >>>>> >>>>> I can confirm that the Local_Template_Property_A >>>>> and Local_Template_Property_B are valid, as those params are referenced >>>>> earlier in the template, and they do work. I have another template >>>>> which >>>>> uses something similar, but which is working correctly: >>>>> >>>>> {{#formlink:form=Yet_Another_Form >>>>> |link type=button >>>>> |link text=New Entry >>>>> |query string=Yet Another_Template[Property Name 1]={{{Local >>>>> Property Name 1|}}}&Yet_Another_Template[Property Name 2]={{{Local List >>>>> Property 1|}}},%20{{{Local List Property 2|}}} >>>>> }} >>>>> >>>>> I can confirm that in the one that's not working that the form name, >>>>> the >>>>> template name, and the property names are all correct. I can also >>>>> confirm >>>>> that in the local template where this #formlink is called from, the >>>>> properties being passed are valid and have values. >>>>> >>>>> Any thoughts would be greatly appreciated. Thanks. >>>>> >>>>> -Ben Pitzer >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Live Security Virtual Conference >>>>> Exclusive live event will cover all the ways today's security and >>>>> threat landscape has changed and how IT managers can respond. >>>>> Discussions >>>>> will include endpoint security, mobile security and the latest in >>>>> malware >>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>> _______________________________________________ >>>>> Semediawiki-user mailing list >>>>> Sem...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >>>>> >>>> >>>> >>>> >>>> -- >>>> WikiWorks · MediaWiki Consulting · http://wikiworks.com >>>> >>> >>> >> > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Ben P. <bp...@gm...> - 2012-08-28 12:50:59
|
I could see how that would resolve the issue, however I'm looking for a numbered list. The contents of the field are a meeting agenda, and consequently when input they need to show up in the original page (Template:Local_Template) as such. It would be confusing for the users to be instructed to enter their agenda as a comma delimited list of agenda items, I think, rather than as a wiki-formatted ordered list. Incidentally, what you suggest is what is happening with {{{Local Template Property A|}}}, as that is a comma delimited list of meeting attendees. Thanks for the response. -Ben Pitzer On Fri, Aug 24, 2012 at 11:42 AM, Yaron Koren <ya...@wi...> wrote: > Hi Ben, > > One option, if I understand the issue correctly, is to have the > values {{{Local Template Property B|}}} just separated by commas, instead > of using the "#" syntax. I'm pretty sure you could have the template then > use #arraymap to display the values as a bulleted list. > > -Yaron > > > On Fri, Aug 24, 2012 at 11:29 AM, Ben Pitzer <bp...@gm...> wrote: > >> Folks, >> >> Since I hate seeing questions on mailing lists which ask a question that >> I'm having trouble with, but which fall off and never explain how it was >> resolved, I thought I'd follow up on this post with what caused and >> ultimately semi-resolved my issue. >> >> As I noted, the fact that {{{Local Template Property B|}}} contained a >> wiki list was the problem. It was apparently choking on things like the # >> characters, which of course have specific meanings in URLs. Thus, the link >> was treating my property contents like part of the URL, rather than the >> contents of a value being passed in that URL. The answer is very similar >> to what I had put in here earlier, but instead of using the string function >> {{#urlencode:foo}}, I used the magic word {{urlencode: foo}} which >> apparently works better for this particular problem. Unfortunately, any >> spaces that I have in my list show up in Form:Secondary_Form as a + instead >> of a space. Unfortunately, however, there's no way to {{urldecode}} those >> contents in the form, so far as I'm aware. The presence of a + sign >> instead of a space isn't too big an issue for now, but some day it could be >> more of a problem. I haven't yet seen if any other special characters get >> odd representation in the form. I should probably test that. In the >> meantime, if anybody has any ideas on how I could do a better job of >> passing the contents of that local template field in the {{#formlink}} to >> the second form, I would be glad to hear them. Thanks. >> >> Answer syntax: >> >> {{#formlink:form=Secondary_Form >> |link text=Add New Entry >> |link type=button >> >> |Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{urlencode:{{{Local_Template_Property_B|}}} >> }} >> }} >> >> -Ben Pitzer >> >> >> On Mon, Aug 13, 2012 at 5:50 PM, Ben Pitzer <bp...@gm...> wrote: >> >>> Another quick update on my progress: >>> {{urlencode:{{{Local_Template_Property_B|}}} }} does work, however it >>> replaces all of the spaces with a + character in the form that gets opened, >>> which is less than ideal. Still playing with this. >>> >>> -Ben Pitzer >>> >>> >>> On Mon, Aug 13, 2012 at 5:20 PM, Ben Pitzer <bp...@gm...> wrote: >>> >>>> Yaron, >>>> >>>> I think I figured out most of the issue. The big problem is that the >>>> contents of {{{Local_Template_Property_B|}}} are a text field with a >>>> wiki-formatted list. Thus, the query string now has # symbols in it when >>>> the passed property is expanded in the HTML. Unfortunately, that is a >>>> problem. I've tried formatting that field differently, using plaintext, >>>> even, but that doesn't see to help either. I suspect that I must somehow >>>> #urlencode that field's contents before they can be passed to the >>>> Secondary_Template's form field. Unfortunately, it doesn't work >>>> (apparently) to try this: >>>> >>>> {{#formlink:form=Secondary_Form >>>> |link text=Add New Entry >>>> |link type=button >>>> >>>> |Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{#urlencode:{{{Local_Template_Property_B|}}} >>>> }} >>>> }} >>>> >>>> Any thoughts on how to pass this along would be appreciated. As it is, >>>> it appears to be passing the first 2 properties when I put them together, >>>> and leave the Third_Property in a different line, or else leave it out >>>> altogether. Thanks. >>>> >>>> -Ben Pitzer >>>> >>>> On Mon, Aug 13, 2012 at 3:20 PM, Yaron Koren <ya...@wi...>wrote: >>>> >>>>> Hi Ben, >>>>> >>>>> Obviously, that shouldn't happen. Is this happening on a public wiki? >>>>> If not, could you try to replicate it on a public wiki, like >>>>> http://scratchpad.referata.com ? >>>>> >>>>> -Yaron >>>>> >>>>> On Fri, Aug 10, 2012 at 5:29 PM, Ben Pitzer <bp...@gm...> wrote: >>>>> >>>>>> Folks, >>>>>> >>>>>> I've got a template within which I'm putting a #formlink like this: >>>>>> >>>>>> {{#formlink:form=Secondary_Form >>>>>> |link text=Add New Entry >>>>>> |link type=button >>>>>> |Secondary_Template[First_Property]={{BASEPAGENAME}} >>>>>> >>>>>> |Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}} >>>>>> >>>>>> |Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} >>>>>> }} >>>>>> >>>>>> I get a button, which does open the correct form. Unfortunately, >>>>>> none of >>>>>> the specified values get passed to the form when it opens. I've >>>>>> recently >>>>>> added the additional two query string params. This used to work when >>>>>> I had >>>>>> it like this: >>>>>> >>>>>> {{#formlink:form=Secondary_Form >>>>>> |link text=Add New Entry >>>>>> |link type=button >>>>>> |Secondary_Template[First_Property]={{BASEPAGENAME}} >>>>>> }} >>>>>> >>>>>> The {{BASEPAGENAME}} value from the page calling the primary template >>>>>> was >>>>>> passed into the form as the value of First_Property. Now, however, >>>>>> even >>>>>> that value doesn't get passed into the form, so long as I have these >>>>>> properties in the #formlink. >>>>>> >>>>>> One more note: I tried using this syntax as well, however this gave >>>>>> me a >>>>>> button that did nothing when clicked: >>>>>> >>>>>> {{#formlink:form=Secondary_Form >>>>>> |link text=Add New Entry >>>>>> |link type=button >>>>>> |query >>>>>> >>>>>> string=Secondary_Template[First_Property]={{BASEPAGENAME}}&Secondary_Template[Second_Property]={{{Local_Template_Property_A|}}}&Secondary_Template[Third_Property]={{{Local_Template_Property_B|}}} >>>>>> }} >>>>>> >>>>>> I can confirm that the Local_Template_Property_A >>>>>> and Local_Template_Property_B are valid, as those params are >>>>>> referenced >>>>>> earlier in the template, and they do work. I have another template >>>>>> which >>>>>> uses something similar, but which is working correctly: >>>>>> >>>>>> {{#formlink:form=Yet_Another_Form >>>>>> |link type=button >>>>>> |link text=New Entry >>>>>> |query string=Yet Another_Template[Property Name >>>>>> 1]={{{Local >>>>>> Property Name 1|}}}&Yet_Another_Template[Property Name 2]={{{Local >>>>>> List >>>>>> Property 1|}}},%20{{{Local List Property 2|}}} >>>>>> }} >>>>>> >>>>>> I can confirm that in the one that's not working that the form name, >>>>>> the >>>>>> template name, and the property names are all correct. I can also >>>>>> confirm >>>>>> that in the local template where this #formlink is called from, the >>>>>> properties being passed are valid and have values. >>>>>> >>>>>> Any thoughts would be greatly appreciated. Thanks. >>>>>> >>>>>> -Ben Pitzer >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Live Security Virtual Conference >>>>>> Exclusive live event will cover all the ways today's security and >>>>>> threat landscape has changed and how IT managers can respond. >>>>>> Discussions >>>>>> will include endpoint security, mobile security and the latest in >>>>>> malware >>>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>>> _______________________________________________ >>>>>> Semediawiki-user mailing list >>>>>> Sem...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> WikiWorks · MediaWiki Consulting · http://wikiworks.com >>>>> >>>> >>>> >>> >> > > > -- > WikiWorks · MediaWiki Consulting · http://wikiworks.com > |