1. 8.12 release Notes

2. Previous release Latest release Release 9th June 2008 11 betas
72 tickets

3. CAPTCHA Option in forms configuration under field type
Prevent automatic (program based) submission of forms.
Separate style: Span class ‘formCaptcha’
Example:

4. RSS Categorisation
Support for multiple categorisation, separated by commas
These are available for filtering in the IE7 RSS view
Support for filtering by categorisation in the address bar
e.g. both of the above can be used in data islands and XML consumer pages
Examples on

5. CSS inheritance
It’s now possible to inherit from other Sitekit CSS’s via the standard CSS syntax of <sitekit CSS template name>”
Works best if the template name doesn’t have spaces so ‘_’ or ‘-’ are best
Can also be used to reference CSS’s stored in the file library. Order of execution is that the file library is searched for a match first then the templates
The relevant CSS can also be accessed via URLs i.e.
Example to import the Sitekit Stylesheet ‘blaat-inset’ into ‘blaat-2’

6. User Export
Option in control panel “Users” section to export all users as a CSV file

7. Global variable dependency
There are no changes to the interface for the creation of Global variables but their precedence and inheritance has been formalised as follows.
            global,       default language = lowest
            domain-dependent, default language = 2
            branch-dependent, default language = 3
            global,       page language = 4
            domain-dependent, page language = 5
            branch-dependent, page language = highest
KB article:

8. Embedded ‘if’ statements
Basic logic can now be embedded in templates and pages. Examples would be comparisons with Sitekit Variables as shown below.
<sitekit:IF ":::username:::" == ""> <p>You are not logged in. <a>Click here to log in.</a></p>
</sitekit:IF> OR
<sitekit:IF “:::querystringparameters.reveal:::” == “true”>
<p>This text will only show if the querystring parameter ‘reveal=true’ is supplied to the page.</p>
</sitekit:IF >
Overall the intention is to reduce the number of required templates.
Syntax is “==“ for comparison (string only) and “<>” for inequality
Example page:

9. Interface tweaks 1
Simpler login - allowing IE to prompt you for saving of passwords etc
If access is needed to a different site then this should be done by editing the ste argument in the address

10. Interface tweaks 2
Items you’ve worked on in the CMS… Design… Site Templates stay selected after saving when you return to the main page.
Soft check in for Style sheets – you’ll be informed if some other user has opened a style sheet for editing.

11. Interface tweaks 3
Internal links popup – for larger site this was becoming unworkable so if a site has more than 150 internal links then the popup changes to a more scalable ‘search and pick’ type.

12. Interface tweaks 4
Inheritance displayed– if a page inherits its layout and or style from elsewhere, the relevant parent is displayed in the drop down.

13. Items removed or changed
Credit card field – This was a field type option in forms module and has been removed because we’re not certified to take payment online.
In line editing - the earlier (single body field plus special content type) version of this has been removed

14. Highlighted feature
In line editing - the earlier (single body field plus special content type) version of this has been removed as its been replace with the current click and type version, available for all content types and body fields (except those containing script tags)