Tips & Trix Blog
2012-06-28, 18:22 by Jonas Wallden in RXML/XSLT
One little-known feature of Roxen CMS is that component-based pages can include components declared entirely in XML/XSLT without the need for a corresponding Pike module. This is ideal for parameters or settings that non-programmers should have easy access to.
The idea is that you place these components on an internal page that can be seen in the Insite Editor environment but that is hidden from external visitors, e.g. using the External Visibility property. The page can then be modified and published using familiar actions.
You will need Roxen CMS 5.0.443 or newer to find the necessary module, though older versions should run it just fine if you copy the Pike module.
Check it out:
2008-10-21, 16:00 by Tobias Liin in RXML/XSLT
As a web developer working with Roxen, you often need to make components render in different columns on the site, which may seem difficult since there is no column concept in the component editor. You may also want page layouts to vary from page to page, on one page you might want to use the full width of the page to render the content, but on another page you want two columns where the content column is a bit smaller to make room for a right column. There are many different ways to accomplish this, and the best way to do it depends on the requirements.
One way to do it, that I like personally, is to use pre-defined variant intervals. This will allow the page layout to vary automatically with the type of component inserted on the page, without having to treat each component specifically or make any modifications to the main XSL code when adding new components.
Lets say you have a site with two different possible layouts, one or two columns. Some components are supposed to be used in any of the columns, some only in the left and some only in the right column. So you specify variant intervals:
- variant 0-99: renders in left column
- variant 100-199: renders in right column
- variant >= 200: not supported (open for future changes)
2008-09-19, 15:29 by Erik Dahl in RXML/XSLT
How it works:
- Verfies the email adress according to string patterns. Valid email string patterns could be of this format and probably many more:
- Erik Dahl <firstname.lastname@example.org>
- Erik Dahl <"email@example.com">
- Verifies that the domain part of the email address has a MX record - meaning that the <vinput type="email"/> does a domain name look-up.
- Domain name look-up can be disabled in the tag using the disable-domain-check="yes" attribute in the <vinput/> tag.
<vinput type="email" name="email" id="e_mail">
* Incorrect email address
<span style="color: green;">OK</span>