n order to then migrate your existing file content to blobs you can use the
migration interface provided at http://localhost:8080/plone/@@blob-migration,
where "plone" should be replaced with the id of your "Plone Site" object. The
page will show you the number of available ATFile instances and lets you
convert them to the provided blob content type by clicking a button.
For a root ZEO cluster an equivalent command could be
sudo /opt/Plone-3.1/zeocluster/bin/client1 stop && sudo /opt/Plone-3.1/zeocluster/parts/client1/bin/zopectl adduser user1 password1
wondering what led to the problem for me, if I had deleted the product at /Control_Panel/Products/manage_main then restarted the ZEO cluster, might that have thrown a spanner in the works?
2008-09-23T10:35:03 <RobZoneNet> i believe that should be the desired action
Seems that it's OK to delete products in this way. (AFAIR it's sometimes necessary/recommended when the TTP view of available/installed products has gone awry. Following that, and a restart, both ZMI and TTP views of products should be fine.)
The RPX SaaS is agnostic to the platform running your
website. The only requirements are 1) the website is
able to make HTTPS call out to the service, and 2) that
the site must be able to parse either JSON or XML used
in the response.
We need to make clear from the outset that whilst startup time may be noticeable to a developer, it need never be an issue to end users of a production service.
r the core which is maintained by the Plone Foundation