Help talk:Embedded format/Archive


The claim that "SMW will take care that embedded articles do not import their semantic annotations, so these need not be treated specifically" seems to now be true as of SMW (in my experience, it was not the case with previous versions of SMW that I have used, <= 1.5.2).

However, it should be noted that properties set with {{#set:}}et al. will get upwardly transcluded unless they are specifically wrapped in <noinclude> tags. Please do not change that behavior, though, I think this is excellent! It allows certain properties to be upwardly transcluded (which in some rare cases is quite desirable), but defaults to not doing that. Clear and thoughtful reasons this should NOT happen appear here --Alex 19:51, 9 February 2011 (CET)


The above behavior has been reported and acknowledged as a bug, not a feature. Therefore, for the time being, you must either wrap your {{#set functions in noinclude tags or mark them as silent annotations, e.g., [[Property::value| ]] --Alex 19:30, 10 February 2011 (CET)

unwanted category from transcluded template[edit]

Let's say PAGE A uses a template (TEMPLATE A) with named parameters to create the contents of the page, as is customary for most SMW wiki's. Let's say TEMPLATE A has the category definition (CATEGORY A's). If PAGE B contains an SMW query with the embedded result format, CATEGORY A's will be transcluded into PAGE B and PAGE B will now be a part of CATEGORY A's.

How can this be avoided (without manually defining categories per page)?


This is a very useful output format, but I just noticed one limitation to its use. If this format is selected in a query enabled by Semantic Forms (and quite possibly in regular inline queries, too), the embedded page may exclude some or all of its inline queries (=queries which are part of the source page). Cavila 12:17, 18 November 2011 (CET)

Heiya Cavila, thanks for pointing this out to us. I will have this checked. Perhaps its a bug or it is not possible (=limitation) Cheers --[[kgh]] 23:37, 18 November 2011 (CET)
Just for the sake of completeness (in 2011 I added a note to the documentation but never responded here), this is a limitation that is due to the specific functionality of the magic word PAGENAME (which no longer refers to the intended page once it is embedded somewhere else). Since many users enable queries (of the type {{#ask: [[Some property::{{PAGENAME}}]] }}) through the use of templates, it seems to be a fairly significant limitation. Will this ever be fixed? Cavila (talk) 12:54, 20 November 2013 (CET)
There are no threads on this page yet.