Adding additional new products to Cyn.in 3.1.3

Overview

The objective of this wiki is guide about the process of adding additional new products to the Cyn.in 3.1.3

For this task I selected the example.archetype product that is "an example package for learning how to develop an Archetypes-based content type".

Although this product is available to install from two resources like:

• http://pypi.python.org/pypi/example.archetype/1.0
• http://plone.org/products/example.archetype/releases/1.0
  

• http://svn.plone.org/svn/collective/example.archetype/trunk/

Step by step

cd ~/cynin313-source-snapshot/

nano ~/cynin313-source-snapshot/buildout.cfg

and add the lines bellow:

[buildout]
...
extends = versions.cfg
versions = versions

# This extension will dump a list of unpinned versions
# each time you run buildout.
extensions = 
    buildout.dumppickedversions
    mr.developer

dump-picked-versions-file = dumped-versions.cfg
overwrite-picked-versions-file = True

always-check = true
auto-checkout =
    example.archetype

# Reference any eggs you are developing here, one per line
# e.g.: develop = src/my.package
develop =
   ...
    src/example.archetype
   
...

[cyninbase]
# Add additional eggs here
# elementtree is required by Plone
eggs =
    ...
    example.archetype

zcml =
    ...
    example.archetype

...
#
# specific source checkouts
#
[sources]
example.archetype = svn http://svn.plone.org/svn/collective/example.archetype/trunk/

nano ./src/ubify.policy/ubify/policy/config.py

Locate the bellow sections and add the new configuration

PRODUCT_DEPENDENCIES = ('Calendaring',
                        ...
                        'example.archetype',

spacesdefaultaddablenonfolderishtypes = ('Document',
                                         ...
                                         'InstantMessage',
                                        )

Then edit ContentRoot.xml file from default profile of ubify.coretypes products and add the bellow configuration:

nano ./src/ubify.coretypes/ubify/coretypes/profiles/default/types/ContentRoot.xml

...
<element value="Image"/>
<element value="InstantMessage"/>
<element value="Link"/>,
...

Also you need repeat the last past with ContentSpace.xml files from default profile of ubify.coretypes product and add the bellow configuration:

nano ./src/ubify.coretypes/ubify/coretypes/profiles/default/types/ContentSpace.xml

...
<element value="Image"/>
<element value="InstantMessage"/>
<element value="Link"/>,
...

Then re-run buildout

./bin/buildout -vNc user.cfg

When your buildout is complete, you can start the zope server by typing:

./bin/instance fg

"2008-07-14 13:58:25 INFO Zope Ready to handle requests"

Congratulations, you've managed to get over the difficult parts. Now for the easy / fun stuff:

Open up your favorite browser (Everybody say together with me: Firefox!) :)

Navigate to http://localhost:8080 (if you use the same computer as desktop) or substitute the localhost with the hostname (or even the IP address) of the computer that zope/cyn.in is running on.

You should see the "Zope quick start screen". Cool, you can access your newly built Zope server. Next, navigate to http://localhost:8080/manage . This will give you an HTTP basic authentication request. Use the following credentials to get in: username: admin and password: secret

You will see the standard Zope management interface. On the left you will see a frame when the Id of your previous cyn.in website created. The go to clic on Id and Now, scroll down, and find the item called portal_quickinstaller (Allows to install/uninstall products) and click on that.

button. Do NOT check any other item.

Again, this will take some time and you can watch the scrolling progress in your fg command line window. When it completes, the list will refresh where most of the items will have moved down to the "Installed Products" section.

Great, you don't know it yet, but you've managed to get a working cyn.in installation built out of source! :)

http://localhost:8080/cynin

If you don't like doing as recommended and chose a different ID during Plone Site creation, substitue your ID in place of cyin in the above URL, of course.

After some moments of tense waiting, the familiar cyn.in login screen should greet you and you can get in by using the following standard credentials: username: siteadmin and password: secret

TODO

• Write how integrate with meta data block
• Write how create a new site updates portlet for new content type
• Write how create a new apps view for new content type
• Write how integrate my new content type to site stats and content types distribution pie chart
• Create a Policy product for these configuration