(Redirected from Talk:Semantic MediaWiki)
Jump to: navigation, search
Community portal of Semantic MediaWiki

Welcome to the community portal. This is the place for general inquiries, your ideas or comments concerning this wiki. Here you may get in touch with one of the admins of this wiki, who also use this portal as a noticeboard.

If you are looking for support with problem about the software itself, please have a look at the info page on getting support.

We are always looking for ways to improve documentation and communication with the community therefore it would help us if you could take 5 minutes of your time and fill out the survey form. Thank you.

First page
First page
Previous page
Previous page
Last page
Last page

How to install the SMW _2.2_?

host> composer.phar require mediawiki/semantic-media-wiki "~2.2" --update-no-dev
./composer.json has been updated
  - Installing mediawiki/semantic-media-wiki (2.3.0)
    Loading from cache

Writing lock file
Generating optimized autoload files

Why "2.3.0"?

StasR (talk)21:00, 28 November 2015

Error on talk pages

Our talk/discussion pages are getting a SMW-related error that I have no clue about:

Catchable fatal error: Argument 2 passed to SMW\MediaWiki\Hooks\ArticleFromTitle::__construct() must implement interface Page, boolean given, called in /home/services/xf/public_html/wiki/extensions/SemanticMediaWiki/src/MediaWiki/Hooks/HookRegistry.php on line 446 and defined in /home/services/xf/public_html/wiki/extensions/SemanticMediaWiki/src/MediaWiki/Hooks/ArticleFromTitle.php on line 39

We're on the following versions:

MW 1.25.1 SMW 2.2.2 Semantic Forms 3.4

Anyone have any helpful insights? As-is, our talk pages are completely unusable.

Aerrin99 (talk)01:33, 17 November 2015

> Anyone have any helpful insights? As-is, our talk pages are completely unusable

Because we expect either a NULL or a page object and not a boolean (true, false) as value according to [0].

Please open an issue with [1] and in the meantime you could try removing the type check [2] (change from "Page &$article = null" to "&$article = null").





MWJames (talk)01:46, 17 November 2015

The phrase, "... in conjunction with many spinoff extensions ..."

Could be, "... in conjunction with many spinoff extensions ...". I'd be bold, but the homepage is blocked for editing. Also, why not stick the survey in what was the SMWCon banner? kthxbi

Dan Bolser (talk)22:58, 3 November 2015

Semantic search in documents (indexing)

Hello everyone,

Recently I've started doing some research about semantic web and this amazing mediawiki. Currently i'm wondering if it's possible to do a full text search on documents such as docx and pdf on my wiki page. That's the reason why I want to make my search engine as smart as possible. For example if I fill in an unknown keyword that my search engine will search in everything like what I stated above such as documents/files on all pages.

Is there such extension or a way already that searches in documents ? I hope someone can help me out with this, because i've been stuck for days, for trying to reinvent the wheel.

PS: these are all educational purposes and it's all for my research.

Tinnie (talk)10:33, 9 October 2015

> Currently i'm wondering if it's possible to do a full text search on documents such as docx and pdf on my wiki page.

If we talk about Semantic MediaWiki then the answer is no.

> Is there such extension or a way already that searches in documents ? I hope someone can help me out with this, because i've been stuck for days, for trying to reinvent the wheel.

Maybe CirrusSearch [0] which underneath uses ElasticSearch can help with file indexing.



MWJames (talk)12:51, 9 October 2015

Thank you for your reply I was actually wondering about this extension

Tinnie (talk)13:42, 9 October 2015

Right, forget about this one maybe it will work (I never used it).

MWJames (talk)13:48, 9 October 2015

I just created Help:Full-text search, it would be of great help if you could extend this page with your research experience about this topic.

MWJames (talk)13:53, 9 October 2015

Of course, will do

Tinnie (talk)14:12, 9 October 2015

apparently does support documented full text search since the engine is based on Lucene's ! Solrstore is outdated btw.

Tinnie (talk)11:22, 19 October 2015

