MRS IT Admin | 1 Feb 10:01
Picon
Favicon

Upgrading from Plone 2.0.5 to 2.5 on different Server


I am new for Plone and I have only Windows experience. 
I have Plone system 2.0.5 (Zope 2.3; Python 2.3.3). I do not have time to
read the whole Plone manual and the provided upgrade manual is not enough
for me. 
Is there a proper guide of how to perform upgrade to 2.5 which I am planning
to install on different server. 
Thanks
--

-- 
View this message in context: http://n2.nabble.com/Upgrading-from-Plone-2-0-5-to-2-5-on-different-Server-tp4493272p4493272.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.

Martin Aspeli | 1 Feb 11:28
Picon

Re: Upgrading from Plone 2.0.5 to 2.5 on different Server

MRS IT Admin wrote:
> I am new for Plone and I have only Windows experience.
> I have Plone system 2.0.5 (Zope 2.3; Python 2.3.3). I do not have time to
> read the whole Plone manual and the provided upgrade manual is not enough
> for me.
> Is there a proper guide of how to perform upgrade to 2.5 which I am planning
> to install on different server.

You're going to get better help if you ask better questions.

  - What did you read?
  - Why is it not enough for you?
  - What are you struggling with?
  - What did you try?

Also, please note that Plone 2.5 is about to go out of support, as Plone 
4 is around the corner. You may be better served upgrading to Plone 3.3.4.

Martin

--

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

Dale DeWitt | 2 Feb 02:47
Picon

Re: Upgrading from Plone 2.0.5 to 2.5 on different Server

I take it you meant installing Plone 3.3.4 and moving content/path
manually.  Surely you didn't mean that it would be feasible to upgrade
from 2.0.5 upward and have a pristine version free from error,
assuming minimal third-party product assault.  Although I've never
done that I've surmised from the forums what a long laborious hoop
journey that would become (better left to A.I.).

On Feb 1, 4:28 am, Martin Aspeli <optilude+li...@...> wrote:
> MRS IT Admin wrote:
> > I am new for Plone and I have only Windows experience.
> > I have Plone system 2.0.5 (Zope 2.3; Python 2.3.3). I do not have time to
> > read the whole Plone manual and the provided upgrade manual is not enough
> > for me.
> > Is there a proper guide of how to perform upgrade to 2.5 which I am planning
> > to install on different server.
>
> You're going to get better help if you ask better questions.
>
>   - What did you read?
>   - Why is it not enough for you?
>   - What are you struggling with?
>   - What did you try?
>
> Also, please note that Plone 2.5 is about to go out of support, as Plone
> 4 is around the corner. You may be better served upgrading to Plone 3.3.4.
>
> Martin
>
> --
> Author of `Professional Plone Development`, a book for developers who
(Continue reading)

MRS IT Admin | 2 Feb 09:46
Picon
Favicon

Re: Upgrading from Plone 2.0.5 to 2.5 on different Server


Dear Martin,
I wanted to upgarde forst to 2.5 as there is no direct way to upgarde to v3.
Only when everything works on 2.5 the next step will be 3.3.
Well basically I do not know what to read in order to get the right
knowledge for the Package.
As Plone includes Plone, Zope and Python I am not sure on what I should
concentrate to become system admin e.g installation, upgrading and adding
plug ins.
So my thought was is there a way I can compare check the plugins installed
on the old version, export the site settings and data and import it into the
new server.
Thanks
Georgi

--

-- 
View this message in context: http://n2.nabble.com/Upgrading-from-Plone-2-0-5-to-2-5-on-different-Server-tp4493272p4499627.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.

Picon

buildout problems behind a proxy

Hi all,

I'm trying to use buildout behind a proxy.

If I'm directly connecet to Internet everything works.

behind a proxy (and a firewall) the standard buildout generated by the 
unified installer doesn't work unless I add in /etc/profile file the lines

export http_proxy=http://test:test-Q0ErXNX1RuYZj/J+X32AWw <at> public.gmane.org:8080
export ftp_proxy=http://test:test-Q0ErXNX1RuYZj/J+X32AWw <at> public.gmane.org:8080

after this the command "sudo bin/buildout -n -v" works correctly.

But when I add my buildout extensions I get the error:

IOError: [Errno socket error] (-2, 'Name or service not known')

Adding in /etc/profile the line

export https_proxy=http://test:test-Q0ErXNX1RuYZj/J+X32AWw <at> public.gmane.org:8080

doesn't change anything.

What can I do?

Thanks
    Mirto

P.S. the complete log:
(Continue reading)

Doodeff | 9 Feb 07:13
Picon
Favicon

Migration Problem "exceptions.AttributeError: manage_addTool"


Dear Community 

I'm migrating a Plone Site from the very old version 2.0.5 to the newest
version. Like many others as well, I have serious problems with the
migration step from 2.0.5 to 2.1.4. 

My setup: I deinstalled all products within the Plone Site Configuration and
moved the Data.fs to the new instance 2.1.4 which is installed on the same
Zope server (2.7.0) like the 2.0.5 instance. 

In the new instance I try to migrate via "plone_migration" and there I get
the following error: 

