Add tag {'qlwiki'} in article text (of course without '; if I did it here the tag wouldn't be displayed;-). Via url parameter you can connect to a wiki; e. g.: {'qlwiki url='}. If you use a local, private wiki; enter the url in {'qlwiki'} tag or simply use the default settings of plugin in backend. Separate one attribute from the other via the separator -_-

  • some wiki (that has entry 'Joomla') set in params :{'qlwiki title="Joomla"}
  • Wikipedia: {'qlwiki url=""}
  • Wikipedia: {'qlwiki url="" edit="0" action="render"}
  • {'qlwiki url="" edit="0"}
  • url - e. g. for wikipedia - or for a local wiki as well like https://wiki.local?title=Joomla or http://wiki.local/Joomla
  • action - e. g. 'render', I can't imagine a case when to set action not to render; but just in case you need it set
  • title - for local wiki to get entry intended; ! replace blank space ' ' by underscore '_' !
  • login - set yes for your local, private wiki if locked behind a login
  • user - e. g. 'wikiuser', for local, private wiki locked behind a login
  • password - e. g. 'yourPassword$!??', for local, private wiki locked behind a login
  • useragent - string
  • edit - e. g.
    • 0=never;
    • 1=always;
    • 2 = only Super Administrators
  • cut - 0 für nicht beschneide; 1-10000 etc für auf angegebene Zahl an Zeichen zuschneiden
  • to - 0 all; 1 Show introtext (no directory); 2 Show introtext AND directory; 3Show only first image
  • hideImages - 0 no; 1 yes
  • when connecting via curl, mind to allow curl_exec on server
  • mind the protocol on the url: make sure you use https or http according to wiki url

To show only extracts of a wiki article, you have to use the wiki api - and that makes things sophisticated thanks to the params. I decided just to give you some examples:

Pluging params might name the wiki api, then you font have to mention it on everr single tag:

Tag within article

  • {'qlwiki query="action=parse&section=0&prosp=text&page=termoli&format=json&formatversion=2"}
  • Important is the "section=0" stuff; herer you can choose which section you would like to display; it starts counting on '0', so if you want to display the 3rd section it would be section=2.

You can override (for another api) in every call - they produce the same result.

  • {'qlwiki  url=""} OR
  • {'qlwiki  url="" query="action=query&prop=extracts&format=json&exintro=&titles=Termoli"}

Further examples:

  • {'qlwiki  url="!"}
  • {'qlwiki  url="" query="action=query&prop=extracts&format=json&exintro=&titles=Joomla!"}
  • {'qlwiki  url="" query="action=query&prop=extracts&format=json&exintro=&titles=Joomla!"}
  • {'qlwiki url="!&formatversion=2"}
  • {'qlwiki url="!"}

I am not yet happy with the sophisticated handling, its due to the wiki aps which seems to have somehow evolved/grown into what it is now, without a real planning. But we can be very happy, that there is one at all:-)