Migration from 2.5.1 to 3.1.7 dies.

I am trying to migrate a vanilla Plone site with quite a bit of content
from 2.5.1 (the default Debian 4.0 Plone install on an Itanium CPU
system) to Plone 3.1.7 on Debian on Intel installed by the Unified
Installer.

I uninstalled all of the products and packed the database.  The
migration dies after making it to 2.5.2. 

http://paste.plone.org/25175

Thanks!

Re: Migration from 2.5.1 to 3.1.7 dies.

> I am trying to migrate a vanilla Plone site with quite a bit of content
> from 2.5.1 (the default Debian 4.0 Plone install on an Itanium CPU
> system) to Plone 3.1.7 on Debian on Intel installed by the Unified

That is exactly what I will need to do soon.

> I uninstalled all of the products and packed the database.  The
> migration dies after making it to 2.5.2.
>
> http://paste.plone.org/25175

Look at this solution that solved this problem for me a year ago:

"The reason is that two MIME types are missing from the mimetypes_registry. To 
correct the issue, add the MIME types:

   1. In the ZMI, go to the root of your Plone site.
   2. Go into the mimetypes_registry
   3. At the top of that sreen is a button to Add a New MIME type. Click that.
   4. In the resulting screen, complete that form. I believe the only fields 
that are required are Name and mime-types.
   5. In name, enter a name of your choice.
   6. In mime-type, enter: text/x-web-markdown
   7. Repeat steps 5 and 6, except for mime-type, enter: text/x-web-textile 
   8. Re-export the site and the import to the new instance should now succeed 
(at least it did for me ).

Source: https://weblion.psu.edu/trac/weblion/wiki/PloneTroubleshooting

Did it help?

Re: Migration from 2.5.1 to 3.1.7 dies.

---- Original Message ----
From: Milos Prudek <prudek-//zWVuv0bFo@public.gmane.org>
Look at this solution that solved this problem for me a year ago:

"The reason is that two MIME types are missing from the mimetypes_registry. To
correct the issue, add the MIME types:

   1. In the ZMI, go to the root of your Plone site.
   2. Go into the mimetypes_registry
   3. At the top of that sreen is a button to Add a New MIME type. Click that.
   4. In the resulting screen, complete that form. I believe the only fields
that are required are Name and mime-types.
   5. In name, enter a name of your choice.
   6. In mime-type, enter: text/x-web-markdown
   7. Repeat steps 5 and 6, except for mime-type, enter: text/x-web-textile
   8. Re-export the site and the import to the new instance should now succeed
(at least it did for me ).

Source: https://weblion.psu.edu/trac/weblion/wiki/PloneTroubleshooting

Did it help?

OK, I did that and the problem changed:

• Dry run selected.
• Starting the migration from version: 2.5.1
• Attempting to upgrade from: 2.5.1
• Registered tools as utilities.
• Changed credentials_cookie_path login_path property to 'require_login'.
• Upgrade to: 2.5.2-rc1, completed
• Attempting to upgrade from: 2.5.2-rc1
• Upgrade to: 2.5.2, completed
• Attempting to upgrade from: 2.5.2
• Added `text/x-web-markdown` and `text/x-web-textile`.
• Upgrade to: 2.5.3-rc1, completed
• Attempting to upgrade from: 2.5.3-rc1
• Upgrade to: 2.5.3-final, completed
• Attempting to upgrade from: 2.5.3-final
• Set plone GS profile as default
• Upgrade to: 2.5.4-final, completed
• Attempting to upgrade from: 2.5.4-final
• Upgrade to: 2.5.4-2, completed
• Attempting to upgrade from: 2.5.4-2
• Upgrade to: 2.5.5, completed
• Attempting to upgrade from: 2.5.5
• Upgrade aborted
• Error type: zExceptions.BadRequest
• Error value: ('Empty or invalid id specified', '')
• File "/home/paul/Plone-3.1.7/zinstance/parts/plone/CMFPlone/MigrationTool.py", line 210, in upgrade newv, msgs = self._upgrade(newv)
• File "/home/paul/Plone-3.1.7/zinstance/parts/plone/CMFPlone/MigrationTool.py", line 321, in _upgrade res = function(self.aq_parent)
• File "/home/paul/Plone-3.1.7/zinstance/parts/plone/CMFPlone/migrations/v3_0/alphas.py", line 100, in three0_alpha1 migrateOldActions(portal, out)
• File "/home/paul/Plone-3.1.7/zinstance/parts/plone/CMFPlone/migrations/v3_0/alphas.py", line 425, in migrateOldActions portal.portal_actions._setObject(category, ActionCategory(id=category))
• File "/home/paul/Plone-3.1.7/zinstance/parts/zope2/lib/python/OFS/ObjectManager.py", line 314, in _setObject v = self._checkId(id)
• File "/home/paul/Plone-3.1.7/zinstance/parts/zope2/lib/python/OFS/ObjectManager.py", line 81, in checkValidId raise BadRequest, ('Empty or invalid id specified', id)
• End of upgrade path, migration has finished
• The upgrade path did NOT reach current version
• Migration has failed
• Dry run selected, transaction aborted

