Installing XDV -

heya,

I'm attempting to install XDV, as per the instructions here:

http://plone.org/documentation/manual/theming/referencemanual-all-pages

After running bin/buildout, I re-started Plone, and there was no "Theme
Transform" section under "Site Setup"

Running back to have a look at the output from buildout, I did notice some
errors. I've attached the output for it below this message. I also ran a
buildout -n after that, output also below.

Any suggestions?

Cheers,
Victor

[victorhooi <at> zenator-arch zinstance]$ bin/buildout 
Uninstalling zopepy.                              
Uninstalling instance.                            
Updating zope2.                                   
Updating fake eggs                                
Updating productdistros.                          
Installing instance.                              
Getting distribution for 'collective.xdv==1.0rc3'.
Got collective.xdv 1.0rc3.                        
Download error: (-2, 'Name or service not known') -- Some packages may not
be found!

xdv: problem in locating theme and rules files

Hi all,
I'm trying to setup xdv for plone 3.3 following the intructions at:
http://plone.org/documentation/manual/theming/referencemanual-all-pages

All went well until I try to activate xdv.
If I give to the theme and rule files the full pathname it works.

If I give the buildout relative path it gives an error

If I use apache to serve the static files it gives an error.

What can I do?

Thanks
    Mirto

In detail (paths relative to my installation):

Full path (works):
/usr/local/Plone33/zeocluster/themes/theme.html
/usr/local/Plone33/zeocluster/themes/rules.xml

Relative path (error):
themes/theme.html
themes/rulesbase.xml

The event.log says:
______________________________________________________________________________________________
------
2009-09-03T13:25:57 ERROR collective.xdv Unexpected error whilst trying 

Re: xdv: problem in locating theme and rules files

Mirto Silvio Busico wrote:
> Hi all,
> I'm trying to setup xdv for plone 3.3 following the intructions at:
> http://plone.org/documentation/manual/theming/referencemanual-all-pages
> 
> All went well until I try to activate xdv.
> If I give to the theme and rule files the full pathname it works.
> 
> If I give the buildout relative path it gives an error

It's not necessarily the buildout relative path: it's the pat relative 
to the working directory from which you started Zope.

> If I use apache to serve the static files it gives an error.

Not sure what could be wrong. I think it's only really been tested with 
local files.

Martin

--

-- 
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book

Re: Re: xdv: problem in locating theme and rules files

Martin Aspeli ha scritto:
> Mirto Silvio Busico wrote:
>> Hi all,
>> I'm trying to setup xdv for plone 3.3 following the intructions at:
>> http://plone.org/documentation/manual/theming/referencemanual-all-pages
>>
>> All went well until I try to activate xdv.
>> If I give to the theme and rule files the full pathname it works.
>>
>> If I give the buildout relative path it gives an error
>
> It's not necessarily the buildout relative path: it's the pat relative 
> to the working directory from which you started Zope.
A little confused.
I'm using the 3.3 unified installer. Used the zeo configuration.
So the scripts that I use to start zeo, client1 and client2 are located 
in /usr/local/Plone33/zeocluster/bin

You mean a subdirectory in bin? Or a subdirectory in zeocluster? Or a 
subdirectory in zeocluster/var/filestorage where Data.fs lives?

