I just tested this, and it was easy to do. Just run this:
php /path/to/SMW_setup.php -b SMWSQLStore2
That worked for me when I tested it just now. I don't think you'll have much
to worry about, because you can always regenerate SMW's database info from
scratch if something goes wrong.
--
View
Jeroen De Dauw-2 wrote
>
> Hey all,
>
> Lot's of great work has been done on SMW and related extensions recently,
> quite a bit of it by relatively new contributors.
>
Although I'm not a new contributor, I normally only contribute bug testing
and reports. I finally made my first very simple c
Thanks for the update! I'm following progress eagerly. This project is
important for the future of SMW.
--
View this message in context:
http://wikimedia.7.n6.nabble.com/Green-SMW-Progress-tp4955143p4964941.html
Sent from the Semantic Mediawiki - Development mailing list archive at
Nabble.com.
I just tested the examples in Opera, and it looks very nice. I did notice
that autoscroll didn't seem to be working, though.
--
View this message in context:
http://wikimedia.7.n6.nabble.com/SRF-1-7-SRF-Gallery-php-patch-allowing-a-gallery-to-be-displayed-as-carousel-using-jcarousel-plug-in-tp448
It sounds like you've lost the battle and it seems you've lost the war. But,
there's always the partisans and guerillas, and the war isn't over until
they say it's over.
You could try playing the subversive by running SMW clandestinely, and
making sure any data that goes into foswiki is also in S
I can't begin to describe my frustration at having spent an afternoon bug
testing, only to find that the "bug" I'm hunting is simply a version
incompatibility that is documented in an obscure corner of the many, many
places where SMW documentation is scattered. Example:
https://bugzilla.wikimedia.
This was reported as a bug here:
https://bugzilla.wikimedia.org/show_bug.cgi?id=33203
The short version is that SMWSQLStore2 is consuming all available memory
before failing. It has made all wiki pages that use SMW inaccessible. Is
there any advice on debugging this further, and hopefully correct
Did removing the sort parameter solve your problem? If it did, then this
appears to be an unreported bug.
--
View this message in context:
http://wikimedia.7.n6.nabble.com/In-line-queries-tp603651p1799820.html
Sent from the Semantic Mediawiki - Development mailing list archive at
Nabble.com.
--
Here's a fresh report for this enhancement:
https://bugzilla.wikimedia.org/show_bug.cgi?id=32976
--
View this message in context:
http://wikimedia.7.n6.nabble.com/one-to-many-validation-tp678004p1572068.html
Sent from the Semantic Mediawiki - Development mailing list archive at
Nabble.com.
---
I agree with Yaron. The "mandatory" parameter should have a limited meaning:
something must be entered. The "existing values only" parameter should not
require that something be entered. Instead, it only requires that IF
something is entered, it must be an existing value.
--
View this message in c
Here is the bug report for the issue being discussed:
https://bugzilla.wikimedia.org/show_bug.cgi?id=26088
--
View this message in context:
http://wikimedia.7.n6.nabble.com/one-to-many-validation-tp678004p1371217.html
Sent from the Semantic Mediawiki - Development mailing list archive at
Nabble
Will image queries be fixed in 1.6.2? They were broken in 1.6.1, so actually
1.6.0 is the last version that was fully functional. See this bug:
https://bugzilla.wikimedia.org/show_bug.cgi?id=30494
Markus Krötzsch-2 wrote:
>
> On 29/09/11 13:05, Toni Hermoso Pulido wrote:
>> Hello,
>>
>> I wa
Here's how I suggest solving the problem:
{{#if: {{#ask:[[Category:Images]] [[Belongs to::{{PAGENAME}}]] [[Main::Yes]]
[[Image of::Portrait]]|?}}
| {{#ask:[[Category:Images]] [[Belongs to::{{PAGENAME}}]]
[[Main::Yes]]
[[Image of::Portrait]]|?}}
| {{#formlink: form
I'm not sensitive to the consequences for code size, but I can tell you that
my plan for working around the lack of built-in uniqueness checking for
properties will probably involve a bot querying for duplicates, and then
removing them, discussed here:
http://old.nabble.com/forum/ViewPost.jtp?pos
I like the schedule idea. It provides a goal, and a measure of how accurately
it is being achieved. It's less important that it be correct, than to just
have it as an understood tentative guideline. By the way, I love the FreeBSD
development model. Have you seen this?:
http://en.wikipedia.org/wik
es -
> more info at [2]
>
> [1] http://www.w3.org/TR/sparql11-query/
>
> [2] http://semantic-mediawiki.org/wiki/Help:Using_SPARQL_and_RDF_stores
>
>
>> -Original Message-
>> From: badon [mailto:fastgoldf...@gmail.com]
>> Sent: Wednesday, A
es -
> more info at [2]
>
> [1] http://www.w3.org/TR/sparql11-query/
>
> [2] http://semantic-mediawiki.org/wiki/Help:Using_SPARQL_and_RDF_stores
>
>
>> -Original Message-
>> From: badon [mailto:fastgoldf...@gmail.com]
>> Sent: Wednesday, A
A page can have more than one property, and a property can be another page
that has properties of its own. Properties can form a complex web (connected
graph). The best-practice is for properties to point from child to parent,
so the graph ends up looking more like a tree than a web. That best-pra
It looks like I had left out NS_IMAGE from $smwgNamespacesWithSemanticLinks
So, it's not a bug after all.
Problem solved!
badon wrote:
>
> To see this wiki, you'll need this login info:
>
> user: demo
> pass: dedauw
>
> I think I've triggered a bug,
To see this wiki, you'll need this login info:
user: demo
pass: dedauw
I think I've triggered a bug, but I'm not sure exactly what did it, so I
need help figuring out how to make a useful bug report. On this page, and
also on the pages listed in the first two tables at the top, there are
supp
20 matches
Mail list logo
