New issue 72 by davydany: Issues creating Custom Content Types
http://code.google.com/p/contentmirror/issues/detail?id=72
What steps will reproduce the problem?
1. Create custom content type, based on Archetypes. Custom content types
are in <Plone_home>/zinstance/src
2. Add custom content type to buildout, and compile. (Content Type is
usable: able to add new custom content; also edit and view them)
3. Install ContentMirror using Installation instructions from wiki.
4. Configure settings.zcml according to Installation instructions. Please
see the contents of my settings.zcml here: http://pastebin.com/RvyijkuK
What is the expected output? What do you see instead?
The expected output is that ContentMirror is supposed to detect the custom
content types, and start mirroring them to the DB.
When I start Plone, (bin/plonectl start), it is supposed to run smoothly,
but it never starts up. When running in foreground (bin/plonectl fg), The
following error is thrown: http://pastebin.com/5eERUGC8
The structure of my project is as shown below, along with my custom content
type (people.py)
<PLONE_HOME>
- buildout-cache
- Python-2.4
- zinstance
- bin
- develop-eggs
- fake-eggs
- parts
- products
- src
- crest_cms_project
- crest
- cms
- browser
- content
- people.py (contents of file:
http://pastebin.com/tzmGW7Ey)
... other content types
...
- __init__.py
- crest_cms_project.egg-info
- docs
...
- var
- Zope-2.10.11-final-py2.4
What version of the product are you using? On what operating system?
ContentMirror 0.6.0-rc3 (from cheeseshop)
Ubuntu 9.10 LTS
Please provide any additional information below.
I think the information I provided above would suffice.
Comment #1 on issue 72 by kapilt: Issues creating Custom Content Types
http://code.google.com/p/contentmirror/issues/detail?id=72
davydany was able to give me access to his instance so i could look at this
error.
The problem was that the buildout was configured to load/mirror the content
class, before loading the contentmirror configuration. Changing the zcml
load order, such that the contentmirror configuration was loaded first
fixed the issue. Clearly the error message for such a case needs to be
better constructed so that the underlying issue is more obvious.
apparently this misconfiguration of loading settings.zcml before
contentmirror was also documented in the installation instructions by alan.
so the installation instructions also need addressing.