Personal tools
You are here: Home Documentation Manuals Archetypes Developer Manual
Support

Get Help

Join our chat rooms or support forums if you have more specific questions.

Plone Training
Learn how to design, build, and deploy a website in Plone through one of the numerous Plone training sessions around the world.
Find Plone training…
 
Document Actions

Archetypes Developer Manual

This Reference Manual applies to: Plone 3.0.x, Plone 2.5.x, Plone 2.1.x
This Reference Manual is intended for: Developers

All content on one page (useful for printing, presentation mode etc.)

  1. Introduction
    1. What is Archetypes?
    2. What is ATContentTypes?
  2. A simple AT Product
    1. Introduction
    2. AT product layout
    3. The permissions module
    4. The configuration module
    5. The startup module
    6. Permissions and startup modules - Take 2
    7. The content package and its modules
    8. Adding a custom view to the skin
    9. Installing the product
    10. Basic integration tests
  3. Fields
    1. Overview
    2. Fields Reference
    3. Widgets Reference
    4. Validator Reference
by Kamon Ayeva last modified August 31, 2007 - 15:39
Contributors: Sisi Nutt, Alexander Limi, Martin Aspeli, Marco De Vitis, Raphael Ritz, Maik Röder, Steve McMahon
All content is copyright Plone Foundation and the individual contributors.

"Add comment" for the product

Posted by Bernhard Jantscher at November 20, 2007 - 22:22
Great tutorial! :)
But I didn't get how to enable discussions for such a product (like "instant message"). I played around with it, but I could not figure out how to get this "Add comment" button for such instant message objects, although I enabled "allow discussion" for the objects...

Be careful while naming fields

Posted by Shashikant Penumarthy at January 23, 2008 - 02:15
Note that there are some names that seem to be 'reserved' in Plone. A couple that I've encountered are 'role' and 'manager'. If you use these in your content types (as portal_type or name of a property) you will get strange errors that tell you nothing about the name collision.

So to avoid problems, use the java-style naming convention. Instead of calling a portal_type 'role', call it 'com.mycompany.role'. Instead of calling a property 'manager', give it a longer name like 'mycompanyManager' or something.

Same goes for searching with portal_catalog. Don't use portal_type to search but rather search for objects that implement a certain interface, etc.

content_icon format and size

Posted by Derek Richardson at February 18, 2008 - 17:32
As stated by jensens on #plone:

normally content_icon is 16x16 gif or png

I'm adding this here so I can find it if I forget. Google searches previously turned up nothing useful.

For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by