From: <Asa...@pr...> - 2011-11-10 03:17:40
|
I have enabled simple user tagging on our wiki pages using a property [[Has keywords::<string>]]. Here's an example: http://wiki.prov.vic.gov.au/index.php/Number_3_East_Street,_Ballarat_East I don't want users to have to worry about keeping their tags the same i.e. New York as opposed to new york. At the moment if these tags get entered on separate pages they are not seen as the same value. How do I make SMW see them as the same value despite them being in different cases? Cheers Asa Letourneau Digital Projects Officer, Public Record Office Victoria 03 9348 5759 I M 0432 263 402 I F 03 9348 5656 asa...@pr... Events | http://www.prov.vic.gov.au/whats-on News | http://prov.vic.gov.au/publications/blog 2011 Local History Grant recipients | http://prov.vic.gov.au/community-programs/grants-awards/local-history-grants You must not copy, disclose, distribute, store or otherwise use this material without permission. Any personal information in this email must be handled in accordance with the Information Privacy Act 2000 (Vic) and applicable laws. If you are not the intended recipient, please notify the sender immediately and destroy all copies of this email and any attachments. The State does not accept liability in connection with computer viruses, data corruption, delay, interruption, unauthorised access or use. ********************************************************************** Any personal or sensitive information contained in this email and attachments must be handled in accordance with the Victorian Information Privacy Act 2000, the Health Records Act 2001 or the Privacy Act 1988 (Commonwealth), as applicable. This email, including all attachments, is confidential. If you are not the intended recipient, you must not disclose, distribute, copy or use the information contained in this email or attachments. Any confidentiality or privilege is not waived or lost because this email has been sent to you in error. If you have received it in error, please let us know by reply email, delete it from your system and destroy any copies. ********************************************************************** |
From: James H. K. <jam...@gm...> - 2011-11-10 04:11:55
|
Hi, You might want to apply a formatting [1] hidden in a template before the the value is assigned to a property: [[Has keywords::{{lc:string}} ]] convert to lower case inputs or [[Has keywords::{{uc:string}}]] convert to upper case inputs. Either way consistency on formatting in all places where [[Has keywords ... ]] does gets mentioned is necessary. [1] http://www.mediawiki.org/wiki/Help:Magic_words#Formatting Cheers MWJames On Thu, Nov 10, 2011 at 12:17 PM, <Asa...@pr...> wrote: > > > > > I have enabled simple user tagging on our wiki pages using a property [[Has > keywords::<string>]]. Here's an example: > > http://wiki.prov.vic.gov.au/index.php/Number_3_East_Street,_Ballarat_East > > I don't want users to have to worry about keeping their tags the same i.e. > New York as opposed to new york. At the moment if these tags get entered on > separate pages they are not seen as the same value. How do I make SMW see > them as the same value despite them being in different cases? > > Cheers > Asa Letourneau > Digital Projects Officer, Public Record Office Victoria > 03 9348 5759 I M 0432 263 402 I F 03 9348 5656 > asa...@pr... > > Events | http://www.prov.vic.gov.au/whats-on > News | http://prov.vic.gov.au/publications/blog > 2011 Local History Grant recipients | > http://prov.vic.gov.au/community-programs/grants-awards/local-history-grants > > > You must not copy, disclose, distribute, store or otherwise use this > material without permission. Any personal information in this email must be > handled in accordance with the Information Privacy Act 2000 (Vic) and > applicable laws. If you are not the intended recipient, please notify the > sender immediately and destroy all copies of this email and any > attachments. The State does not accept liability in connection with > computer viruses, data corruption, delay, interruption, unauthorised access > or use. > ********************************************************************** > Any personal or sensitive information contained in this email and > attachments must be handled in accordance with the Victorian Information > Privacy Act 2000, the Health Records Act 2001 or the Privacy Act 1988 > (Commonwealth), as applicable. > > This email, including all attachments, is confidential. If you are not the > intended recipient, you must not disclose, distribute, copy or use the > information contained in this email or attachments. Any confidentiality or > privilege is not waived or lost because this email has been sent to you in > error. If you have received it in error, please let us know by reply > email, delete it from your system and destroy any copies. > ********************************************************************** > > > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > |
From: Bruce W. <br...@fu...> - 2011-11-10 08:15:07
|
I have the #forminput parser function on a Template and everything seems ok but the form never loads. I get a box where one can enter the name of the page to create, and it does the autocomplete just fine. It starts to load the popup but it never loads anything. What could be the problem? I didn't include the query because I just let people fill in the value into the field and with autocomplete all is fine. Here is the code I use: {{#forminput:form=Marriage|size=100|default value=Marriage of Wife Name and Husband Name|button text=Add/Edit Marriage|autocomplete on category=Bio:Marriage|popup}} The default value is supposed to just help people with giving them an idea of how to format the page. Thanks, Bruce |
From: Yaron K. <ya...@wi...> - 2011-11-10 14:33:14
|
Hi Bruce, I think this was a bug in previous SVN versions of Semantic Forms, that is now fixed in the current SVN code. If you're using SVN, could you try updating your code? By the way, "inline query" is the term specifically for "#ask". The generally term for functions within wiki-text, like #forminput, is "parser functions". -Yaron On Thu, Nov 10, 2011 at 2:04 AM, Bruce Whealton <br...@fu... > wrote: > I have the #forminput parser function on a Template and everything seems > ok but the form never loads. I get a box where one can enter the name of > the page to create, and it does the autocomplete just fine. It starts to > load the popup but it never loads anything. What could be the problem? I > didn't include the query because I just let people fill in the value into > the field and with autocomplete all is fine. Here is the code I use: > > {{#forminput:form=Marriage|size=100|default value=Marriage of Wife Name > and Husband Name|button text=Add/Edit Marriage|autocomplete on > category=Bio:Marriage|popup}} > > The default value is supposed to just help people with giving them an idea > of how to format the page. > Thanks, > Bruce > > > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Bruce W. <br...@wh...> - 2011-11-11 06:44:40
|
Yaron, I just got the latest SVN and uploaded that to the site but it still has the same problem. Thanks for clarifying the terms. I tried removing the popup from the parser function and it worked fine. I wonder if there is a conflict with other JQuery lightbox plug-ins that I tried to setup to enable a lightbox effect for editing other content. Unfortunately, the other JQuery lightbox plug-ins did not work on mediawiki, which isn't actually a Semantic Mediawiki issue but it is strange because I have used JQuery lightbox type effects on other sites and even on CMS but I couldn't get it to work with MediaWiki. Anyway, I just wonder if those plug-ins added to my skin caused a conflict and problem with the popup parameter for the parser function. It's a long shot but who knows. Bruce ++++++++++++++++++++++++++++++++++++++++++++++++++ Bruce Whealton, Owner Future Wave Designs http://FutureWaveDesigns.com (Web Design/Web Development FOAF: http://whealton.info/BruceWhealtonJr/foaf.rdf Please join the following genealogy site for sharing and collaborating: http://whealton.info/w/ http://whealton.info/Genealogy/urllist.html - list of genealogy data http://futurewavedesigns.com/wordpress/ Web Technology wiki: http://futurewavedesigns.com/w/ ++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Yaron Koren [mailto:ya...@wi...] Sent: Thursday, November 10, 2011 9:33 AM To: Bruce Whealton Cc: sem...@li... Subject: Re: [Semediawiki-user] Inline Query #forminput help Hi Bruce, I think this was a bug in previous SVN versions of Semantic Forms, that is now fixed in the current SVN code. If you're using SVN, could you try updating your code? By the way, "inline query" is the term specifically for "#ask". The generally term for functions within wiki-text, like #forminput, is "parser functions". -Yaron On Thu, Nov 10, 2011 at 2:04 AM, Bruce Whealton <br...@fu... > wrote: > I have the #forminput parser function on a Template and everything > seems ok but the form never loads. I get a box where one can enter > the name of the page to create, and it does the autocomplete just > fine. It starts to load the popup but it never loads anything. What > could be the problem? I didn't include the query because I just let > people fill in the value into the field and with autocomplete all is fine. Here is the code I use: > > {{#forminput:form=Marriage|size=100|default value=Marriage of Wife > Name and Husband Name|button text=Add/Edit Marriage|autocomplete on > category=Bio:Marriage|popup}} > > The default value is supposed to just help people with giving them an > idea of how to format the page. > Thanks, > Bruce > > > > ---------------------------------------------------------------------- > -------- > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- WikiWorks . MediaWiki Consulting . http://wikiworks.com ---------------------------------------------------------------------------- -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Semediawiki-user mailing list Sem...@li... https://lists.sourceforge.net/lists/listinfo/semediawiki-user |
From: Stephan G. <s7...@gm...> - 2011-11-11 09:35:46
|
Hi Bruce, I just tried it to ensure nothing broke badly with the last changes and it worked here, so I think there must be something particular to your setup. Could you try replace the forminput with a formlink for a moment and see if that works? Also could you have a look at your javascript error log (Ctrl+Shift+J on Firefox) if there is anything in there? Oh and I guess you would have told us if it were, but is your wiki public? Cheers, Stephan On 11 November 2011 07:44, Bruce Whealton <br...@wh...> wrote: > Yaron, > I just got the latest SVN and uploaded that to the site but it still has the > same problem. > Thanks for clarifying the terms. I tried removing the popup from the parser > function and it worked fine. I wonder if there is a conflict with other > JQuery lightbox plug-ins that I tried to setup to enable a lightbox effect > for editing other content. Unfortunately, the other JQuery lightbox > plug-ins did not work on mediawiki, which isn't actually a Semantic > Mediawiki issue but it is strange because I have used JQuery lightbox type > effects on other sites and even on CMS but I couldn't get it to work with > MediaWiki. Anyway, I just wonder if those plug-ins added to my skin caused > a conflict and problem with the popup parameter for the parser function. > It's a long shot but who knows. > Bruce > > ++++++++++++++++++++++++++++++++++++++++++++++++++ > Bruce Whealton, Owner Future Wave Designs > http://FutureWaveDesigns.com (Web Design/Web Development > FOAF: http://whealton.info/BruceWhealtonJr/foaf.rdf > Please join the following genealogy site for sharing and collaborating: > http://whealton.info/w/ > http://whealton.info/Genealogy/urllist.html - list of genealogy data > http://futurewavedesigns.com/wordpress/ > Web Technology wiki: http://futurewavedesigns.com/w/ > ++++++++++++++++++++++++++++++++++++++++++++++++++ > > -----Original Message----- > From: Yaron Koren [mailto:ya...@wi...] > Sent: Thursday, November 10, 2011 9:33 AM > To: Bruce Whealton > Cc: sem...@li... > Subject: Re: [Semediawiki-user] Inline Query #forminput help > > Hi Bruce, > > I think this was a bug in previous SVN versions of Semantic Forms, that is > now fixed in the current SVN code. If you're using SVN, could you try > updating your code? > > By the way, "inline query" is the term specifically for "#ask". The > generally term for functions within wiki-text, like #forminput, is "parser > functions". > > -Yaron > > On Thu, Nov 10, 2011 at 2:04 AM, Bruce Whealton <br...@fu... >> wrote: > >> I have the #forminput parser function on a Template and everything >> seems ok but the form never loads. I get a box where one can enter >> the name of the page to create, and it does the autocomplete just >> fine. It starts to load the popup but it never loads anything. What >> could be the problem? I didn't include the query because I just let >> people fill in the value into the field and with autocomplete all is fine. > Here is the code I use: >> >> {{#forminput:form=Marriage|size=100|default value=Marriage of Wife >> Name and Husband Name|button text=Add/Edit Marriage|autocomplete on >> category=Bio:Marriage|popup}} >> >> The default value is supposed to just help people with giving them an >> idea of how to format the page. >> Thanks, >> Bruce |