Show-stopping migration problem with CMFPlacefulWorkflow (plone 3.1.2 to 3.2.2)

9 messages

Mat Ridley () Show-stopping migration problem with CMFPlacefulWorkflow (plone 3.1.2 to 3.2.2)

Reply Threaded

Can anybody shed any light on what might be going wrong with my
attempted migration from Plone 3.1.2 to 3.2.2? The core migration all
goes fine, but when I come to reinstall/update CMFPlacefulWorkflow (from
the versions that ship with those versions of Plone, 1.3.1 to 1.4.0), I
get a "'NoneType' object is not callable" error, with the following
traceback -

http://paste.plone.org/28775

This is a big problem for us, since we are heavily dependent on Placeful
Workflow... and it doesn't seem immediately obvious to me exactly where
to look to try to fix the error.

I've already tried updating the catalog before attempting the reinstall,
but with the same result. I can also confirm that Placeful Workflow
installs quite happily in a new Plone site on the same server, so there
must be something screwy in my database which is upsetting Placeful
Workflow - but I stumped as to where to start looking.

I've also had a go with Plone 3.3rc3 (and the Placeful Workflow 1.4.2
that comes with it), but get a similar error message.

Can anyone help?

Mat

Mat Ridley
IT Officer
Cambridge Theological Federation

------------------------------------------------------------------------------
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users

Raphael Ritz () Re: Show-stopping migration problem with CMFPlacefulWorkflow (plone 3.1.2 to 3.2.2)

Reply Threaded

Mat Ridley wrote:
> Can anybody shed any light on what might be going wrong with my
> attempted migration from Plone 3.1.2 to 3.2.2? The core migration all
> goes fine, but when I come to reinstall/update CMFPlacefulWorkflow (from
> the versions that ship with those versions of Plone, 1.3.1 to 1.4.0), I
> get a "'NoneType' object is not callable" error, with the following
> traceback -
>
> http://paste.plone.org/28775

More guessing than knowing but maybe you are hit
by a bug (or stupidity) of the quickinstaller tool.

On a backup/trial-and-error system you could try and
see what happens if you use 'portal_setup' to reapply
the profile of CMFPlacefulWorkflow instead of reinstalling
it via the quickinstaller (and don't worry if it then "thinks"
you should update it).

Also check the release notes on CMFPlacefulWorkflow to see
whether a reinstall/reload of profile is in fact necessary.

Or the other way around: do things work without reinstalling
or do you get any errors?

Raphael

>
> This is a big problem for us, since we are heavily dependent on Placeful
> Workflow... and it doesn't seem immediately obvious to me exactly where
> to look to try to fix the error.
>
> I've already tried updating the catalog before attempting the reinstall,
> but with the same result. I can also confirm that Placeful Workflow
> installs quite happily in a new Plone site on the same server, so there
> must be something screwy in my database which is upsetting Placeful
> Workflow - but I stumped as to where to start looking.
>
> I've also had a go with Plone 3.3rc3 (and the Placeful Workflow 1.4.2
> that comes with it), but get a similar error message.
>
> Can anyone help?
>
> Mat
>
>
> Mat Ridley
> IT Officer
> Cambridge Theological Federation
>
>
>
> ------------------------------------------------------------------------------

------------------------------------------------------------------------------
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users

Mat Ridley () Re: Show-stopping migration problem with CMFPlacefulWorkflow (plone 3.1.2 to 3.2.2)

Reply Threaded

Thanks for getting back to me...

