Sep 18, 2012
My journey exploring hidden features of the Plone registry continues. This time we will focus on aspects related to product migration, and how to get a nice user interface for our users
My last post was about how to use Plone registry in a clean way, also when storing complex data inside it.
Today we'll talk about the Plone registry again! I've some other tips to share!
Another good article
I'm not the only one to be inspired by the registry. After my first article about this subject, I came upon Complex Plone registry settings revisited. Take a read, is another interesting approach!
I needed to implement the same product that inspired me for the last article, collective.analyticspanel, with some new features requested by a customer of ours.
Regardless the specific features, what is important is that:
- it somehow changes the type of one of our existing field;
- it adds a new field (that should be kept separated from the others).
Jul 23, 2012
Once upon a time there was Plone; it used to store its configuration inside a ZMI repository called "Plone Properties Tool"... But time has passed and now Plone is moving to plone.app.registry
A debconf-like (or about:config-like) registry for storing application settings
I think this is great: I really like the about:config page on my Firefox!
This means that there is a unified configuration panel for storing "data", in the most general way. Let me show you some examples:
- If your application need to store a secret API key...
- When your product must store some general installation preference...
- If your site need to store something that isn't content specific...
...Let's use the registry! Ok, I think you got it. Now, let's see how it works.