plg_qlmodule enables you to call any published module you generates and display it in your article. Menu assignments have not to be set anymore.

qlform module is called via command {'qlmodule id=88} (of course without '). The module has been generates via Extensions>Modules etc.

By the way. Thus you can call any module by its id.

{qlmodule id=88}

qlform module is called via command {'qlmodule id=88}recipient=mareike.riegel@ql.de{'/qlmodule} (of course without '). This module - a mod_qlform - has been generated via Extensions>Modules etc.

The text within the tags ("recipient=mareike.riegel@ql.de~~email@halbfrau.de") override module params. As the mod_qlform separates the e-mail addresses via linebreak, I added the two tildes (~~); they will be replaced by a common linebreak (\n).

Standard fields
Calendar stuff
Editor? Yepp!
J! stuff
... and captcha - J! captcha pulgins available
qlform generator by ql.de

 

qlform module is called via command {'qlmodule id=102}user=978,showForm=1{'/qlmodule} (of course without '). The module (#102) is a mod_qlcontact module and has been generated via Extensions>Modules etc.

The text within the tags ("user=978,showForm=1") override module params. It's not yet fully tested and surely limited (e. g. concerning params with multiple select boxes); but it's a start.

Position
Boss No. 3

mod_qlcontact

This is a demo of mod_qlcontact. It shows

  • data of a contact chosen, e. g. name, address, telephone, e-mail, image etc.
  • text (the very one you red here)
  • contact form sending e-mail to contact e-mail address
  • link to contact

If there is no contact selected, it displays the data of the user (and his contact data if provided) that has created the currently displayed article.

Contact form

Name
E-Mail
Betreff
Nachricht

 

qlform module is called via command {'qlmodule id=103}{'/qlmodule} (of course without '). The module (#103) is the core module mod_articles_latest. It has been generated via Extensions>Modules etc.

The text within the tags of the second command ("count=3") override module params.

mod_articles_latest {'qlmodule id=103}{'/qlmodule}

mod articles_latest {'qlmodule id=103}count=3{'/qlmodule}

 

{'qlmodule qlmoduleId="HERE_YOUR_MODULE_ID" /} into the article. The module with that very id will be loaded into article.

Setting params:

  • Module params can be set within the tags, e. g. {'qlmodule qlmoduleId="123" user="2" query="SELECT * FROM #__something" /}.
  • In case a module param asks for a linebreak, set a double tilde (~~).
  • If you need a json within param, use param="JSON['first','second']"
  • add alternating variables {qlmodule qlmoduleId="HERE_YOUR_MODULE_ID" codeParams="{'numContactId':'13','strClass':'one_third'}" /}; codeParams can be caught by "$codeParams"

As params can be set - though limitedly - for different callings. E. g. so you need only 1 generated module for 5 callings, just set params within tag.

Examples:

  • 1
  • Module width id 127, a gallery module, created as a basic scheme;
  • basic setting in module itself
  • overrides (herer path to folder) in actual call by qlmodule plugin: {'qlmodule qlmoduleId="127" codeParams="{'image_folder':'images/_ql_sample/gallery'}" /}