Sorry I was not able to determine this.
BTW I failed to install deliverance and I was only able to create a test 
suite with deliverancedemo 
(http://svn.plone.org/svn/collective/deliverancedemo/) for wich I was 
not able to connect to the Plone 3.3 normal framework. So xdv seems the 
only solution I can try.

Thanks
    Mirto

Re: xdv: problem in locating theme and rules files

Mirto Silvio Busico wrote:
> Martin Aspeli ha scritto:
>> Mirto Silvio Busico wrote:
>>> Hi all,
>>> I'm trying to setup xdv for plone 3.3 following the intructions at:
>>> http://plone.org/documentation/manual/theming/referencemanual-all-pages
>>>
>>> All went well until I try to activate xdv.
>>> If I give to the theme and rule files the full pathname it works.
>>>
>>> If I give the buildout relative path it gives an error
>> It's not necessarily the buildout relative path: it's the pat relative 
>> to the working directory from which you started Zope.
> A little confused.
> I'm using the 3.3 unified installer. Used the zeo configuration.
> So the scripts that I use to start zeo, client1 and client2 are located 
> in /usr/local/Plone33/zeocluster/bin
> 
> You mean a subdirectory in bin? Or a subdirectory in zeocluster? Or a 
> subdirectory in zeocluster/var/filestorage where Data.fs lives?
> 
> Sorry I was not able to determine this.

The current working directory is wherever you are when you launch the 
process (unless it's changed).

It's a standard shell concept - you can find out the current one on the 
command line by typing 'pwd'.

Martin

Buildout error: No module named download

Hi all,
today I have problems with plone 3.3 buildout modified for xdv.

The error is:
  File

"/usr/local/plotest/buildout-cache/eggs/zc.recipe.cmmi-1.3-py2.4.egg/zc/recipe/cmmi/__init__.py", 
line 27, in ?
    import zc.buildout.download
ImportError: No module named download

Any hint?

Thanks
    Mirto

P.S. The complete log:

mirto <at> msb02:/usr/local/plotest/zinstance$ sudo bin/buildout -v
Installing 'z3c.recipe.staticlxml'.                          
Picked: z3c.recipe.staticlxml = 0.7.1                        
Getting required 'zc.recipe.cmmi'                            
  required by z3c.recipe.staticlxml 0.7.1.                   
Picked: zc.recipe.cmmi = 1.3                                 
Getting required 'zc.recipe.egg==1.2.2'                      
We have the distribution that satisfies 'zc.recipe.egg==1.2.2'.
While:                                                        
  Installing.                                                 
  Getting section lxml.                                       
  Initializing section lxml.                                  

Upgrade to 3.3 Failed

I just tried to upgrade to 3.3 today.  Buildout went fine, but the Upgrade
did not go through in dry run mode.  Here's the output.  Any thoughts?

    *   Dry run selected.
    * Starting the migration from version: 3.1.4
    * Attempting to upgrade from: 3.1.4
    * Upgrade aborted
    * Error type: zExceptions.BadRequest
    * Error value: Invalid or duplicate property id
    * File
"/usr/local/Plone3.2.3/buildout-cache/eggs/Plone-3.3-py2.4.egg/Products/CMFPlone/MigrationTool.py",
line 210, in upgrade newv, msgs = self._upgrade(newv)
    * File
"/usr/local/Plone3.2.3/buildout-cache/eggs/Plone-3.3-py2.4.egg/Products/CMFPlone/MigrationTool.py",
line 321, in _upgrade res = function(self.aq_parent)
    * File
"/usr/local/Plone3.2.3/buildout-cache/eggs/Plone-3.3-py2.4.egg/Products/CMFPlone/migrations/v3_1/final_three1x.py",
line 15, in three14_three15 loadMigrationProfile(portal,
'profile-Products.CMFPlone.migrations:3.1.3-3.1.4')
    * File
"/usr/local/Plone3.2.3/buildout-cache/eggs/Plone-3.3-py2.4.egg/Products/CMFPlone/migrations/migration_util.py",
line 107, in loadMigrationProfile tool.runAllImportStepsFromProfile(profile,
purge_old=False)
    * File
"/usr/local/Plone3.2.3/buildout-cache/eggs/Products.GenericSetup-1.4.5-py2.4.egg/Products/GenericSetup/tool.py",
line 390, in runAllImportStepsFromProfile
ignore_dependencies=ignore_dependencies)
    * File
"/usr/local/Plone3.2.3/buildout-cache/eggs/Products.GenericSetup-1.4.5-py2.4.egg/Products/GenericSetup/tool.py",

Re: Upgrade to 3.3 Failed

Re: Buildout error: No module named download

Mirto Silvio Busico wrote:
> Hi all,
> today I have problems with plone 3.3 buildout modified for xdv.
> 
> The error is:
>  File 
>
"/usr/local/plotest/buildout-cache/eggs/zc.recipe.cmmi-1.3-py2.4.egg/zc/recipe/cmmi/__init__.py", 
> line 27, in ?
>    import zc.buildout.download
> ImportError: No module named download
> 
> Any hint?
> 
> Thanks
>    Mirto
> 
> 
> P.S. The complete log:
> 
> mirto <at> msb02:/usr/local/plotest/zinstance$ sudo bin/buildout -v
> Installing 'z3c.recipe.staticlxml'.                          Picked: 
> z3c.recipe.staticlxml = 0.7.1                        Getting required 
> 'zc.recipe.cmmi'                             required by 
> z3c.recipe.staticlxml 0.7.1.                   Picked: zc.recipe.cmmi = 
> 1.3                                 Getting required 
> 'zc.recipe.egg==1.2.2'                      We have the distribution 
> that satisfies 'zc.recipe.egg==1.2.2'.
> While:                                                        
>  Installing.                                                  Getting 
> section lxml.                                        Initializing 
> section lxml.                                   Loading zc.buildout 
> recipe entry z3c.recipe.staticlxml:default.
> 
> An internal error occured due to a bug in either zc.buildout or in a
> recipe being used:                                                 
> Traceback (most recent call last):                                  File 
>
"/usr/local/plotest/buildout-cache/eggs/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py", 
> line 1509, in 
> main                                                                                                     
> 
>    getattr(buildout, command)(args)
>  File 
>
"/usr/local/plotest/buildout-cache/eggs/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py", 
> line 357, in install
>    [self[part]['recipe'] for part in install_parts]
>  File 
>
"/usr/local/plotest/buildout-cache/eggs/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py", 
> line 888, in __getitem__
>    options._initialize()
>  File 
>
"/usr/local/plotest/buildout-cache/eggs/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py", 
> line 969, in _initialize
>    recipe_class = _install_and_load(reqs, 'zc.buildout', entry, buildout)
>  File 
>
"/usr/local/plotest/buildout-cache/eggs/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py", 
> line 932, in _install_and_load
>    return pkg_resources.load_entry_point(
>  File 
> "/usr/local/plotest/buildout-cache/eggs/setuptools-0.6c9-py2.4.egg/pkg_resources.py", 
> line 277, in load_entry_point
>    return get_distribution(dist).load_entry_point(group, name)
>  File 
> "/usr/local/plotest/buildout-cache/eggs/setuptools-0.6c9-py2.4.egg/pkg_resources.py", 
> line 2180, in load_entry_point
>    return ep.load()
>  File 
> "/usr/local/plotest/buildout-cache/eggs/setuptools-0.6c9-py2.4.egg/pkg_resources.py", 
> line 1913, in load
>    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
>  File 
>
"/usr/local/plotest/buildout-cache/eggs/z3c.recipe.staticlxml-0.7.1-py2.4.egg/z3c/recipe/staticlxml/__init__.py", 
> line 16, in ?
>    import zc.recipe.cmmi
>  File 
>
"/usr/local/plotest/buildout-cache/eggs/zc.recipe.cmmi-1.3-py2.4.egg/zc/recipe/cmmi/__init__.py", 
> line 27, in ?
>    import zc.buildout.download
> ImportError: No module named download
> mirto <at> msb02:/usr/local/plotest/zinstance
> 
> _______________________________________________
> Setup mailing list
> Setup@...
> http://lists.plone.org/mailman/listinfo/setup

Mirto,

I had the same error. I pinned my cmmi recipe to the previous version 
and that fixed it for now.

HTH,

--

-- 
Larry Pitcher
Catapult Solutions

Web:    www.catapultsolutions.net
Email:  larry.pitcher@...
Skype:  larry.pitcher
Phone:  509.849.2660

[SOLVED] Re: Buildout error: No module named download

Larry Pitcher ha scritto:
> Mirto Silvio Busico wrote:
>> Hi all,
>> today I have problems with plone 3.3 buildout modified for xdv.
>>
>> The error is:
>>  File 
>>
"/usr/local/plotest/buildout-cache/eggs/zc.recipe.cmmi-1.3-py2.4.egg/zc/recipe/cmmi/__init__.py", 
>> line 27, in ?
>>    import zc.buildout.download
>> ImportError: No module named download
>>
>> Any hint?
>>
>> Thanks
>>    Mirto
>>
>>
>> P.S. The complete log:
>>
>> mirto <at> msb02:/usr/local/plotest/zinstance$ sudo bin/buildout -v
>> Installing 'z3c.recipe.staticlxml'.                          Picked: 
>> z3c.recipe.staticlxml = 0.7.1                        Getting required 
>> 'zc.recipe.cmmi'                             required by 
>> z3c.recipe.staticlxml 0.7.1.                   Picked: zc.recipe.cmmi 
>> = 1.3                                 Getting required 
>> 'zc.recipe.egg==1.2.2'                      We have the distribution 
>> that satisfies 'zc.recipe.egg==1.2.2'.
>> While:                                                        
>>  Installing.                                                  Getting 
>> section lxml.                                        Initializing 
>> section lxml.                                   Loading zc.buildout 
>> recipe entry z3c.recipe.staticlxml:default.
>>
>> An internal error occured due to a bug in either zc.buildout or in a
>> recipe being used:                                                 
>> Traceback (most recent call last):                                  
>> File 
>>
"/usr/local/plotest/buildout-cache/eggs/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py", 
>> line 1509, in 
>> main                                                                                                     
>>
>>    getattr(buildout, command)(args)
>>  File 
>>
"/usr/local/plotest/buildout-cache/eggs/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py", 
>> line 357, in install
>>    [self[part]['recipe'] for part in install_parts]
>>  File 
>>
"/usr/local/plotest/buildout-cache/eggs/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py", 
>> line 888, in __getitem__
>>    options._initialize()
>>  File 
>>
"/usr/local/plotest/buildout-cache/eggs/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py", 
>> line 969, in _initialize
>>    recipe_class = _install_and_load(reqs, 'zc.buildout', entry, 
>> buildout)
>>  File 
>>
"/usr/local/plotest/buildout-cache/eggs/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py", 
>> line 932, in _install_and_load
>>    return pkg_resources.load_entry_point(
>>  File 
>> "/usr/local/plotest/buildout-cache/eggs/setuptools-0.6c9-py2.4.egg/pkg_resources.py", 
>> line 277, in load_entry_point
>>    return get_distribution(dist).load_entry_point(group, name)
>>  File 
>> "/usr/local/plotest/buildout-cache/eggs/setuptools-0.6c9-py2.4.egg/pkg_resources.py", 
>> line 2180, in load_entry_point
>>    return ep.load()
>>  File 
>> "/usr/local/plotest/buildout-cache/eggs/setuptools-0.6c9-py2.4.egg/pkg_resources.py", 
>> line 1913, in load
>>    entry = __import__(self.module_name, globals(),globals(), 
>> ['__name__'])
>>  File 
>>
"/usr/local/plotest/buildout-cache/eggs/z3c.recipe.staticlxml-0.7.1-py2.4.egg/z3c/recipe/staticlxml/__init__.py", 
>> line 16, in ?
>>    import zc.recipe.cmmi
>>  File 
>>
"/usr/local/plotest/buildout-cache/eggs/zc.recipe.cmmi-1.3-py2.4.egg/zc/recipe/cmmi/__init__.py", 
>> line 27, in ?
>>    import zc.buildout.download
>> ImportError: No module named download
>> mirto <at> msb02:/usr/local/plotest/zinstance
>>
>> _______________________________________________
>> Setup mailing list
>> Setup@...
>> http://lists.plone.org/mailman/listinfo/setup
>
> Mirto,
>
> I had the same error. I pinned my cmmi recipe to the previous version 
> and that fixed it for now.
>
> HTH,
>
Thanks a lot: it worked!

Regards
    Mirto