https://bugzilla.wikimedia.org/show_bug.cgi?id=21273


Markus Krötzsch <mar...@semantic-mediawiki.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |LATER




--- Comment #1 from Markus Krötzsch <mar...@semantic-mediawiki.org>  2009-10-25 
21:40:55 UTC ---
Due to the architecture of MediaWiki and SMW, it is not possible to distinguish
between transcluded and directly inserted texts at the time when SMW properties
are collected during the processing of a page. I think this would be very hard
to change.

Various other options are possible, however:
* You can generally disable SMW data for some namespace (as already done for
templates). The relevant configuration option is explained at
[http://semantic-mediawiki.org/wiki/Help:Configuration#smwgNamespacesWithSemanticLinks].
* You can construct a parser function "#if" that checks the current namespace
(there is also a parser function for obtaining it) and that controls whether or
not SMW annotations are set based on this information. The disadvantage is a
higher number of parser function calls which could hurt performance. If this is
not an issue, then yuo could even wrap this intelligence into a template that
takes an SMW property name and a value, and that is used instead of SMW syntax
in all templates. But large numbers of nested template calls can really be a
performance issue.
* Maybe you can use SMW's format=embed with #ask to make the lists at foobar
automatically instead of creating them manually? This format takes care of
preventing transclusion of properties (it uses a hack right now, but it does
the job, and future versions are very likely to still solve the issue, maybe
without the hack).
* You can also use the hack directly: put [[SMW::off]] ... [[SMW::on]] around
any piece of wiki text for which SMW links should be ignored. As I said, this
is an undocumented hack, and it will go away without notice or regret as soon
as we have time for building a better solution.

I hope that some of the above will be of some use to you. We will not do
anything else about the issue for now, as I have no idea how to implement a
special handling for transcluded code in a clean way (if this is possible at
all).


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to