Re: [SMW-devel] [Semediawiki-user] Upgrade Fail
Thanks, Markus, that helped. I think it must have been the Start updating data on Special:SMWAdmin I did a while back. Something got lost in there when I had incompatible versions of SMW and SMW+. Appreciate your help. On Mon, Aug 16, 2010 at 7:08 AM, Markus Krötzsch mar...@semantic-mediawiki.org wrote: On 16/08/2010 06:34, Robert Murphy wrote: Dear Sirs and Madams, I posted on this before but the situation is worse than I feared. I upgraded to SMW 1.15.1.1 to get the n-ary functionality I so desperately need. But now, properties on pages are disappearing and runJobs.php (my bread and butter) doesn't work. Well, it does about 4 pages and then says Fatal error: Call to a member function getNamespace() on a non-object in /../www/mediawiki/includes/JobQueue.php on line 277 I have disabled EVERY other extension and this still happens! Any help would be greatly appreciated. It seems that some problematic jobs are in your job queue. A brute force way to kill these is to empty that table job in your MediaWiki installation. This can be done either using some graphical UI, or by executing the MySQL query: TRUNCATE TABLE job; after logging in to your server (selecting the appropriate database). I recall such issues some time back in rare cases, and I thought the SMW jobs had been guarded against this potential problem since then. Maybe there is another place where it happens. In general, the problem should occur due to the job queue containing a job for a page name that is not a valid title. When trying to use this page name, a page object is attempted to be created, but no such object is returned. The software then seems to access this supposed object without checking its validitiy, leading to the error you see. For debugging this, it would be useful if you could post some more output, if available. Especially the name of the job and, if possible, of the page it acts on. Regards, Markus Sadly, Robert Murphy -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-user mailing list semediawiki-u...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-user -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] [Semediawiki-user] Possible defect in Semantic Forms
Hi John, That doesn't sound like a defect - regardless of what you see on the property page, the actual semantic data (allowed values, in this case) doesn't get updated until there's some sort of update action taken, like a page save. In any case, that's not the ideal way to do it - you should instead define an SMW concept that holds that query, and then use either values from concept or autocomplete on concept in the form input (probably the former). -Yaron On Mon, Aug 16, 2010 at 12:50 PM, John Arrowwood j...@irie-inc.com wrote: I have a sequence of pages that all have a common base page, Structured Documents. So, for example, I have Structured Documents/Term for the page that has the definition of a glossary Term. I created a property. The definition of that property includes a query that returns all of those structured documents, listing only their name without the Structured Documents prefix. The idea was that the property will be a dropdown on the appropriate form which shows a cleaned-up version of the page names. The intention is that as soon as I added a new Structured Document, the property would update its 'allowed' list, and the new document would appear in the dropdown. In reality, I have to go to the page for that property, make a meaningless change, then click Save in order for the change to be picked up. Even though I can go to the page, click Purge, and see the new item in the list, that alone is not enough. I have to edit and save before the new item(s) appear in the dropdown of a form. So the defect is that even though you view the property page and see the list of allowed values, the form is not picking up the new list of allowed values. However, the real NEED here is a way of associating a form on a page with a queried list of values. Unfortunately, I have tried in vain to do that. If I put a template call in the default= part of the field definition, it isn't treated as a template, and so the user sees it as a template, not as a list of values. What is the proper way of accomplishing this goal? -- John Arrowwood John (at) Irie (dash) Inc (dot) com John (at) Arrowwood Photography (dot) com John (at) Hanlons Razor (dot) com -- http://www.irie-inc.com/ http://arrowwood.blogspot.com/ -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-user mailing list semediawiki-u...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-user -- WikiWorks · MediaWiki Consulting · http://wikiworks.com -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] [Semediawiki-user] Possible defect in Semantic Forms
Has there been any discussion about ways around the data update issue? Maybe there could be a way for SMW to run the data repair/upgrade in the background? I've run into this annoyance countless times. It would be nice not to have to turn off page caching for the whole wiki. AK On Mon, Aug 16, 2010 at 10:05 AM, Yaron Koren yaro...@gmail.com wrote: Hi John, That doesn't sound like a defect - regardless of what you see on the property page, the actual semantic data (allowed values, in this case) doesn't get updated until there's some sort of update action taken, like a page save. In any case, that's not the ideal way to do it - you should instead define an SMW concept that holds that query, and then use either values from concept or autocomplete on concept in the form input (probably the former). -Yaron On Mon, Aug 16, 2010 at 12:50 PM, John Arrowwood j...@irie-inc.com wrote: I have a sequence of pages that all have a common base page, Structured Documents. So, for example, I have Structured Documents/Term for the page that has the definition of a glossary Term. I created a property. The definition of that property includes a query that returns all of those structured documents, listing only their name without the Structured Documents prefix. The idea was that the property will be a dropdown on the appropriate form which shows a cleaned-up version of the page names. The intention is that as soon as I added a new Structured Document, the property would update its 'allowed' list, and the new document would appear in the dropdown. In reality, I have to go to the page for that property, make a meaningless change, then click Save in order for the change to be picked up. Even though I can go to the page, click Purge, and see the new item in the list, that alone is not enough. I have to edit and save before the new item(s) appear in the dropdown of a form. So the defect is that even though you view the property page and see the list of allowed values, the form is not picking up the new list of allowed values. However, the real NEED here is a way of associating a form on a page with a queried list of values. Unfortunately, I have tried in vain to do that. If I put a template call in the default= part of the field definition, it isn't treated as a template, and so the user sees it as a template, not as a list of values. What is the proper way of accomplishing this goal? -- John Arrowwood John (at) Irie (dash) Inc (dot) com John (at) Arrowwood Photography (dot) com John (at) Hanlons Razor (dot) com -- http://www.irie-inc.com/ http://arrowwood.blogspot.com/ -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-user mailing list semediawiki-u...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-user -- WikiWorks · MediaWiki Consulting · http://wikiworks.com -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-user mailing list semediawiki-u...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-user -- Alex Kozak Program Assistant Creative Commons -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] RDFIO 0.4.0 Released - GSoC Finished
Wanted to announce that version 0.4.0 of RDFIO [0] is now released. This also marks the finishing of my GSoC 2010 project [1]. I posted a blog post which wraps up some notes regarding both the new release, and the GSoC in general [2]. Thanks for a great time! [0] http://localhost/smw/index.php/Special:RDFIO [1] http://www.mediawiki.org/wiki/User:SHL/GSoC2010 [2] http://saml.rilspace.org/rdfio-040-released-gsoc-finished Best Regards Samuel P.S. For those who wonder, I can also mention that I'm planning a transition to MediaWiki repositories (from the current one at Google code) in the near future. -- Samuel Lampa --- Biotech Student @ Uppsala University GSoC Student @ Semantic MediaWiki Mentor: Denny Vrandečić --- Blog: http://saml.rilspace.org Twitter: http://twitter.com/samuellampa --- -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] RDFIO 0.4.0 Released - GSoC Finished
On 08/16/2010 08:11 PM, Samuel Lampa wrote: [0] http://localhost/smw/index.php/Special:RDFIO So typical ... should of course be: [0] http://www.mediawiki.org/wiki/Extension:RDFIO // Samuel -- Samuel Lampa --- Biotech Student @ Uppsala University GSoC Student @ Semantic MediaWiki Mentor: Denny Vrandečić --- Blog: http://saml.rilspace.org Twitter: http://twitter.com/samuellampa --- -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Adding autocompletion for printouts to Special:Ask
Hi, Sanyam (who is cc'ed) has been working hard on his Google Summer of Code project, which has been about converting SMW and various of its extensions to use the jQuery Javascript library, and to generally use more Javascript. The project is basically done now, and you'll be hearing a lot more about it later, including from Sanyam. For now, I just wanted to ask one question - I'm planning to start checking in a lot of Sanyam's code to SVN soon, and there's one change to Semantic MediaWiki itself that I wanted to ask about. Sanyam added autocompletion for the additional data/printouts textarea, which you can see here if you start typing: http://discoursedb.org/wiki/Special:Ask I just wanted to know if anyone thinks this autocompletion is a bad idea, or has any comments/criticisms about the specific look-and-feel of it. Thanks, Yaron -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] [Semediawiki-user] Possible defect in Semantic Forms
I tried all of those options. The problem is, I don't want to display the page name in the drop-down. I want to be able to filter the output using a template, or something, and I couldn't find a way to do that with a 'concept'. Did I miss something? The only solution I could find was to embed the valid values in the property page via a query. And you are telling me, that doesn't work, either. So what WILL do what is needed? On Mon, Aug 16, 2010 at 1:05 PM, Yaron Koren yaro...@gmail.com wrote: Hi John, That doesn't sound like a defect - regardless of what you see on the property page, the actual semantic data (allowed values, in this case) doesn't get updated until there's some sort of update action taken, like a page save. In any case, that's not the ideal way to do it - you should instead define an SMW concept that holds that query, and then use either values from concept or autocomplete on concept in the form input (probably the former). -Yaron On Mon, Aug 16, 2010 at 12:50 PM, John Arrowwood j...@irie-inc.comwrote: I have a sequence of pages that all have a common base page, Structured Documents. So, for example, I have Structured Documents/Term for the page that has the definition of a glossary Term. I created a property. The definition of that property includes a query that returns all of those structured documents, listing only their name without the Structured Documents prefix. The idea was that the property will be a dropdown on the appropriate form which shows a cleaned-up version of the page names. The intention is that as soon as I added a new Structured Document, the property would update its 'allowed' list, and the new document would appear in the dropdown. In reality, I have to go to the page for that property, make a meaningless change, then click Save in order for the change to be picked up. Even though I can go to the page, click Purge, and see the new item in the list, that alone is not enough. I have to edit and save before the new item(s) appear in the dropdown of a form. So the defect is that even though you view the property page and see the list of allowed values, the form is not picking up the new list of allowed values. However, the real NEED here is a way of associating a form on a page with a queried list of values. Unfortunately, I have tried in vain to do that. If I put a template call in the default= part of the field definition, it isn't treated as a template, and so the user sees it as a template, not as a list of values. What is the proper way of accomplishing this goal? -- John Arrowwood John (at) Irie (dash) Inc (dot) com John (at) Arrowwood Photography (dot) com John (at) Hanlons Razor (dot) com -- http://www.irie-inc.com/ http://arrowwood.blogspot.com/ -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-user mailing list semediawiki-u...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-user -- WikiWorks · MediaWiki Consulting · http://wikiworks.com -- John Arrowwood John (at) Irie (dash) Inc (dot) com John (at) Arrowwood Photography (dot) com John (at) Hanlons Razor (dot) com -- http://www.irie-inc.com/ http://arrowwood.blogspot.com/ -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] [Semediawiki-user] Possible defect in Semantic Forms
Hi Alex, The SemanticUpdateOnPurge extension, which I'm told is bug-free, :) might be what you're looking for: http://www.mediawiki.org/wiki/Extension:SemanticUpdateOnPurge I assume that's what you're talking about, though your comment about page caching is a little odd - turning off page caching won't affect data updating. John - in a sense, this extension might be helpful for you as well; though I'm always sure there's a better way for you to do whatever it is you're trying to do; though, not knowing your data structure, I don't know what that is. -Yaron On Mon, Aug 16, 2010 at 1:14 PM, Alex Kozak ako...@creativecommons.orgwrote: Has there been any discussion about ways around the data update issue? Maybe there could be a way for SMW to run the data repair/upgrade in the background? I've run into this annoyance countless times. It would be nice not to have to turn off page caching for the whole wiki. AK On Mon, Aug 16, 2010 at 10:05 AM, Yaron Koren yaro...@gmail.com wrote: Hi John, That doesn't sound like a defect - regardless of what you see on the property page, the actual semantic data (allowed values, in this case) doesn't get updated until there's some sort of update action taken, like a page save. In any case, that's not the ideal way to do it - you should instead define an SMW concept that holds that query, and then use either values from concept or autocomplete on concept in the form input (probably the former). -Yaron On Mon, Aug 16, 2010 at 12:50 PM, John Arrowwood j...@irie-inc.com wrote: I have a sequence of pages that all have a common base page, Structured Documents. So, for example, I have Structured Documents/Term for the page that has the definition of a glossary Term. I created a property. The definition of that property includes a query that returns all of those structured documents, listing only their name without the Structured Documents prefix. The idea was that the property will be a dropdown on the appropriate form which shows a cleaned-up version of the page names. The intention is that as soon as I added a new Structured Document, the property would update its 'allowed' list, and the new document would appear in the dropdown. In reality, I have to go to the page for that property, make a meaningless change, then click Save in order for the change to be picked up. Even though I can go to the page, click Purge, and see the new item in the list, that alone is not enough. I have to edit and save before the new item(s) appear in the dropdown of a form. So the defect is that even though you view the property page and see the list of allowed values, the form is not picking up the new list of allowed values. However, the real NEED here is a way of associating a form on a page with a queried list of values. Unfortunately, I have tried in vain to do that. If I put a template call in the default= part of the field definition, it isn't treated as a template, and so the user sees it as a template, not as a list of values. What is the proper way of accomplishing this goal? -- John Arrowwood John (at) Irie (dash) Inc (dot) com John (at) Arrowwood Photography (dot) com John (at) Hanlons Razor (dot) com -- http://www.irie-inc.com/ http://arrowwood.blogspot.com/ -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-user mailing list semediawiki-u...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-user -- WikiWorks · MediaWiki Consulting · http://wikiworks.com -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-user mailing list semediawiki-u...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-user -- Alex Kozak Program Assistant Creative Commons -- WikiWorks · MediaWiki Consulting · http://wikiworks.com -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] [Semediawiki-user] Possible defect in Semantic Forms
Ah, my apologies. Disabling page caching had been discussed as a potential solution to the data update issue on one wiki in the past but it was before I got involved in the project. Thanks for the link, I'll take a look! AK On Mon, Aug 16, 2010 at 2:34 PM, Yaron Koren yaro...@gmail.com wrote: Hi Alex, The SemanticUpdateOnPurge extension, which I'm told is bug-free, :) might be what you're looking for: http://www.mediawiki.org/wiki/Extension:SemanticUpdateOnPurge I assume that's what you're talking about, though your comment about page caching is a little odd - turning off page caching won't affect data updating. John - in a sense, this extension might be helpful for you as well; though I'm always sure there's a better way for you to do whatever it is you're trying to do; though, not knowing your data structure, I don't know what that is. -Yaron On Mon, Aug 16, 2010 at 1:14 PM, Alex Kozak ako...@creativecommons.orgwrote: Has there been any discussion about ways around the data update issue? Maybe there could be a way for SMW to run the data repair/upgrade in the background? I've run into this annoyance countless times. It would be nice not to have to turn off page caching for the whole wiki. AK On Mon, Aug 16, 2010 at 10:05 AM, Yaron Koren yaro...@gmail.com wrote: Hi John, That doesn't sound like a defect - regardless of what you see on the property page, the actual semantic data (allowed values, in this case) doesn't get updated until there's some sort of update action taken, like a page save. In any case, that's not the ideal way to do it - you should instead define an SMW concept that holds that query, and then use either values from concept or autocomplete on concept in the form input (probably the former). -Yaron On Mon, Aug 16, 2010 at 12:50 PM, John Arrowwood j...@irie-inc.com wrote: I have a sequence of pages that all have a common base page, Structured Documents. So, for example, I have Structured Documents/Term for the page that has the definition of a glossary Term. I created a property. The definition of that property includes a query that returns all of those structured documents, listing only their name without the Structured Documents prefix. The idea was that the property will be a dropdown on the appropriate form which shows a cleaned-up version of the page names. The intention is that as soon as I added a new Structured Document, the property would update its 'allowed' list, and the new document would appear in the dropdown. In reality, I have to go to the page for that property, make a meaningless change, then click Save in order for the change to be picked up. Even though I can go to the page, click Purge, and see the new item in the list, that alone is not enough. I have to edit and save before the new item(s) appear in the dropdown of a form. So the defect is that even though you view the property page and see the list of allowed values, the form is not picking up the new list of allowed values. However, the real NEED here is a way of associating a form on a page with a queried list of values. Unfortunately, I have tried in vain to do that. If I put a template call in the default= part of the field definition, it isn't treated as a template, and so the user sees it as a template, not as a list of values. What is the proper way of accomplishing this goal? -- John Arrowwood John (at) Irie (dash) Inc (dot) com John (at) Arrowwood Photography (dot) com John (at) Hanlons Razor (dot) com -- http://www.irie-inc.com/ http://arrowwood.blogspot.com/ -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-user mailing list semediawiki-u...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-user -- WikiWorks · MediaWiki Consulting · http://wikiworks.com -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-user mailing list semediawiki-u...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-user -- Alex Kozak Program Assistant Creative Commons -- WikiWorks · MediaWiki Consulting · http://wikiworks.com -- Alex Kozak Program Assistant Creative Commons -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
Re: [SMW-devel] Adding autocompletion for printouts to Special:Ask
Hi, On 2010-08-17 02:16, Yaron Koren wrote: Sanyam (who is cc'ed) has been working hard on his Google Summer of Code project, which has been about converting SMW and various of its extensions to use the jQuery Javascript library, and to generally use more Javascript. The project is basically done now, and you'll be hearing a lot more about it later, including from Sanyam. Great news, thanks! :) For now, I just wanted to ask one question - I'm planning to start checking in a lot of Sanyam's code to SVN soon, and there's one change to Semantic MediaWiki itself that I wanted to ask about. Sanyam added autocompletion for the additional data/printouts textarea, which you can see here if you start typing: http://discoursedb.org/wiki/Special:Ask I just wanted to know if anyone thinks this autocompletion is a bad idea, or has any comments/criticisms about the specific look-and-feel of it. It looks very useful, and it will make figuring out a query much much easier. I often found myself switching between an example page's Browse properties page and Special:Ask, and copy- and pasting the property names into the 'additional data to display' field. That is no longer necessary with this functionality - big improvement for the user! I see a potential problem with Wikis that have a very large amount of properties - Special:Ask would then load slowly, because all those property names are in the page. Would it be possible to choose, like in SF, between 'autocompletion' and 'remote autocompletion'? Also, the dropdown does not have its own scrollbar, which looks a bit weird when there are hundreds of properties in it - but it's not really a problem, and I don't know if it would actually be better if the dropdown had a scrollbar. Patrick. -- Key ID: 0x86E346D4http://patrick-nagel.net/key.asc Fingerprint: 7745 E1BE FA8B FBAD 76AB 2BFC C981 E686 86E3 46D4 signature.asc Description: OpenPGP digital signature -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
