Upcoming Elxis 5.6 information

[datahell]

Page generators in Elxis 5.6

A feature that will be available in upcoming Elxis 5.6 are the Page Generators. A Page generator is a custom block of code that generates the HTML of the page instead of the built-in component (actually the HTML of component's viewer). This allows us to achieve 100% customization of the pages layout and style. Page Generators are optional parts of a template. For now, page generators are available in component Content for:

• Category pages
• Articles
• Tags page
• Archive page

On each category/article you can select (or not) a page generator (if available on your template). Category "A"may have a totally different style of category "B", while category "C" might have the Elxis default style.

If you have a template named "supercool" Page Generators should be added here: templates/supercool/generators/
Page generators are php files and have special naming depending on their type. For instance page generators for categories must start with "category_". For articles with "article_" and for tags and archive the name is standard (content_tags and content_archive respectively).

Here are sample generators for template "supercool".

templates/supercool/generators/category_Blog.php
templates/supercool/generators/category_Blog2.php
templates/supercool/generators/category_List.php
templates/supercool/generators/article_presentation.php
templates/supercool/generators/article_tourism.php
templates/supercool/generators/content_tags.php
templates/supercool/generators/content_archive.php

When you edit a category you can select as generator: Component Content (Elxis default), Blog, Blog2 or List. If you change the template and the selected generator does not exist in the new template the page will be generated by component Content (fallback process).

More information after the release of Elxis 5.6

[michalis1984]

wow wow wowww  waiting for this datahell  customization at top level

[seadhna]

Sounds great!

[datahell]

New passwords policy

Elxis 5.6 has a more strict user's password policy. This is done in order to meet highest security standards. If you perform an update from a previous version then the policy will apply to new created user accounts, not to the existing ones. However, if you go to change your password then the new password must meet the new password policy.

A password, in order to be accepted must:

• Have a minimum length of 12 characters
• Have at least 2 lowercase characters
• Have at least 2 uppercase characters
• Have at least 2 digits
• Have at least 2 symbols

This password is invalid (it contains only 1 symbol):
4RTrd57@E1o0p

This password is invalid (it has a length of 9 characters):
4RTr@a6!d

This password is valid:
4RTr@a6!dD34

[datahell]

Finally, Elxis password policy became a configuration option including password complexity (normal/high) and expiration.

Available options:
Normal - Never expires
Normal - Expires in 3 months
Normal - Expires in 6 months
Normal - Expires in 12 months
High - Never expires
High - Expires in 3 months
High - Expires in 6 months
High - Expires in 12 months

Elxis 5.6 focuses a lot on strengthen security in order to meet highest security standards.

[seadhna]

Elxis 5.6 request: Not sure if this is possible, but it would be useful to be able to give a module an ID in parameters, similar to how we can already apply classes.
e.g. for pages with internal anchor links, to enable internal navigation via anchor link to a module that appears on the page.

[datahell]

Done. All modules in Elxis 5.6 have now an ID declared in their wrapper DIV element.
Example:
<div class="module" id="moduleX">
...
</div>

Where X is the module ID. So you can create links like href="#module14"

Attention: If you include the same module twice in the same page (eg in 2 module positions) you will end with duplicated IDs in the same page which is an HTML error.