I had a look around portal_setup, but couldn't seem to fix the problem
that way - I tried profiles > update base profile, but that had no
effect, but it didn't sound like it would. I also tried import > import
all steps for both the "current base profile" and the
CMFPlacefulWorkflow profiles, but both of these give me errors - a
slightly different one to the original message I was getting (see
http://paste.plone.org/28780), but still a "'NoneType' object is not
callable"...

I have also since found that the problem exists on my current Plone
3.1.2 site, and is probably not a migration problem per se; even if I
simply try to reinstall CMFPlacefulWorkflow in place, I still get the
same error. Having said that, I'm still no closer to understanding the
cause of the problem :-/

The release notes for CMFPlacefulWorkflow don't mention profiles at all
(at least, not that I could see)...

Despite the error message, there don't seem to be any obvious errors
when I assign a Placeful Workflow to a folder on my newly migrated site,
but of course I don't like the idea of leaving something up in the air
like that, especially not if it's something that might cause other
problems further down the line - so if you have any more suggestions,
I'd love to hear them...

Thanks again,

Mat

Mat Ridley
IT Officer
Cambridge Theological Federation

Raphael Ritz wrote:

> Mat Ridley wrote:
>> Can anybody shed any light on what might be going wrong with my
>> attempted migration from Plone 3.1.2 to 3.2.2? The core migration all
>> goes fine, but when I come to reinstall/update CMFPlacefulWorkflow (from
>> the versions that ship with those versions of Plone, 1.3.1 to 1.4.0), I
>> get a "'NoneType' object is not callable" error, with the following
>> traceback -
>>
>> http://paste.plone.org/28775
>
> More guessing than knowing but maybe you are hit
> by a bug (or stupidity) of the quickinstaller tool.
>
> On a backup/trial-and-error system you could try and
> see what happens if you use 'portal_setup' to reapply
> the profile of CMFPlacefulWorkflow instead of reinstalling
> it via the quickinstaller (and don't worry if it then "thinks"
> you should update it).
>
> Also check the release notes on CMFPlacefulWorkflow to see
> whether a reinstall/reload of profile is in fact necessary.
>
> Or the other way around: do things work without reinstalling
> or do you get any errors?
>
> Raphael
>
>
>> This is a big problem for us, since we are heavily dependent on Placeful
>> Workflow... and it doesn't seem immediately obvious to me exactly where
>> to look to try to fix the error.
>>
>> I've already tried updating the catalog before attempting the reinstall,
>> but with the same result. I can also confirm that Placeful Workflow
>> installs quite happily in a new Plone site on the same server, so there
>> must be something screwy in my database which is upsetting Placeful
>> Workflow - but I stumped as to where to start looking.
>>
>> I've also had a go with Plone 3.3rc3 (and the Placeful Workflow 1.4.2
>> that comes with it), but get a similar error message.
>>
>> Can anyone help?
>>
>> Mat
>>
>>
>> Mat Ridley
>> IT Officer
>> Cambridge Theological Federation
>>
>>
>>
>> ------------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Plone-Users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-users

Raphael Ritz () Re: Show-stopping migration problem with CMFPlacefulWorkflow (plone 3.1.2 to 3.2.2)

Reply Threaded

Mat Ridley wrote:

