Differences

This shows you the differences between two versions of the page.

--- admin_menu:page_modules:start [2010/05/13 17:12]
james
+++ admin_menu:page_modules:start [2014/09/25 16:55] (current)
@@ Line 12: / Line 12: @@
 There used to be HTML modules within versions earlier than v5.  Within the v5 implementation of the Smarty template system you can create as many templates and sub-templates to use in those page templates as you want.  Within the default v5 design the head.tpl template just such a sub-template.   You can reference these sub-template within other templates by simply using Smarty terminology to include the template files where you need them.  This is how you should include those template files in other templates:
-  {external file='sometemplatefile.tpl'}
+<code html>{include file='sometemplatefile.tpl'}</code>
-===== Deprecation of PHP Modules in v5 =====
-There also used to be php modules within the Enterprise edition of our software.  This allowed you to include php code within the design where ever you placed these php modules within page template.  With the use of the Smarty template system within v5 php modules were no longer needed.  You now just need to insert the php you want to place in a template exactly where you want it to appear but between two Smarty template tags for that purpose to make sure it is properly recognized and executed.  This is the form you should take:
-<php>
+To show text only if a user is logged in or not logged in, you can use the following in any template:
-{php}
-echo "hello world<br>\n";
-{/php}
-</php>
-Page modules run independently of the {body_html} tag and have their own settings within each modules administration page.  Each administration tool contains settings that pertain to and control the functionality of that specific module.  These admin settings are independent of the "Site Setup" settings typically associated with the {body_html} tag. To access each page module’s individual settings, click the "edit" button for that page module within the PAGE MODULES admin tool. If applicable, there will be text with each module for you to edit.
+<code html>
+{if not $logged_in}
+	You are NOT Logged in!
+{else}
+	Welcome!  You are logged in!
+{/if}
+</code>
 ===== Module Attachments =====
 Within each modules admin tool page you will see a section at the bottom of the page that contains all of the page templates that specific modules placement tag is found.  So if you make changes to the configuration settings for that module you can immediately see which templates will be affected by that change.  You can even go directly to the edit page for that page template by clicking the "edit template" button to the right of that template.
+<tip c n>Note that page to module attachment is automatically done by the software.  But this only applies when you make template edits directly through the admin tool.  If you make changes to templates outside the software's admin tool you will occasionally need to click the **Re-Scan Attachments** button in the following admin tool for the template you are editing so that the software will re-scan that template set for module and addon placement tags.
+DESIGN > TEMPLATE SETS
+</tip>
 ===== Page Module Font Controls =====
-Page module fonts, like other fonts in the system, are controlled by css documents within the system.  Most of those css controls will be included in the site wide/template set wide css document.  Some modules have their own css files and these will be included in the <head> of the page if the {header_html} tag is placed properly in the <head> </head> section of that html.  To see if the page module you are using has it's own css document you can view the html source code for a client side page containing that module.  Within the <head> of that page you will see all the css documents included for the functionality/modules within the templates used on that page.  If there is a css document for a module you will see that it has the same document name as that of the module itself.  You will be able to see where that css file is within the template system and can then edit that file in the DESIGN > MANAGER admin tool.
+Page module fonts, like other fonts in the system, are controlled by css documents within the system.  Most of those css controls will be included in the site wide/template set wide css document.  Some modules have their own css files and these will be included in the <head> of the page if the {header_html} tag is placed properly in the <head> </head> section of that html.  To see if the page module you are using has its own css document you can view the html source code for a client side page containing that module.  Within the <head> of that page you will see all the css documents included for the functionality/modules within the templates used on that page.  If there is a css document for a module you will see that it has the same document name as that of the module itself.  You will be able to see where that css file is within the template system and can then edit that file in the DESIGN > MANAGER admin tool.

Geodesic Solutions Community Wiki

User Tools

Site Tools

Differences

Page Tools