Perhaps, you should think about converting your *.docs and *.pdfs into wikitext.

Alexander Mashintalk05:40, 21 October 2015

Images in Graphviz nodes - which path to use?

I need to create a graph with the Graphviz extension, in which the node is filled with an image. "Image" is used as an attribute in a "node" definition. An example is found here: However, that example does not run on MediaWiki, which has a different way to store images. That could be a problem. According to the extension description at, a restriction states that "Any image attribute values are required to be the names of uploaded files". Okay... but whatever I do, just the filename, or the full link to the file in the images folder, it doesn't work. The system error message is "The dot image attribute must be the name of an uploaded file". Has anyone worked with this and found a solution?

Woudsma (talk)22:23, 20 October 2015

Strange Properties appearing

I've had a persistent problem with a Property I use: "CentralIndexRef" this is usually a reference number eg V51 or X1, it seems fairly straightforward. I use a form to build the data.

Article |CentralIndexRef=G T X W

However I get loads of junk entries appearing

CentralIndeB1Ref (134 uses)
CentralIndeC2Ref (88 uses)
CentralIndeP4Ref (56 uses)
CentralIndeR2Ref (54 uses)
CentralIndeA3Ref (52 uses)
CentralIndeK5Ref (40 uses)
CentralIndeN3Ref (39 uses)
CentralIndeS3Ref (34 uses)
CentralIndeN1Ref (24 uses)
CentralIndeK4Ref (24 uses)
CentralIndeDRef (22 uses)
CentralIndeG T X WRef (21 uses)

Etc, etc. It seems as though it's treating the x in the property title as a variable. I've just wiped and rebuilt all the data as suggested here: Help:Repairing_SMW's_data#Rebuilding_everything, but it doesn't seem to have solved it.

is this a known issue?

Stuarticus (talk)15:24, 16 October 2015

> Etc, etc. It seems as though it's treating the x in the property title as a variable

No, a property label (or title) doesn't make any arbitrary decisions about part of the character set it represents.

I don't fully understand the issue, maybe it would be good if you try the replicate your issue on [0] so we can attempt to eliminate or identify the potential problem.


MWJames (talk)15:34, 16 October 2015