Any suggestions?

Re: Migration from 2.5.1 to 3.1.7 dies.

> OK, I did that and the problem changed:

Well, I cannot take you any further. I have no experience upgrading beyond 
Plone 2.5.2, and none about Plone debugging.

Someone else will have to step in.

--

-- 
Milos Prudek

varnish via buildout error

Re: varnish via buildout error

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Plone-Users mailing list
Plone-Users@...
https://lists.sourceforge.net/lists/listinfo/plone-users

Re: Items missing from Personal Bar

Jacques,

Thanks very much for posting this solution!
It worked for me like a charm.

Now I must go pick up tufts of hair that are laying around from before I
read your post.

Charles

OmicroN wrote:
> 
> To resolve your problem try this :
> 
> Goto '/root/portal_actions/user'
> Add a 'CMF Action' and complete :
>   UID = 'mystuff'
>   Title = 'My Folder'
>   I18n Domain = 'plone'
>   URL = 'string:${portal/portal_membership/getHomeUrl}'
>   Condition = 'python:(member is not None) and
> (portal.portal_membership.getHomeFolder() is not None)'
>   Permissions = 'View'
>   Visible  checked
> 
> Jacques
> 
> 
> 
> AndyH wrote:
>> 
>> Good afternoon!
>> 
>> Working with Plone 3.1.6, trying to get it up and going for a school
>> district.  Have it installed, up and running on an Ubuntu server.  It
>> looks pretty good, although I'm still working out some kinks.  One issue
>> that I know I need to get resolved is that, when a user logs in, we are
>> missing the "My Folder" from the personal bar, along with something else
>> - all we have is the username and log out.
>> 
>> I've gone through all the settings, etc. and it looks to be set right,
>> but I'm sure there's something I am missing.  I set up a whole new Plone
>> site on the same server, and the same issue was there.  The server does
>> create the folder in "Users," but there isn't a clean way for the user to
>> access the folder.
>> 
>> Thanks.
>> 
>> Andy
>> 
> 
> 

--

-- 
View this message in context: http://n2.nabble.com/Items-missing-from-Personal-Bar-tp1360939p1607011.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.

setup error on win xp: calls different pythonwin

Unified Installer vs Source

Re: Unified Installer vs Source

I presume when you say "integrates further than necessary" you're
referring to a separate python?  I'm not sure though, from the literal
interpretation of what you write.

Steve McMahon says: "Platform packages have been of uneven quality and
have used installation trees that make it difficult for the community
to offer help when problems occur. Also, platform packages have
historically been vulnerable to changes in the system Python. Zope/
Plone is very picky about the version of Python used to run it, and an
update of the system Python when some other item is installed can
easily break Zope/Plone. At this point, you may be thinking that this
just means that the packages have poorly specified dependencies. The
Unified Installer was created because generation after generation of
packages did not solve this problem." from
http://plone.org/documentation/tutorial/installing-plone-3-with-the-unified-installer

I've never had any problems with the installer on win32 ubuntu
opensolaris.  And I've tested many instances of each operating
system.  So, the advantage of using the Unified Installer is that it
saves time.  If you want a standard installation then saving time is a
good thing.  Dale

On Dec 3, 8:18 pm, moncho <monflo...@...> wrote:
> Someone could explain what is the advantage of using the Unified Installer, which already integrates
further than necessary.
>
> How is the upgrade?
> the Unified Installer is reliable and safe to take an online system?
>
> Would greatly appreciate your comments.
>
> Thank you very much
>
> _______________________________________________
> Setup mailing list
> Se...@...://lists.plone.org/mailman/listinfo/setup