Author: Plone Foundation



KSS (Kinetic Style Sheets) for Archetypes

This product gives generic KSS support to Archetypes. It depends on the product
"kss.core" and "".

Features implemented

- In-place field validation. In the edit field, when a field area is left,
  the field gets validated and field error  message is displayed.

  This must be implemented for each field type individually. At the moment,
  only the stringField is done. To test, go to a mandatory field like Title,
  delete its value and try to leave it.

- In-place form submission. When the Save button is pressed, we first validate
  the entire form from the page. If we have an error, we stay in the page and
  display the portal status message, plus every field error message. If there is
  no error, we resubmit the form.

  The form resubmission may be implemented in a more effective way in the future,
  together with the total rewrite of AT's current submission scripts.


     - Implement field validation for all the other field types.

     - There is a lingering UnicodeDecodeError during the rendering of document_view.
       UPDATE. The problem is related to Zope 2.10 and/or AT,
       but since I can't run AT trunk on Zope 2.9, I will need to provide a fix...

     - The popups for leaving the edit region are not hooked in. This means that sometimes
       the "do you want to leave the page" popup comes in where it should not be.

     - The loading of the kupu editor is done with a simple hack, it seems to
       be no clean way in javascript to find when the iframe has been loaded,
       some more complex hack is needed for this that works on all browsers
       and is reliable in all the cases.

KSS extensions defined for general purpose use

- A generic macro replacer server action

- client action for submitting to an url

- client action for submitting the current form


1.7.3 (2013-08-14)

- On KSS Validation, pass REQUEST to validate method.
  Without it, it can happen that the language negociator chooses
  a different language for error messages than the regular form validation.
  This can result in error messages in different languages for kss
  and normal form validation.

1.7.2 (2012-05-25)

1.7.1 (2011-07-19)

- The change r12412 in 1.6.0a3 introduced a regression,
  the field inline validating error message was not shown to the user.
  The error message is not always the "required field" message, so it's
  problematic to not show the error message in all cases.
  The warning_only parameter is now set to False in the issueFieldError call so
  the error message appears again.

1.7.0 (2011-01-03)

- Use plone.uuid to look up content UUIDs.
  [toutpt, davisagli]

1.6.0 (2010-07-31)

- Calling it a 1.6.0 final, no changes since b1.

1.6.0b1 (2010-05-01)

- Check for inline editing status on an actual field in the content-core, not
  title which is now rendered by hand.

1.6.0a3 (2010-03-09)

- Made error message be a warning instead before the form has been submitted,
  this causes less disruption in a form while editing.

1.6.0a2 (2010-03-09)

- Fixed test failure in testVersionPreviewIsNotInlineEditable.

1.6.0a1 (2009-11-19)

- Fixed validation test to work with files.

- Updated reference to IATDocument from Products.ATContentTypes to the
  standard location.

1.4.3 (2008-11-02)

- Enable unlock on unload for inline edits.

1.4.2 (2008-08-18)

- Using an adapter to determine whether inline editing is enabled, so
  the default behaviour can easily be overridden.

- Added check for site_property 'enable_inline_editing'. This is a global
  setting which can still be overwritten with