I have seen it to appear in [0] and I suspect that this relates to this code {{#arraymap:{{{CentralIndexRef|}}}|,|y|[[CentralIndexRef::y]]}} in your Template:Article that creates an empty property.

I think if you remove the arraymap call then those arbitrary properties should no longer be created but this isn't really related to smw-core (this parser is provided by SF).

I think the x in CentralIndexRef in combination with arraymap causes this strange appearance, if you would use something else without x the issue might also disappear but again this relates to the use of arraymap and not smw-core.


MWJames (talk)17:31, 16 October 2015

I suspect that entries like CentralIndeB1Ref are empty (when created by the arraymap) and despite being void are still created as property reference hence the visibility in Special:Properties.


MWJames (talk)18:42, 16 October 2015

That makes sense, thanks MWJames. Replaced the variable x with y and rebuilt data and it's all gone.

Stuarticus (talk)12:37, 20 October 2015

Version support

It says here that the latest SMW release is compatible with MW 1.19.0 - 1.24.x. What about MW 1.25?

Jackson667 (talk)09:04, 13 October 2015

Good catch! The whole point of this release was to provide compatibility with MW 1.25. I have just fixed this. More detailed and more up-to-date information on compatibiliy is also provided with the software itself. Have a look at Cheers

[[kgh]] (talk)10:04, 13 October 2015

Creating new content (tables) through other tables

What I have:

Manual created projects (movies) with master data for: Actor, Role, Voice Actor Example:

Actor Role Voice Actor
Actor 1 Role 1 Voice Actor 1
Actor 2 Role 2 Voice Actor 2

What I need:

An automatic generated table on the page of the actor/voice actor with the information:

for the Voice Actor:

Project Role Actor
Project 1 Role 1 Actor 1
Project 2 Role 2 Actor 2

for the Actor:

Project Role Voice Actor
Project 1 Role 1 Voice Actor 1
Project 2 Role 2 Voice Actor 2
Clemonde (talk)07:39, 15 September 2015
Edited by author.
Last edit: 14:40, 15 September 2015

In addition to table lines on the page about a project, your template (I hope you use template for this) should create subobjects: {{#subobject: | Project = {{FULLPAGENAME}} | Role = {{{Role|}}} | Actor = {{{Actor|}}} | Voice actor = {{{Voice actor|}}} }}.

The tables you want will then be produced by queries: {{#ask: [[Voice actor::{{{Voice actor|+}}}]] | ?Project | ?Role | ?Actor | format = table }} and {{#ask: [[Actor::{{{Actor|+}}}]] | ?Project | ?Role | ?Voice actor | format = table }}.

Of course, you will need to create properties Project, Actor, Voice actor of the type Page and Role of the type Text.

Alexander Mashintalk10:07, 15 September 2015
Edited by author.
Last edit: 11:09, 15 September 2015

Thanks for the quick reply,

yes I am using templates for the projects (not for the tables yet since I didnt know how to create n+1 tables as of yesterday since I found this extension)

but it shouldnt be a problem to change the projects.

the template looks like that for now:

|Original Title=
|Dubbing Studio=
|Dialogue Script=
|Dialogue direction=

and then I am adding the tables by hand

{| class="wikitable sortable"
! scope="col"|Actor
! scope="col"|Role 
! scope="col"|Voice Actor
| [[Actor 1 ]]||Role 1||[[Voice Actor 1]]
| [[Actor 2 ]]||Role 2||[[Voice Actor 2]]
Clemonde (talk)10:51, 15 September 2015

Hi Clemonde, Alexander made a mistake, probably by accident. Don't use #set for subobjects but #subobject, which is documented here.

Cavila (talk)11:07, 15 September 2015

Yes, it should be #subobject.

Alexander Mashintalk14:41, 15 September 2015
Edited by author.
Last edit: 22:38, 15 September 2015

You can define template {{role}} like this:

 <tr><td>[[{{{Actor|}}}]]</td><td>{{{Role|}}}</td><td>[[{{{Voice actor|}}}]]{{#subobject: | Project = {{FULLPAGENAME}} | Role = {{{Role|}}} | Actor = {{{Actor|}}} | Voice actor = {{{Voice actor|}}} }}</td></tr>

and call any number of times it on any project page between <table class="sortable wikitable"><thead><tr><th>Actor</th><th>Role</th><th>Voice actor</th></tr></thead><tbody> and </tbody></table>.

These table header and footer can also be wrapped in a template {{roles}}: <table class="sortable wikitable"><thead><tr><th>Actor</th><th>Role</th><th>Voice actor</th></tr></thead><tbody>{{{1|<tr><td colspan="3">put one or more role templates here</td></tr>}}}</tbody></table>.

Or better, create a Lua function that can accept a variable number of arguments.

Alexander Mashintalk14:48, 15 September 2015

thanks guys, I will see if it works and give feedback tomorrow

Clemonde (talk)16:43, 15 September 2015

before I can can even start testing:

maybe I am just too stupid for the basic installation of semantic mediawiki ...

do I need to install composer on my server where the wiki is located or on my local machine?

Maybe I should use the tarball method :D

Clemonde (talk)21:32, 15 September 2015

dear Alexander Mashin, could you show me the {{{role}}} and {{{roles}}} templates with an example in wiki please?

btw the ask function does work perfectly:

{{#ask: [[Actor::{{{Actor|+}}}]] 
| mainlabel=-
| ?Year
| ?Project 
| ?Role 
| ?Voice Actor
| format = sortable 
| sort = Year
| order = desc

btw you can use "nocinclude" to make it look like I did

and is it possible to set a width for the output-table?

Clemonde (talk)22:07, 17 September 2015

I have not created those templates in any wiki. You could just copy the wikitext for them that I wrote in one of my previous replies.

As to table's width, you can use widetable format or set the table width for .smwtable class with site-wide CSS in MediaWiki:Common.css.

Alexander Mashintalk22:24, 17 September 2015

Issues with the "sep" function in mode Query template.

There is a issue since the 2.1 SMW version when we use a "sep" function with the Template format.

Here is the code:

{{#ask: [[Category:City]] [[located in::Germany]]
              | format = template
              | template = Link
              | sep =  • 
              | link = none

Here is the result:

Main PageMain PageMain PageMain PageMain PageMain Page

There should be a separator between the each value. That's not the case obviously. It seems to be a bug.

LIMAFOX76 (talk)16:05, 24 August 2015

`sep` is only used as divider for when multiple values are assigned to same field (property) for querys like:

{{#ask: [[Category:City]] [[located in::Germany]]
 |?Has something --> used by/for sep

The template has to care for the formatting, values do not contain arbitrary separators (except those concatenated of multiple values) that weren't part of its value declaration.

You can make a feature request [0] to have the `sep` parameter made available as {{{sep}}} in a template (so it can be used further within a template).

BTW: I tested it against 1.9.2.


MWJames (talk)17:14, 24 August 2015

Yet it's working on a version 1.8

Here are the link (bottom template):

And now the same template on a 2.1.3 version:

LIMAFOX76 (talk)21:18, 24 August 2015

I replaced |format = template by |format = list living the rest as this and now it's working well. With this, I can change the sep parameter using the template I need.

LIMAFOX76 (talk)10:34, 8 September 2015

Using SMW to query Anchors

Good day:

My Versions: MediaWiki: 1.25.1 | PHP: 5.6.8 | MySQL: 5.6.24 Semantic MediaWiki: 2.2.1 | Lingo: 1.2.0 | Semantic Glossary: 1.1.0

I searched the MediaWiki website for the phrase “Anchor”.

About 13 items down in the Search results I see an entry like the following:

Manual:PAGENAMEE encoding (section Whitespaces in page names and anchors (section headings))

The search returns a particular anchor inside an article.

Is there a way that I can use MSW to mark MediaWiki anchors so that I can get an SMW query to return anchors?

AKSHA (talk)01:54, 29 July 2015

Looks like that you should use subobjects instead of or in addition to anchors.

Alexander Mashintalk03:05, 30 July 2015

Thank you Alexander:

Could you say a little more please? I use subobjects presently. They are very good for precisely querying articles.

Is there a way to arrange a subobject so that a query it returns a section of an article?

Perhaps there is some alternative way to create sections in an article?

AKSHA (talk)12:43, 30 July 2015

I'm not quite sure I understand the issue/question but what if you create a page `ArtitlceWithSection` that contains:

 |Has page=ArticleWithSection
 |Has section=ArticleWithSection#abc
 |Has page=ArticleWithSection
 |Has section=ArticleWithSection#123

{{#ask: [[Has page::+]][[Has section::+]]
 |?Has section

== abc ==

== 123 ==

The query should display and link to the correct section.

MWJames (talk)16:29, 30 July 2015

Good morning:

Honestly; I saw that a search on Wikipedia or MediaWiki could return sections of articles as well as articles. I wanted that precious ring and was told it was accomplished using CirrusSearch. I failed to get CirrusSearch working and got lost trying to follow the detailed configuration advice. Is this because I am using the latest MediaWiki version? Is it because of some configuration I have not done on my wiki? Is it because of subtle CirrusSearch requirements?

The answer to these questions, clearly, was to see if I could have a search of my wiki return article sections by relying solely on SMW.

The solution you provide works neatly and is easy. Thank you Alexander.

I worry that a subobject per anchor adds some overhead per anchor in an article across the wiki. That is to say that it is more work.

In addition to a subobject per anchor; I see that I can shift to a larger number of shorter articles.

Shorter articles will leave me better able to zoom in on a very specific topic without being able to query sections of an article.

Then I will want to mitigate that my articles are become grains of sand on a beach.

I can give each short article a subobject. I can then query to organize related short articles to create a more inclusive article using the Embedded Format.

Sorry to be verbose. Thanks to the forum.

AKSHA (talk)13:43, 7 August 2015

Purge deleted properties

Hello all.

After i create a property with "Special:property" and delete it, whenever i go to "Special:createTemplate" i can still choose it as an element of the template (even if it should no longer exist). I understand that property itself does not longer exist (does not have nothing on it), and that when you use it, you are kind of creating it.

Anyway, i would like that after deleting it, it´s name also dissapeared, as if it had never existed before, so does not show up when you want to create a template.

How could i do this?


Maiser (talk)15:05, 23 March 2015

My Versions: MediaWiki: 1.25.1 | PHP: 5.6.8 | MySQL: 5.6.24 Semantic MediaWiki: 2.2.1

If you have articles that use the deleted property; you will continue to see the deleted property among existing properties. Cleaning up articles to remove references to the deleted property can help.

I have also seen improvement by using maintenance scripts.

Deleting Unused Content[edit]


This deletes old revisions from the database.

php deleteOldRevisions.php --delete


This deletes deleted pages from the database.

php deleteArchivedRevisions.php --delete

Hurrying Jobs[edit]

The folowing speeds up pending jobs.


It is demanding and can freeze the server, so I don't do it.

The following is less demanding and does not freeze the server.

php runJobs.php --maxjobs 1000

I run this from an XAMPP cmd window of the Maintenance directory. It runs pretty fast. It does not remove phantom properties by itself.

You may may have already done enough to remove the phantom property and just be waiting for the job that eliminates references to it. In that case this will help.

AKSHA (talk)01:47, 29 July 2015

Album-to-song and tracklists relationships

Hi. First of all, thanks for SMW, a great software solution. I've just discovered it recently, and it looks really cool. I'm a long-time MediaWiki user and maintain a public music band wiki. I'm going to start a new project and now I would like to introduce SMW to avoid the existing wiki problems. I have a local playground where I do my SMW experiments, and I'm wondering if it's possible to make an album tracklist solution (one-to-many). Let's say, there is an album titled ALBUM and it contains the following template invocation:


The Tracklist template is as follows:

{{#fornumargs: I
| V
| {{#set:
  |Index={{#var: I}}
  |Song={{#var: V}}

It produces:


And when, by my intention, I'm trying to query a tracklist for the album, I get a grouped result unfortunately (as far as I understand, this is how SMW works):

{{#ask: [[Type::tracklist]]

turns into a one-row table (format=ol produces a single line list) because of grouping:

|         | Collection | Version | Index | Song   |
|         |            |         | 1     | SONG 1 |
|         |            |         +-------+--------+
| ALBUM   | ALBUM      |         | 2     | SONG 2 |
|         |            |         +-------+--------+
|         |            |         | 3     | SONG 3 |
|         |            |         +-------+--------+
|         |            |         | 4     | SONG 4 |

After all, the whole ALBUM just got 4 properties, and this is why the result is grouped. I would like to "ungroup" it as if it's a SQL-like query without a GROUP BY clause. The only solution I see is spreading the tracklist information onto each of 4 song pages, like {{#set|Type=tracklist|Collection=ALBUM|Version=|Index=1|Song=SONG1}} thus associating the tracklist album/index with a particular song, not the album itself where I'd expect to store the actual tracklist I used to do in my existing non-SMW wiki. This may look unusual, odd and violationg the SMW principles. Sorry for probably a vague explanation.

My question is as follows: what would you suggest to "ungroup" the result? Does my SQL-like idea violate the SMW principles? Any comments are appreciated. Thanks!

Halo (talk)00:34, 25 June 2015

To build a one-to-many relationship for a subject (e.g. Album entity) it would be best to use the #subobject instead of #set.

 |Index={{#var: I}}
 |Song={{#var: V}}
{{#ask: [[Collection::{{FULLPAGENAME}}]]

See also Examples/Queries/Subobject to display table rows

> music band wiki. I'm going to start a new project and now

You may want to look at [0] to get some ideas about a music related wiki that uses SMW.


MWJames (talk)19:38, 25 June 2015

This is interesting. I'm currently testing it, and it seems to be what I want. Thank you!

Halo (talk)10:08, 28 June 2015

One more question, please. Is it possible to refer the properties defined at the "sub/child"-pages? I would like to extend the above template/table output with the "Length" column so it could look like a real tracklist. The ?Song property refers to song pages, and every song page has a song definition with the Length property set. It's like the INNER JOIN operation, but I feel like I'm abusing SMW capabilities (and it looks like I'm more of finding a search mechanism like XPath). Is it possible somehow?

Halo (talk)20:16, 28 June 2015

In case you go with the #subobject then your data model will most likely be something like:

  • An ALBUM is represented by a wikipage ->
  • Subobjects are embedded in a page to represent each individual song ->
  • Each song has attributes like:
    • Song title
    • Song index
    • Song length
    • Song author/composer/writer (optional in case it is a compilation where a song can have different writers from the Album)
    • etc.

As demonstrated you attach attributes/properties to an individual song which a #subobject not a page (we are talking about an entity)

If you want to split an ALBUM/SONG by page/subpage then you can take a similar approach only that subobjects need to contain a reference to the album.

For example, looking for an album of song writer YYY where you want to see songs with title and length -> [[Has song writer::YYY]]|?Song title|?Song length.

MWJames (talk)15:02, 7 July 2015

It sounds promising. I'll try your suggestion as soon as possible. Thank you very much!

Halo (talk)18:59, 13 July 2015

The task for SMW or not?

I need to solve the following problem: there are several thousands of pages, and each page contains a variety of unique labels (up to several dozen). These labels are unique globally and I need be able to find the page on the label. It is clear that, in theory, this problem can be solved by standard Mediawiki redirects, but they are difficult to automatically create (or remove when modifying pages).

Question: how far is it appropriate to solve this task by means of SMW?

StasR (talk)09:17, 5 July 2015

What is a "label", how is it defined in the wikitext, and how do you ensure that it's globally unique?

Yaron Koren (talk)00:10, 6 July 2015

There are partial dumps of external database, these labels - unique keys in the database. I will convert the dump to xml for import into wiki, so I can include labels into the body of tag pages in any form. When parsing I can resolve internal links within a single partial dump, but links to other parts (already included in the wiki, or included in the future) should be linked by means of mw / smw / something else.

StasR (talk)09:17, 6 July 2015

Alright. What's a "tag page", and what does it mean to resolve an internal link?

Yaron Koren (talk)20:54, 6 July 2015

If the page refers to labels that have been defined on another page of the same partial dump, then I convert it into a normal Wiki link when I convert the dump to XML.

StasR (talk)21:39, 6 July 2015

I don't know, I still don't really understand the question. Hopefully someone else can help you.

Yaron Koren (talk)21:18, 8 July 2015

I may confer with the previous commenter not being able to see the full extend of what you want to achieve but for what it's worth maybe the following datamodel can help.

Have your labels that point (from the origin subject) to (or from) the source being collected as part of a subobject like:

Page "SomeSubject" that relates to:

 |Has label=One,Two,Three,...|+sep=,

With above statement you should be able the search for labels that point to the subject that contain those labels without having to create any redirects.

{{#ask: [[Has label::~*Two*]] }}

If the search of a subject that contain some of those labels (with "Has label" being of either "Page" or "Text" type) is not your primary objective then you need to clarify the intention of your DM.

MWJames (talk)07:50, 9 July 2015

Semantic Forms: Forminput with Multiple Rows

Hey, like I wrote above, I would like to create a forminput multiple input fields. I want to do that because our workers always mess up the form Name and put in to many spaces or delete the commas. I hope you understand what I mean, if not I try to explain it better with this:

Currently our Forminput looks like this

{{#forminput:Installation|70|Installation: Ort,Projektname,Rechner1}}

and after that comes the rest of the form.

Now this is only one input row, and I want three input rows where each contains a part of the title.




If it stays like this our workers keep messing up the title names and sometimes the names are full of underlines.

Sorry for my bad english, if there is something not clear I try my best to edit it.

Arty (talk)07:10, 15 June 2015

Have a look at the one step process. So the form should have something like {{{info|page name=Installation: <Installation[Ort]> <Installation[Projektname]> <Installation[Rechner]>|add title=Installation erfassen|edit title=Installation bearbeiten}}}. The best and fastest entry point to help regarding Semantic Forms is this talk page. Cheers

[[kgh]] (talk)19:20, 15 June 2015

Okay thanks for helping me, but somehow this won't work for me

When i try the info tag it only prints the stuff thats in the first "bracket" like I put in your code and it only prints "page name=Installation: <Installation[Ort]> <Installation[Projektname]> <Installation[Rechner]>"

Then when you put other things in the first place it for examples prints "add title=Installation erfassen"

Maybe I'm just overlooking something but it would be nice if you could also help me out with this problem

Arty (talk)07:05, 17 June 2015

> Maybe I'm just overlooking something but it would be nice if you could also help me out with this problem

Unfortunately this forum is mostly concerned with SMW-core questions and #forminput is a specific SF question (and is not related to SMW) therefore it would be best to ask the maintainer [0] directly.


MWJames (talk)14:31, 17 June 2015

fresh install and semantic bundle question

Hi, I want to make a fresh install from source on a redhat 6 64 bit system. Is the order of things to get a working mediawiki, then add the semantic mediawiki extensions? What is the advantage of the bundle? I read the docs but am not clear on what exactly it is and if that would be the best bet for a fresh install. If I install the bundle does it install the extension too? I am assuming with either approach I need to have a working recent (i.e. not rhel6 repo) mediawiki in first. Is that correct? Sorry for such basic questions, but I want to avoid installing the wrong way.

I am particularly excited by the inline query abilities. is SMW the only platform that offers this? Everything else I looked at is only able to query and return rdf in big chunks like tables and we have several projects that could really use the inline query method to good advantage.

Thanks for answering n00b question!

Rcrath (talk)03:16, 13 May 2015

> I read the docs but am not clear on what exactly it is and if that would be the best bet for a fresh install.

Have a look at the video [0] which should give a clear picture of how a fresh install can be achieved. For details on the specific installation requirements, see the Installation help.

> mediawiki in first. Is that correct?

MediaWiki first, SMW comes second as it requires MW to be working.

> What is the advantage of the bundle?

If you talk about the SemanticBundle, not much and it only supports SMW 1.9.2 which is no longer under active maintenance. The current SMW release is 2.2.

If you want install SMW related extensions such as SRF (see [1]) or SM just follow the specific installation guideline of that extension you want to install.

The following list contains details about SMW extensions available via Composer.

If you can`t use Composer, see the tarball installation guideline.

> Sorry for such basic questions

You might also have a look at Help:Getting started.




MWJames (talk)02:47, 14 May 2015

@MWJames, thanks, I'll watch the videos. I didn't pay attention to videos because I am impatient and like documents, so mea culpa and thanks for the pointer. I can use composer and thanks for answering my query re: the bundle.

Rcrath (talk)06:21, 28 May 2015

Problems uploading and deleting files


i have enable file upload with $wgEnableUploads=true; in the LocalSettingsp.php, but i am having some problems.

Each time i try to download a file, i will get a screen which says:

Fatal error: Call to a member function mapDataItemToElement() on a non-object in /home/u480878357/public_html/mediawiki/extensions/SemanticMediaWiki/includes/export/SMW_Exporter.php on line 594

That line stands for this peace of code:

static public function getDataItemExpElement( SMWDataItem $dataItem ) { return self::$dataItemToElementEncoder->mapDataItemToElement( $dataItem ); }

Anyway, even if i get that error, file gets uploaded to the repository.

Afterwards, when i go to repository and i try to delete that file i get:

Fatal error: Call to a member function mapDataItemToElement() on a non-object in /home/u480878357/public_html/mediawiki/extensions/SemanticMediaWiki/includes/export/SMW_Exporter.php on line 594

Exactly the same error, but this time the file will not be deleted.

What is causing this and how could i solve it?

Atm i am installing the semantic media wiki on a free host (hostinger), which uses linux's Centos 5.5 distribution i believe, do not know if that has an influence.

Maiser (talk)12:52, 27 May 2015

> Fatal error: Call to a member function mapDataItemToElement() on a non-object in /home/u480878357/public_html/mediawiki/extensions/SemanticMediaWiki/includes/export/SMW_Exporter.php on line 594

This error can virtually not happen because each call in SMW is using `Exporter::getInstance()->getDataItemExpElement` and there should be not one single caller that is executing `Exporter::getDataItemExpElement` directly therefore I cannot tell as to what happens on your installation. Furthermore, the upload is tested against SQLStore and SPARQLStore with a real upload process [0].

Having the complete stack trace would help in guessing where `Exporter::getDataItemExpElement` is called from.


MWJames (talk)13:29, 27 May 2015

Ok, problem was definitively coming from:

which was calling that function. Going to try to solve it by making a clean instalation of it again (to see if i made an error, even if i know pretty much for sure that it sometimes randomly fails, from previous local instalations) and if that does not the thing, i will go for the complete stack trace.

Many thanks.

Maiser (talk)13:45, 27 May 2015

> Ok, problem was definitively coming from:

The `Exporter` should always be called using `Exporter::getInstance()->...`.

MWJames (talk)13:50, 27 May 2015

Making URL look better


is there any way making an URL look better?

for example if i have a link to an image of a galaxy:

And i want the link just to say "galaxy" but making it able to access the image in one click, how would i do it?



Here is the link, should have looked it first at media wiki, kind of out of topic here lol, did not thought about it. Still there is no way to delete this post so i will just give the answer:

Maiser (talk)20:17, 21 May 2015

Translating categories


i hope there is a simple way of doing this! I have just imported some vocabulary from DublinCore ontology and of course, it is all in english. This vocabulary is located in "categories" and "properties". I want that instead of displaying it in english, whenever a user changes the language of the wiki, these vocabulary shows up in that language.

Perhaps there is some label of type [[lang:(language)->show.....]] r something like this.

Could someone help me with this?

Maiser (talk)13:48, 2 April 2015

Sounds impossible.

Alexander Mashintalk03:03, 3 April 2015

Just contact me via one of my social links and I'll give you support for this issue.

WolfgangFahl (talk)00:57, 11 May 2015

Any way to create a bunch of pages without having to make clicks for each insertion?


Is there any way to do this? For example if i want to introduce 10 different pages (each one with it´s own name). Perhaps a directory in where you can introduce pages information directly, or an extension which makes available to introduce more than one page in a click (dividing one perhaps, which an speficic syntax).

Maiser (talk)15:37, 17 April 2015

Ok, seems like "Data transfer" extensions is pretty easy to manage. Just modify XML type data manually and make and import will create all pages we have defined.

Maiser (talk)19:49, 17 April 2015

The smartMediaWiki approach helps creating pages dynamically. See my talks at SMW Con Spring 2015

WolfgangFahl (talk)00:56, 11 May 2015

How to hide the "Previsualization message"

I want to add some pre-made questions, were user just have to feel a box , make a click, and obtain the answer.

In order to do this i used semantic forms+templates, so that if for example i want to ask "Which are the contributions of a particular user (articles, links, extensions.... basically all in were user is tagged, can be accessed in a organized way just by putting his name in a box and clickig.

For this i converted the "preview" button, in something which takes the value of the box and launches the inline query (#ask) from the template without saving it as a page, obviously.

Problem is that upwards i get this message telling me that "this is a previsualization message....." which i want to get rid of.

Any way to do this?

Maiser (talk)16:32, 7 May 2015

That's not really a question related to this website. ;) I guess you just have to blanc the respective system message in the MediaWiki namespace. Cheers

[[kgh]] (talk)16:56, 7 May 2015
First page
First page
Previous page
Previous page
Last page
Last page