> Thanks for getting back to me...
>
> I had a look around portal_setup, but couldn't seem to fix the problem
> that way - I tried profiles > update base profile, but that had no
> effect, but it didn't sound like it would. I also tried import > import
> all steps for both the "current base profile" and the
> CMFPlacefulWorkflow profiles, but both of these give me errors - a
> slightly different one to the original message I was getting (see
> http://paste.plone.org/28780), but still a "'NoneType' object is not
> callable"...

I still think it's the issue with the quickinstaller deleting
component registrations on uninstall that are later not found
when needed on reinstall.

If you Google for the error message you should find it with
several different Plone add-ons :-(

If that's the case here as well that would be one more reason
to get rid of the QI ASAP.

In order to proceed you can try the following:

Compare the component registrations between two sites
- one where things work versus one where it's broken -
by going to the ZMI of the Plone site root and there
selecting the 'Components' tab. You'll see an XML file
listing the settings. Compare the two and report back.
(or simply copy over the file from the working to the
non-working site or manually fill in the missing pieces)

Does that reveal something?

Raphael

>
> I have also since found that the problem exists on my current Plone
> 3.1.2 site, and is probably not a migration problem per se; even if I
> simply try to reinstall CMFPlacefulWorkflow in place, I still get the
> same error. Having said that, I'm still no closer to understanding the
> cause of the problem :-/
>
> The release notes for CMFPlacefulWorkflow don't mention profiles at all
> (at least, not that I could see)...
>
> Despite the error message, there don't seem to be any obvious errors
> when I assign a Placeful Workflow to a folder on my newly migrated site,
> but of course I don't like the idea of leaving something up in the air
> like that, especially not if it's something that might cause other
> problems further down the line - so if you have any more suggestions,
> I'd love to hear them...
>
> Thanks again,
>
> Mat
>
>
> Mat Ridley
> IT Officer
> Cambridge Theological Federation
>
> Raphael Ritz wrote:
>> Mat Ridley wrote:
>>> Can anybody shed any light on what might be going wrong with my
>>> attempted migration from Plone 3.1.2 to 3.2.2? The core migration all
>>> goes fine, but when I come to reinstall/update CMFPlacefulWorkflow (from
>>> the versions that ship with those versions of Plone, 1.3.1 to 1.4.0), I
>>> get a "'NoneType' object is not callable" error, with the following
>>> traceback -
>>>
>>> http://paste.plone.org/28775
>> More guessing than knowing but maybe you are hit
>> by a bug (or stupidity) of the quickinstaller tool.
>>
>> On a backup/trial-and-error system you could try and
>> see what happens if you use 'portal_setup' to reapply
>> the profile of CMFPlacefulWorkflow instead of reinstalling
>> it via the quickinstaller (and don't worry if it then "thinks"
>> you should update it).
>>
>> Also check the release notes on CMFPlacefulWorkflow to see
>> whether a reinstall/reload of profile is in fact necessary.
>>
>> Or the other way around: do things work without reinstalling
>> or do you get any errors?
>>
>> Raphael
>>
>>
>>> This is a big problem for us, since we are heavily dependent on Placeful
>>> Workflow... and it doesn't seem immediately obvious to me exactly where
>>> to look to try to fix the error.
>>>
>>> I've already tried updating the catalog before attempting the reinstall,
>>> but with the same result. I can also confirm that Placeful Workflow
>>> installs quite happily in a new Plone site on the same server, so there
>>> must be something screwy in my database which is upsetting Placeful
>>> Workflow - but I stumped as to where to start looking.
>>>
>>> I've also had a go with Plone 3.3rc3 (and the Placeful Workflow 1.4.2
>>> that comes with it), but get a similar error message.
>>>
>>> Can anyone help?
>>>
>>> Mat
>>>
>>>
>>> Mat Ridley
>>> IT Officer
>>> Cambridge Theological Federation
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Plone-Users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/plone-users
>
> ------------------------------------------------------------------------------

Mat Ridley () Re: Show-stopping migration problem with CMFPlacefulWorkflow (plone 3.1.2 to 3.2.2)

Reply Threaded

Thanks again for the advice... but still no luck. I took a look at the
component XML information for both my current site and a new test site
on which installing Placeful Workflow works fine, and the only items
which are unique to my broken site are -

- a line corresponding to a customised footer
- a line corresponding to Placeful Workflow, which is either there or
not there depending on whether or not Quick Installer thinks the product
is installed -

<utility
interface="Products.CMFPlacefulWorkflow.interfaces.portal_placeful_workflow.IPlacefulWorkflowTool"
object="portal_placeful_workflow"/>

- a line to do with kss, the purpose of which I am not quite sure about -

<utility
interface="Products.ResourceRegistries.interfaces.registries.IKSSRegistry"
object="portal_kss"/>

I've tried uninstalling Placeful Workflow, removing the customised
footer, and just replacing the entire XML file on the broken site with
that from the working site, but unfortunately, it doesn't make any
difference :-(

Any more ideas?

Mat

Mat Ridley
IT Officer
Cambridge Theological Federation

Raphael Ritz wrote:

> Mat Ridley wrote:
>> Thanks for getting back to me...
>>
>> I had a look around portal_setup, but couldn't seem to fix the problem
>> that way - I tried profiles > update base profile, but that had no
>> effect, but it didn't sound like it would. I also tried import > import
>> all steps for both the "current base profile" and the
>> CMFPlacefulWorkflow profiles, but both of these give me errors - a
>> slightly different one to the original message I was getting (see
>> http://paste.plone.org/28780), but still a "'NoneType' object is not
>> callable"...
>
> I still think it's the issue with the quickinstaller deleting
> component registrations on uninstall that are later not found
> when needed on reinstall.
>
> If you Google for the error message you should find it with
> several different Plone add-ons :-(
>
> If that's the case here as well that would be one more reason
> to get rid of the QI ASAP.
>
> In order to proceed you can try the following:
>
> Compare the component registrations between two sites
> - one where things work versus one where it's broken -
> by going to the ZMI of the Plone site root and there
> selecting the 'Components' tab. You'll see an XML file
> listing the settings. Compare the two and report back.
> (or simply copy over the file from the working to the
> non-working site or manually fill in the missing pieces)
>
> Does that reveal something?
>
> Raphael
>
>
>> I have also since found that the problem exists on my current Plone
>> 3.1.2 site, and is probably not a migration problem per se; even if I
>> simply try to reinstall CMFPlacefulWorkflow in place, I still get the
>> same error. Having said that, I'm still no closer to understanding the
>> cause of the problem :-/
>>
>> The release notes for CMFPlacefulWorkflow don't mention profiles at all
>> (at least, not that I could see)...
>>
>> Despite the error message, there don't seem to be any obvious errors
>> when I assign a Placeful Workflow to a folder on my newly migrated site,
>> but of course I don't like the idea of leaving something up in the air
>> like that, especially not if it's something that might cause other
>> problems further down the line - so if you have any more suggestions,
>> I'd love to hear them...
>>
>> Thanks again,
>>
>> Mat
>>
>>
>> Mat Ridley
>> IT Officer
>> Cambridge Theological Federation
>>
>> Raphael Ritz wrote:
>>> Mat Ridley wrote:
>>>> Can anybody shed any light on what might be going wrong with my
>>>> attempted migration from Plone 3.1.2 to 3.2.2? The core migration all
>>>> goes fine, but when I come to reinstall/update CMFPlacefulWorkflow (from
>>>> the versions that ship with those versions of Plone, 1.3.1 to 1.4.0), I
>>>> get a "'NoneType' object is not callable" error, with the following
>>>> traceback -
>>>>
>>>> http://paste.plone.org/28775
>>> More guessing than knowing but maybe you are hit
>>> by a bug (or stupidity) of the quickinstaller tool.
>>>
>>> On a backup/trial-and-error system you could try and
>>> see what happens if you use 'portal_setup' to reapply
>>> the profile of CMFPlacefulWorkflow instead of reinstalling
>>> it via the quickinstaller (and don't worry if it then "thinks"
>>> you should update it).
>>>
>>> Also check the release notes on CMFPlacefulWorkflow to see
>>> whether a reinstall/reload of profile is in fact necessary.
>>>
>>> Or the other way around: do things work without reinstalling
>>> or do you get any errors?
>>>
>>> Raphael
>>>
>>>
>>>> This is a big problem for us, since we are heavily dependent on Placeful
>>>> Workflow... and it doesn't seem immediately obvious to me exactly where
>>>> to look to try to fix the error.
>>>>
>>>> I've already tried updating the catalog before attempting the reinstall,
>>>> but with the same result. I can also confirm that Placeful Workflow
>>>> installs quite happily in a new Plone site on the same server, so there
>>>> must be something screwy in my database which is upsetting Placeful
>>>> Workflow - but I stumped as to where to start looking.
>>>>
>>>> I've also had a go with Plone 3.3rc3 (and the Placeful Workflow 1.4.2
>>>> that comes with it), but get a similar error message.
>>>>
>>>> Can anyone help?
>>>>
>>>> Mat
>>>>
>>>>
>>>> Mat Ridley
>>>> IT Officer
>>>> Cambridge Theological Federation
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Plone-Users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/plone-users
>> ------------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Plone-Users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-users

Maurits van Rees-3 () Re: Show-stopping migration problem with CMFPlacefulWorkflow (plone 3.1.2 to 3.2.2)

Reply Threaded

Mat Ridley, on 2009-07-03:

>
> Thanks again for the advice... but still no luck. I took a look at the
> component XML information for both my current site and a new test site
> on which installing Placeful Workflow works fine, and the only items
> which are unique to my broken site are -
>
> - a line corresponding to a customised footer
> - a line corresponding to Placeful Workflow, which is either there or
> not there depending on whether or not Quick Installer thinks the product
> is installed -
>
> <utility
> interface="Products.CMFPlacefulWorkflow.interfaces.portal_placeful_workflow.IPlacefulWorkflowTool"
> object="portal_placeful_workflow"/>
>
> - a line to do with kss, the purpose of which I am not quite sure about -
>
> <utility
> interface="Products.ResourceRegistries.interfaces.registries.IKSSRegistry"
> object="portal_kss"/>
>
> I've tried uninstalling Placeful Workflow, removing the customised
> footer, and just replacing the entire XML file on the broken site with
> that from the working site, but unfortunately, it doesn't make any
> difference :-(
>
> Any more ideas?

If you feel comfortable with a python debugging prompt you could add
Products.PDBDebugMode to the eggs of your buildout, start the
instance in the foreground, reinstall placeful workflow and poke
around in the prompt when the error shows up. That might give you
more info about why the NoneType object is None.

Maybe the Products.CMFPlacefulWorkflow egg is broken on your local
machine; you can try deleting it and then rerun buildout. Hm, but it
goes wrong in Plone 3.1.2 already for you so that should not work...

Long shot: go to the Zope root (so outside of the Plone Site), then
the Control_Panel, remove all items from the Products section and
restart the instance.

Strange error...

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

------------------------------------------------------------------------------
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users

Raphael Ritz () Re: Show-stopping migration problem with CMFPlacefulWorkflow (plone 3.1.2 to 3.2.2)

Reply Threaded

Maurits van Rees wrote:

>
> Strange error...
>

Strange indeed.

And what starts to worry me is that it happens with various
different products on reinstall it seems. Just google for

"Module Products.GenericSetup.tool, line 128, in importToolset"

and see what turns up.

My current goes is that QI screws things up, maybe if products
manage their dependencies on install? (really just guessing)

At least I'd be surprised by now if the issue here would turn
out to be CMFPlacefulWorkflow related but I'd love to be proven
wrong.

Raphael

------------------------------------------------------------------------------
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users

Mat Ridley () Re: Show-stopping migration problem with CMFPlacefulWorkflow (plone 3.1.2 to 3.2.2)

Reply Threaded

Well, I tried Maurits' (extreme-sounding!) suggestion to reinstall the
products across the whole zope instance, but still no joy I'm afraid...
and I wouldn't even know how to begin with debug mode. However, what I
can do is to provide a stripped down copy of my Data.fs to anyone who
might be involved with maintaining Quick Installer, in case this is
useful in trying to track down/reproduce the bug. It's about 5MB. Just
let me know...

In the meantime, I'm working around the bug by creating a fresh Plone
site, and migrating all my users/content across to it. So far so good...

Thanks again for the feedback and the help!

Mat

Mat Ridley
IT Officer
Cambridge Theological Federation

Raphael Ritz wrote:

> Maurits van Rees wrote:
>
>> Strange error...
>>
>
> Strange indeed.
>
> And what starts to worry me is that it happens with various
> different products on reinstall it seems. Just google for
>
> "Module Products.GenericSetup.tool, line 128, in importToolset"
>
> and see what turns up.
>
> My current goes is that QI screws things up, maybe if products
> manage their dependencies on install? (really just guessing)
>
> At least I'd be surprised by now if the issue here would turn
> out to be CMFPlacefulWorkflow related but I'd love to be proven
> wrong.
>
> Raphael
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Plone-Users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-users

Burleigh, Matt () Re: Show-stopping migration problem with CMFPlacefulWorkflow (plone 3.1.2 to 3.2.2)

Reply Threaded

In reply to this post by Mat Ridley

Make sure you have all the Plone stock workflows in place.

On 7/2/09 12:01 PM, "Mat Ridley" <[hidden email]> wrote:

>
> Thanks for getting back to me...
>
> I had a look around portal_setup, but couldn't seem to fix the problem
> that way - I tried profiles > update base profile, but that had no
> effect, but it didn't sound like it would. I also tried import > import
> all steps for both the "current base profile" and the
> CMFPlacefulWorkflow profiles, but both of these give me errors - a
> slightly different one to the original message I was getting (see
> http://paste.plone.org/28780), but still a "'NoneType' object is not
> callable"...
>
> I have also since found that the problem exists on my current Plone
> 3.1.2 site, and is probably not a migration problem per se; even if I
> simply try to reinstall CMFPlacefulWorkflow in place, I still get the
> same error. Having said that, I'm still no closer to understanding the
> cause of the problem :-/
>
> The release notes for CMFPlacefulWorkflow don't mention profiles at all
> (at least, not that I could see)...
>
> Despite the error message, there don't seem to be any obvious errors
> when I assign a Placeful Workflow to a folder on my newly migrated site,
> but of course I don't like the idea of leaving something up in the air
> like that, especially not if it's something that might cause other
> problems further down the line - so if you have any more suggestions,
> I'd love to hear them...
>
> Thanks again,
>
> Mat
>
>
> Mat Ridley
> IT Officer
> Cambridge Theological Federation
>
> Raphael Ritz wrote:
>> Mat Ridley wrote:
>>> Can anybody shed any light on what might be going wrong with my
>>> attempted migration from Plone 3.1.2 to 3.2.2? The core migration all
>>> goes fine, but when I come to reinstall/update CMFPlacefulWorkflow (from
>>> the versions that ship with those versions of Plone, 1.3.1 to 1.4.0), I
>>> get a "'NoneType' object is not callable" error, with the following
>>> traceback -
>>>
>>> http://paste.plone.org/28775
>>
>> More guessing than knowing but maybe you are hit
>> by a bug (or stupidity) of the quickinstaller tool.
>>
>> On a backup/trial-and-error system you could try and
>> see what happens if you use 'portal_setup' to reapply
>> the profile of CMFPlacefulWorkflow instead of reinstalling
>> it via the quickinstaller (and don't worry if it then "thinks"
>> you should update it).
>>
>> Also check the release notes on CMFPlacefulWorkflow to see
>> whether a reinstall/reload of profile is in fact necessary.
>>
>> Or the other way around: do things work without reinstalling
>> or do you get any errors?
>>
>> Raphael
>>
>>
>>> This is a big problem for us, since we are heavily dependent on Placeful
>>> Workflow... and it doesn't seem immediately obvious to me exactly where
>>> to look to try to fix the error.
>>>
>>> I've already tried updating the catalog before attempting the reinstall,
>>> but with the same result. I can also confirm that Placeful Workflow
>>> installs quite happily in a new Plone site on the same server, so there
>>> must be something screwy in my database which is upsetting Placeful
>>> Workflow - but I stumped as to where to start looking.
>>>
>>> I've also had a go with Plone 3.3rc3 (and the Placeful Workflow 1.4.2
>>> that comes with it), but get a similar error message.
>>>
>>> Can anyone help?
>>>
>>> Mat
>>>
>>>
>>> Mat Ridley
>>> IT Officer
>>> Cambridge Theological Federation
>>>
>>>
>>>
>>> ----------------------------------------------------------------------------
>>> --
>>
>>
>>

----------------------------------------------------------------------------->>
-

>> _______________________________________________
>> Plone-Users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/plone-users
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Plone-Users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-users

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users