Starting the migration from version: 2.0.5 
Attempting to upgrade from: 2.0.5 
Upgrade aborted 
Error type: exceptions.AttributeError 
Error value: manage_addTool 
File "C:\Programme\Plone 2\Data\Products\CMFPlone\MigrationTool.py", line
274, in upgrade newv, msgs = self._upgrade(newv) 
File "C:\Programme\Plone 2\Data\Products\CMFPlone\MigrationTool.py", line
371, in _upgrade res = function(self.aq_parent) 
File "C:\Programme\Plone
2\Data\Products\CMFPlone\migrations\v2_1\alphas.py", line 65, in
two05_alpha1 installATContentTypes(portal, out) 
File "C:\Programme\Plone
2\Data\Products\CMFPlone\migrations\v2_1\alphas.py", line 273, in
installATContentTypes installOrReinstallProduct(portal, product_name, out) 
File "C:\Programme\Plone
(Continue reading)

Dominik | 10 Feb 14:32

buildout: register ZCML slugs other than 'configure', 'meta' or 'overrides'


Hi,

to activate iw.fss for the standard plone content type file, image and news
item the documentation recommends to add a slug with the line

<include package="iw.fss" file="atct.zcml" />

My idea was to add the line

zcml += iw.fss-atct

to my buildout.cfg so I don't have to create the file by hand.
But this dosn't work since plone.recipe-zope2instance only allows
'configure', 'meta' or 'overrides' zcml files and throws an exception

  File
"\buildout-cache\eggs\plone.recipe.zope2instance-3.3-py2.4.egg\plone\recipe\zope2
instance\__init__.py", line 655, in build_package_includes
    raise ValueError('Invalid zcml', orig)
ValueError: ('Invalid zcml', 'iw.fss-profiles')

So now my question is "is there an other way to create the slug with
buildout"?

thanks in advance
dominik
--

-- 
View this message in context: http://n2.nabble.com/buildout-register-ZCML-slugs-other-than-configure-meta-or-overrides-tp4547854p4547854.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.
(Continue reading)

Raphael Ritz | 10 Feb 15:02
Picon
Favicon

Re: Migration Problem "exceptions.AttributeError: manage_addTool"

Doodeff wrote:
> Dear Community 
> 
> I'm migrating a Plone Site from the very old version 2.0.5 to the newest
> version. Like many others as well, I have serious problems with the
> migration step from 2.0.5 to 2.1.4. 
> 
> My setup: I deinstalled all products within the Plone Site Configuration and
> moved the Data.fs to the new instance 2.1.4 which is installed on the same
> Zope server (2.7.0) like the 2.0.5 instance. 

Does your site start in debug mode or do you get any
errors when trying?

Raphael

> 
> In the new instance I try to migrate via "plone_migration" and there I get
> the following error: 
> 
> 
> 
> Starting the migration from version: 2.0.5 
> Attempting to upgrade from: 2.0.5 
> Upgrade aborted 
> Error type: exceptions.AttributeError 
> Error value: manage_addTool 
> File "C:\Programme\Plone 2\Data\Products\CMFPlone\MigrationTool.py", line
> 274, in upgrade newv, msgs = self._upgrade(newv) 
> File "C:\Programme\Plone 2\Data\Products\CMFPlone\MigrationTool.py", line
(Continue reading)

Raphael Ritz | 10 Feb 15:05
Picon
Favicon

Re: buildout: register ZCML slugs other than 'configure', 'meta' or 'overrides'

Dominik wrote:
> Hi,
> 
> to activate iw.fss for the standard plone content type file, image and news
> item the documentation recommends to add a slug with the line
> 
> <include package="iw.fss" file="atct.zcml" />
> 
> My idea was to add the line
> 
> zcml += iw.fss-atct
> 
> to my buildout.cfg so I don't have to create the file by hand.
> But this dosn't work since plone.recipe-zope2instance only allows
> 'configure', 'meta' or 'overrides' zcml files and throws an exception
> 
>   File
> "\buildout-cache\eggs\plone.recipe.zope2instance-3.3-py2.4.egg\plone\recipe\zope2
> instance\__init__.py", line 655, in build_package_includes
>     raise ValueError('Invalid zcml', orig)
> ValueError: ('Invalid zcml', 'iw.fss-profiles')
> 
> So now my question is "is there an other way to create the slug with
> buildout"?

Not that I would know.

But as soon as you have your own site/customization/whatever product
you could simply add that line to your own package's configure.zcml
file.
(Continue reading)

Graham Perrin | 10 Feb 15:42
Picon
Picon
Favicon

LDAP users can not rename or delete their own content in folders that they own


<http://www.wuala.com/Zope%20&%20Plone/Plone/2010/02/10/a/> screen shots
01--06 for a visual introduction to this problem. 

According to ZMI, 
ATFolder at /centrim/Members/gjp22  is owned by gjp22 (centrim/acl_users).

The CENTRIM site has read-only access to ldap.sussex.ac.uk 
and groups relating to this use of Plone are not stored on that LDAP server. 

gjp22 currently has contributor and member roles at 
/centrim/prefs_users_overview
(but for the majority of LDAP users, the norm is to have the Authenticated
role alone).

Focusing on the problem:

gjp22: 
 * is authenticated via LDAP
 * can add to  /centrim/Members/gjp22 (the folder owned by gjp22
(centrim/acl_users)).

gjp22 can NOT:

 * delete the items added by gjp22 at /centrim/Members/gjp22 
 * rename such items
 * see the Sharing tab at  /centrim/Members/gjp22
--

-- 
View this message in context: http://n2.nabble.com/LDAP-users-can-not-rename-or-delete-their-own-content-in-folders-that-they-own-tp4548248p4548248.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.
(Continue reading)


Gmane