WebDAV configuration with Apache, Kerberos and LDAP

Re: content type icons missing in migrated site

John DeStefano, on 2009-03-31:
> Module Products.PortalTransforms.TransformEngine, line 181, in convertTo
> Module Products.PortalTransforms.chain, line 51, in convert
> Module Products.PortalTransforms.Transform, line 192, in convert
> AttributeError: _v_transform
>
> I found this:
> https://weblion.psu.edu/trac/weblion/wiki/vTransform
> ... which states: "An "Attribute Error?: _v_transform" error is caused  
> by a broken translation in portal_transforms. To resolve it, remove  
> any transformations marked as broken in the "Contents" and "Policy"  
> tabs of the portal_transforms tool in the ZMI."
>
> However, nothing seems broken in the Contents or Policy tabs of  
> portal_transforms.  I also clicked the "Reload transforms" tab, which  
> completed without error, but the document view problem remains.

A guess, bug maybe this is the same problem as I describe here?

http://maurits.vanrees.org/weblog/archive/2009/03/when-your-correctly-configured-portal-tool-is-not-working

--

-- 
Maurits van Rees | http://maurits.vanrees.org/
            Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]

Re: Plone 3 & plone.app.ldap

Oh boy! Here we go again!! 

I was trying this out on a virtual machine on my Mac and somehow my VM got mangled  and I had to start all over. I
was actually Ok with doing this thinking I would be able to figure out a repeatable process.

What I did was install a fresh copy of ubuntu 8.10 server. I then followed my own sequence above (add first the
openldap and python-ldap sections, no plone.app.ldap references, and ran buildout), but I am stuck in
exactly the same spot... bildout complaining that
Error: Couldn't find a distribution for 'python-ldap>=2.0.6'.However, I have the following in my buildout.cfg:
[python-ldap]
recipe = zc.recipe.egg:custom
url = http://kent.dl.sourceforge.net/sourceforge/python-ldap/python-ldap-2.3.6.tar.gz
egg = python-ldap
include-dirs  =
    ${openldap:location}/include
library-dirs  =
    ${openldap:location}/lib 

[openldap]
recipe = zc.recipe.cmmi
url = ftp://ftp.openldap.org/pub/OpenLDAP/openldap-stable/openldap-stable-20080813.tgz
extra_options = --with-sasl --with-tls --enable-slapd=no

and I actually have already installed the binary packages (via ubuntu's apt-get install) for openldap and
python-ldap. In this paste  you can see the versions of both: python-ldap is 2.3.4. In this other paste  I
have a copy of my current bildout.cfg.

So:
1) It seems buildout is not looking for the packages I have installed on my OS before trying to build them
(otherwise, why is it complaining about the python-ldap version?), and
2) Even if it was unable to see and/or make use of the binary packages I have on my OS, the link I am referencing
in the python-ldap section is for version 2.3.6 (!!)... so it is not using this either.

This takes me to believe:
1) There is somewhere else that buildout is looking for python-ldap... but where? I cannot figure it out.
2) There must be a way to tell buildout to use the python-ldap installed on my system... but how?

--

-- 
View this message in context: http://n2.nabble.com/Plone-3---LDAP-with-remote-server--what-to-intall-tp2529188p2578678.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.

Re: Plone 3 & plone.app.ldap

And here's the paste  with the verbose output of buildout
--

-- 
View this message in context: http://n2.nabble.com/Plone-3---LDAP-with-remote-server--what-to-intall-tp2529188p2578856.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.

Re: content type icons missing in migrated site

Pb with buildout and a quite empty development egg

Hi,

I am willing to try sqlalchemy with Plone-3.2.2.

I have created an empty developement egg with "paster create -t plone ..."

I have added the following dependency in my setup.py file :
      install_requires=[
          'setuptools',
          'MySQL-Python',
          'collective-lead',
          # -*- Extra requirements: -*-
      ],

I have made a mistake using a dash instead of a dot.

So I changed setup.py and re-run buildout, I still get an error message Couldn't find a distribution for
'collective-lead' 

I have commented out my product in buildout.cfg (the '#' must be placed as the first character of the line
otherwise, buildout try to install #src/myproduct), run buildout to uninstall it, the try to install my
product again.

Nothing changes, event though my product seems to be only in my zinstance/src directory.

What am I missing ?

Thanks

 
--

-- 
View this message in context: http://n2.nabble.com/Pb-with-buildout-and-a-quite-empty-development-egg-tp2580779p2580779.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.

Re: Pb with buildout and a quite empty development egg

True, and if you remove 'collective-lead' in requires.txt leaving it in setup.py, the buildout would not
complain, once your product commented out in the buildout.cfg ...
strange 
you just need to remove it from setup.py ...

Hi,

I am willing to try sqlalchemy with Plone-3.2.2.

I have created an empty developement egg with "paster create -t plone ..."

I have added the following dependency in my setup.py file :
      install_requires=[
          'setuptools',
          'MySQL-Python',
          'collective-lead',
          # -*- Extra requirements: -*-
      ],

I have made a mistake using a dash instead of a dot.

So I changed setup.py and re-run buildout, I still get an error message Couldn't find a distribution for
'collective-lead' 

I have commented out my product in buildout.cfg (the '#' must be placed as the first character of the line
otherwise, buildout try to install #src/myproduct), run buildout to uninstall it, the try to install my
product again.

Nothing changes, event though my product seems to be only in my zinstance/src directory.

What am I missing ?

Thanks

--

-- 
View this message in context: http://n2.nabble.com/Pb-with-buildout-and-a-quite-empty-development-egg-tp2580779p2581692.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.

Re: Pb with buildout and a quite empty development egg

Thanks for your advice, 

I have unstinstalled my product by commenting it in the buildout.cfg and running bin/buildout

Then I cleared the content of the requires.txt, and reinstall myproduct, and it worked

Hopefully this was just a test and not my production server

Thanks again

True, and if you remove 'collective-lead' in requires.txt leaving it in setup.py, the buildout would not
complain, once your product commented out in the buildout.cfg ...
strange 
you just need to remove it from setup.py ...

--

-- 
View this message in context: http://n2.nabble.com/Pb-with-buildout-and-a-quite-empty-development-egg-tp2580779p2585258.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.

advise needed- existing plone3 site to use ldap

Hi,

I've got a "mature" plone site.  Users, groups, content going
back a few years.  Currently at 3.1.  Actually a few plone sites.

I plan to move from the built-in plone user/group authentication
and information to LDAP.

I expect to use plone.app.ldap to manage the LDAP.

My question, is what is the smoothest way to manage the transistion.

For example, if we move a user's info from plone to ldap, how to
preserve the permissions and meta-data on content within the plone
site.  If a particular user/group has security information set, like
a private folder, I don't want to loose that.

I've searched a bit for this information but have not yet found the
silver bullet.

Any advise appreciated!

thanks,
Stuart

A corporate buildout repository for Windows