Issue 85 in contentmirror: mirror-ddl and mirror-ddl and related script commands not working with Plone > 4.2.1

3 views
Skip to first unread message

conten...@googlecode.com

unread,
Jul 18, 2013, 1:38:36 PM7/18/13
to conten...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 85 by develo...@acsr.de: mirror-ddl and mirror-ddl and related
script commands not working with Plone > 4.2.1
http://code.google.com/p/contentmirror/issues/detail?id=85


1. Install a checkout of ore.contentmirror 0.7.0svn with bulk.py patch for
Plone 4.2.x in a Plone 4.2.5 or 4.3.1 development buildout
2. do proper database setup
3. try to run:

./bin/instance run ./bin/mirror-ddl mysql | sed '/content_id INTEGER NOT
NULL,/ s//content_id INTEGER NOT NULL AUTO_INCREMENT,/g'
> ./mysql-schema.sql

Usually with Plone 4.2.1 a proper database schema is created.

Instead you get an error::

Usage: ./bin/instance run /path/to/ddl.py [options] portal_path

interpreter: error: no such option: -c

The same error message occurs with the mirror-bulk command.

### Installation details ###

Plone 4 development buildout created with paster

OS: MacOSX 10.8.4
custom Python 2.7.3
Plone Version 4.2.1 or 4.3.1 version.cfg setup
MySQL: Server version: 5.5.29 MySQL Community Server (GPL)

Remark:
-------

If you already had run these commands with Plone 4.2.1 you can run
ore.contentmirror with the Plone Versions 4.2.5 and 4.3.1 after doing in
place migration.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

conten...@googlecode.com

unread,
Jul 18, 2013, 1:43:07 PM7/18/13
to conten...@googlegroups.com

Comment #1 on issue 85 by develo...@acsr.de: mirror-ddl and mirror-ddl and
related script commands not working with Plone > 4.2.1
http://code.google.com/p/contentmirror/issues/detail?id=85

# Workaround #
--------------

There is a difference how the zopepy interpreter is setup by the
plone.recipe.zope2instanc recipe.

With Plone 4.2.1 you get the version pinned to:

plone.recipe.zope2instance = 4.2.3

With Plone 4.3.1 you get 4.2.11

If you pin down

plone.recipe.zope2instance = 4.2.3

the ore.contentmirror commands are working again.

Side effect of this pindown are not evaluated currently. Feedback welcome.
Reply all
Reply to author
Forward
0 new messages