Difference between revisions of "Content management"
Lorena Ruiz (talk | contribs) |
Lorena Ruiz (talk | contribs) |
||
Line 2: | Line 2: | ||
− | Content | + | ==Content Management application== |
+ | Create content based portals. | ||
+ | |||
+ | |||
use "<nowiki><!--VP-->"</nowiki> directive for content required to be processed by variable processor. | use "<nowiki><!--VP-->"</nowiki> directive for content required to be processed by variable processor. | ||
Line 8: | Line 11: | ||
[#ssupdate @session.expire@#] - expire a session, usually embedded in a logout page | [#ssupdate @session.expire@#] - expire a session, usually embedded in a logout page | ||
+ | |||
+ | |||
+ | ==Websites== | ||
+ | Allows the creation of custom login pages. This allows you to create multiple custom login pages for various groups of users within the same system. | ||
+ | |||
Revision as of 17:06, 27 November 2014
Content Management application
Create content based portals.
use "<!--VP-->" directive for content required to be processed by variable processor.
[#ssupdate @session.expire@#] - expire a session, usually embedded in a logout page
Websites
Allows the creation of custom login pages. This allows you to create multiple custom login pages for various groups of users within the same system.
Virtual Alias
Within Websites you have the option to configure a Virtual Alias. This virtual alias allows your to mask the instance URL and will only function when used in combination with the virtual folder.
Ex. company.smartsimple.us/welcome/gms/ = subcompany.smartsimple.us/welcome/gms/
When configuring this for the first time, you must append ?u=1 to the end of the URL to activate.
Ex. subcompany.smartsimple.us/welcome/gms/?u=1