This package should be safe to install and easy to uninstall (there is also
uninstall profile). That means its fairly safe to give it a try, but just in
case don’t forget to create backup before testing it.

As of version 1.4.0 there is quite comprehensive unittest coverage of python
code as well as high coverage of our javascript code. There are also some robot
tests which are testing integration with Plone, but this will be improved with
future releases.

This project will be integrated with Plone 5 and will never reach version
2.0.0. You can monitor progress of PLIP here.

If you wonder why there is no Alpha/Beta marker in version, its because version
of this package is kept in sync with other projects deriving from Mockup
(eg. plone.app.widgets). Version 1.4.1 would then mean we’re using
Mockup version 1.4 and there was one bugfix only to the python code. Version
packaged javascript inside is still in sync with Mockup project.

Also, in order to correctly support updating a page after using Edit, you
must ensure that the element #portal-column-content exists within your
theme. In short, as with Plone’s default theme, this element should correspond
to the main content column. It will be repopulated with updated content after
an edit action takes place via the toolbar. A rule similar to this is
needed - in this case, the entire element is placed into the theme: