Site:Frontend:Modules
From Metrixstream
(Difference between revisions)
MetrixJustin (Talk | contribs) |
MetrixJustin (Talk | contribs) |
||
| Line 18: | Line 18: | ||
</html> | </html> | ||
| + | == Accessing Module Pages == | ||
| + | Since modules are injected into a parent page, pages within a module need to be called with the mpage URL parameter. | ||
| − | + | For example, if your parent page is "auth" and your module page is "login": | |
| − | == | + | http://example.com/?page=auth&mpage=login |
| − | + | ||
| − | + | ||
Revision as of 12:08, 15 June 2012
Introduction
Modules contain stand-alone code, files, pages, and page includes required to perform the tasks of the module.
Module Integration
After a module is created or imported, it will be listed under Module Integration while editing a site page.
Selecting the module will populate MS.module.data with the contents of the module. Calling MS.module.data on the page will inject the contents onto the page.
<html>
<head>
<title>Module Test</title>
</head>
<body>
<?cs var:MS.module.data ?>
</body>
</html>
Accessing Module Pages
Since modules are injected into a parent page, pages within a module need to be called with the mpage URL parameter.
For example, if your parent page is "auth" and your module page is "login":
http://example.com/?page=auth&mpage=login
