Updating the Plumi installation process by creating a generic setup profile

[anonymous]

Worked on it. Just commiting the mess in plumi.app

Installing all dependecies, making a generic setup snapshot, installing PlumiSkin, making a new snapshot and comparing both.

Some notes about installing PlumiSkin on plone 3.1.2

Fixes on qPloneCaptcha

• Extensions/Install?.py - replace CMFCorePermissions by permissions

• Extensions/Install?.py - remove raise Exception line 42

Skins depending on Plone versions

    cd qPloneCaptchas/skins/captchas_discussion

    cp -r 2.5 3.1.2

same for captchas_sendto_form and captchas_join_form

Fixes on ATVocabularyManager

A bad fix so that portal setup works with exportSiteStructure. The right way to go would be to make GenericSetup aware of ATVocabularyManager

• ATVocabularyManager/tools/vocabularylib.py line 54

      # fix bug with exportSiteStructure removing protection on replacement
      from Globals import REPLACEABLE
      __replaceable__ = REPLACEABLE
  

[andycat]

just logging the svn urls for this:

 http://dev.plone.org/collective/browser/plumi.app

 http://dev.plone.org/collective/browser/plumi.skin

[andycat]

 http://dev.plone.org/collective/browser/plumi.app/trunk turned into an egg

added to buildout http://plumi.org/changeset/513/plumi-buildout-plone3/trunk

plumi.skin left to go

[andycat]

 http://dev.plone.org/collective/browser/plumi.skin/trunk turned into an egg also

added into buildout 'src' externals http://plumi.org/changeset/515/plumi-buildout-plone3/trunk

added into buildout.cfg http://plumi.org/changeset/516/plumi-buildout-plone3/trunk

closing ticket - open new specific ticks for functionality bugs etc