Re: [Zope-PAS] Problems Upgrading PluggableAuthService

2008-02-01 Thread Stefan H. Holek
Follow the steps outlined in http://plone.org/documentation/how-to/ 
debug-unauthorized (don't miss the comments further down the page).


Stefan


On 30. Jän 2008, at 17:39, Mark Phillips wrote:

I am reading the "How to debug Plone" using pdb, but I don't know  
where

to start with a break point. I don't know the process for login in
plone/zope. Any tutorials on that? I couldn't find any.


--
Anything that happens, happens.  --Douglas Adams


___
Zope-PAS mailing list
Zope-PAS@zope.org
http://mail.zope.org/mailman/listinfo/zope-pas


Re: [Zope-PAS] Problems Upgrading PluggableAuthService

2008-01-31 Thread Mark Phillips
On Thu, 2008-01-31 at 04:49 -0500, Sven Deichmann wrote:
> Hello... I'm afraid that was my fault... I added that comment to the
> issue without checking all results first. I already added a comment
> yesterday stating this problem. My recommendation now: stick with
> 1.4.2
> and add the patch listed in the comments further up. Should be the
> fastest solution. Though it would be great to know, why 1.5.2 does not
> work...
> 

Steve,

Thanks for the update. 

However, when I "downgraded" from PluggableAuthService 1.5.2 to
PluggableAuthService 1.4.2 with the patch, the portrait problem did not
go away. Does PluggableAuthService 1.5.2 make other changes? This is
what I did:

1. Stopped Zope
2. Removed PluggableAuthService 1.5.2 from Product
3. Added PluggableAuthService 1.4.2 to Products
4. Applied the patch: patch -p0 < the-patch inside the
PluggableAuthService directory 
4.5 Checked that the patch was applied - it was
5. Restarted Zope

I can now log in, but when I try to add a portrait to a member's
account, I get this error when I try to add a gif or jpeg image file:

2008-01-31T06:18:54 ERROR Zope.SiteErrorLog
http://hammerhead:8081/ahs/newspaper/personalize_form
Traceback (innermost last):
  Module ZPublisher.Publish, line 115, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 41, in call_object
  Module Products.CMFFormController.FSControllerPageTemplate, line 90,
in __call__
  Module Products.CMFFormController.BaseControllerPageTemplate, line 28,
in _call
  Module Products.CMFFormController.ControllerBase, line 244, in getNext
  Module Products.CMFFormController.Actions.TraverseTo, line 38, in
__call__
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 41, in call_object
  Module Products.CMFFormController.FSControllerPythonScript, line 104,
in __call__
  Module Products.CMFFormController.Script, line 145, in __call__
  Module Products.CMFCore.FSPythonScript, line 108, in __call__
  Module Shared.DC.Scripts.Bindings, line 311, in __call__
  Module Shared.DC.Scripts.Bindings, line 348, in _bindAndExec
  Module Products.CMFCore.FSPythonScript, line 164, in _exec
  Module None, line 31, in personalize
   - 
   - Line 31
  Module Products.PlonePAS.tools.membership, line 449, in
changeMemberPortrait
  Module Products.CMFPlone.MembershipTool, line 182, in
changeMemberPortrait
  Module Products.CMFPlone.utils, line 729, in scale_image
  Module PIL.Image, line 1916, in open
IOError: cannot identify image file

Did the upgrade to PluggableAuthService 1.5.2 make any changes to my
site so that a simple downgrade as I described will not work? Any
thoughts on how I can get portraits to work? How can I turn off
portraits?

As a side note, while using PluggableAuthService 1.5.2, I also tried
upgrading to Five 1.4.4 as one of the posts suggested, and I could not
log in. However, I got this error:

2008-01-30T20:33:00 ERROR Zope.SiteErrorLog
http://hammerhead:8081/ahs/newspaper/login_form
Traceback (innermost last):
  Module ZPublisher.Publish, line 115, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 41, in call_object
  Module Products.CMFFormController.FSControllerPageTemplate, line 90,
in __call__
  Module Products.CMFFormController.BaseControllerPageTemplate, line 28,
in _call
  Module Products.CMFFormController.ControllerBase, line 244, in getNext
  Module Products.CMFFormController.Actions.TraverseTo, line 38, in
__call__
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 41, in call_object
  Module Products.CMFFormController.FSControllerPythonScript, line 104,
in __call__
  Module Products.CMFFormController.Script, line 145, in __call__
  Module Products.CMFCore.FSPythonScript, line 108, in __call__
  Module Shared.DC.Scripts.Bindings, line 311, in __call__
  Module Shared.DC.Scripts.Bindings, line 348, in _bindAndExec
  Module Products.CMFCore.FSPythonScript, line 164, in _exec
  Module None, line 27, in logged_in
   - 
   - Line 27
  Module Products.CMFPlone.MembershipTool, line 572, in setLoginTimes
  Module Products.remember.content.member, line 298, in setProperties
Unauthorized: 

Not sure if it means anything.

Mark
___
Zope-PAS mailing list
Zope-PAS@zope.org
http://mail.zope.org/mailman/listinfo/zope-pas


Re: [Zope-PAS] Problems Upgrading PluggableAuthService

2008-01-31 Thread Jens Vagelpohl


On Jan 31, 2008, at 10:49 , Sven Deichmann wrote:


Hello... I'm afraid that was my fault... I added that comment to the
issue without checking all results first. I already added a comment
yesterday stating this problem. My recommendation now: stick with  
1.4.2

and add the patch listed in the comments further up. Should be the
fastest solution. Though it would be great to know, why 1.5.2 does not
work...


Next time you reply to a digest message please take a second to trim  
the 2 miles of irrelevant quoted text. Thanks.


jens


___
Zope-PAS mailing list
Zope-PAS@zope.org
http://mail.zope.org/mailman/listinfo/zope-pas


Re: [Zope-PAS] Problems Upgrading PluggableAuthService

2008-01-31 Thread Sven Deichmann

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello... I'm afraid that was my fault... I added that comment to the
issue without checking all results first. I already added a comment
yesterday stating this problem. My recommendation now: stick with 1.4.2
and add the patch listed in the comments further up. Should be the
fastest solution. Though it would be great to know, why 1.5.2 does not
work...


Regards,
Sven Deichmann

[EMAIL PROTECTED] schrieb:
| Send Zope-PAS mailing list submissions to
|   zope-pas@zope.org
|
| To subscribe or unsubscribe via the World Wide Web, visit
|   http://mail.zope.org/mailman/listinfo/zope-pas
| or, via email, send a message with subject or body 'help' to
|   [EMAIL PROTECTED]
|
| You can reach the person managing the list at
|   [EMAIL PROTECTED]
|
| When replying, please edit your Subject line so it is more specific
| than "Re: Contents of Zope-PAS digest..."
|
|
| Today's Topics:
|
|1. Problems Upgrading PluggableAuthService (Mark Phillips)
|2. Re: Problems Upgrading PluggableAuthService (Jens Vagelpohl)
|3. Re: Problems Upgrading PluggableAuthService (Mark Phillips)
|4. Re: Problems Upgrading PluggableAuthService (Jens Vagelpohl)
|
|
| --
|
| Message: 1
| Date: Wed, 30 Jan 2008 06:01:09 -0700
| From: Mark Phillips <[EMAIL PROTECTED]>
| Subject: [Zope-PAS] Problems Upgrading PluggableAuthService
| To: zope-pas@zope.org
| Message-ID: <[EMAIL PROTECTED]>
| Content-Type: text/plain
|
| I have a plone site running:
|
| Plone 2.5.5,
| CMF-1.6.4,
| Zope (Zope 2.9.8-final, python 2.4.4, freebsd6),
| Five 1.4.2,
| Python 2.4.4 (#2, Sep 26 2007, 13:07:27) [GCC 3.4.6 [FreeBSD]
| 20060305],
| PIL 1.1.6
| membrane 1.0
| remember 1.0
| PluggableAuthService-1.4.2
|
| The members cannot add portraits to the site, and I get the error
| "ValueError: Property portrait: unknown type"
| when I do a search for all users in site setup.
|
| I looked at the bug reports and found 2 that relate to this error:
| http://plone.org/products/remember/issues/44
| http://plone.org/products/remember/issues/32
|
| The suggested solution is to upgrade
| PluggableAuthService to version 1.5.2, which I did. I stopped zope,
| removed PluggableAuthService v 1.4.2 from the Products directory,
| installed the new PluggableAuthService v 1.5.2, and restarted zope.
|
| However, no one can log in now. The remember members are still alive
| and well, but entering the use name and password does nothing -
| no error, no logged event, just return to the login page.
|
| What else do I have to do to upgrade PluggableAuthService?
|
| Thanks!
|
| Mark
|
|
| --
|
| Message: 2
| Date: Wed, 30 Jan 2008 14:50:11 +0100
| From: Jens Vagelpohl <[EMAIL PROTECTED]>
| Subject: Re: [Zope-PAS] Problems Upgrading PluggableAuthService
| To: zope-pas@zope.org
| Message-ID: <[EMAIL PROTECTED]>
| Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
|
|
| On Jan 30, 2008, at 14:01 , Mark Phillips wrote:
|> I looked at the bug reports and found 2 that relate to this error:
|> http://plone.org/products/remember/issues/44
|> http://plone.org/products/remember/issues/32
|>
|> The suggested solution is to upgrade
|> PluggableAuthService to version 1.5.2, which I did. I stopped zope,
|> removed PluggableAuthService v 1.4.2 from the Products directory,
|> installed the new PluggableAuthService v 1.5.2, and restarted zope.
|>
|> However, no one can log in now. The remember members are still alive
|> and well, but entering the use name and password does nothing -
|> no error, no logged event, just return to the login page.
|>
|> What else do I have to do to upgrade PluggableAuthService?
|
| There are no additional steps.
|
| In a case like this I would start by manually inspecting the user
| folder instance to make sure the plugin registrations are still
| correct. It may help to enable the verbose-security setting in
| zope.conf and remove "Unauthorized" from the swallowed exceptions in
| the error_log object in the ZMI, you may get tracebacks that point to
| the issue then. If that doesn't provide enough clues I would use the
| Python debugger to step through the login process.
|
| jens
|
|
|
|
| ------
|
| Message: 3
| Date: Wed, 30 Jan 2008 07:40:23 -0700
| From: Mark Phillips <[EMAIL PROTECTED]>
| Subject: Re: [Zope-PAS] Problems Upgrading PluggableAuthService
| To: Jens Vagelpohl <[EMAIL PROTECTED]>
| Cc: zope-pas@zope.org
| Message-ID: <[EMAIL PROTECTED]>
| Content-Type: text/plain
|
| On Wed, 2008-01-30 at 08:50 -0500, Jens Vagelpohl wrote:
|> On Jan 30, 2008, at 14:01 , Mark Phillips wrote:
|>> I looked at the bug reports and found 2 that relate to this error:
|>> http://plone.org/products/remember/issues/44
|>> 

Re: [Zope-PAS] Problems Upgrading PluggableAuthService

2008-01-30 Thread Mark Phillips
On Wed, 2008-01-30 at 12:06 -0500, Jens Vagelpohl wrote:
> 
> On Jan 30, 2008, at 17:39 , Mark Phillips wrote:
> > I figured out where the plugins are - acl_users for my plone site,
> not
> > the root level acl_users, right?
> 
> Plone has the annoying habit of replacing the root user folder as 
> well, so it might be helpful to look there as well.

They are the same
> 
> 
> > I then removed Unauthorized from the swallowed exceptions, and added
> > verbose-security to zope.conf. I then tried to login, and no error
> > messages.
> >
> > I am reading the "How to debug Plone" using pdb, but I don't know 
> > where
> > to start with a break point. I don't know the process for login in
> > plone/zope. Any tutorials on that? I couldn't find any.
> 
> I can't say much about Plone, but in many cases you can "follow the 
> code" by looking at the source of that login page. From there you see 
> where it posts to, and what code is invoked to check credentials, or 
> which conditions must be met for the login page to be shown again,
> etc.
> 
> You may find more helpful answers by asking on a Plone-specific list, 
> by the way.

I have, but no response..

Thanks for your help!!

Mark
> 
> jens
> 
> 
> 
> ___
> Zope-PAS mailing list
> Zope-PAS@zope.org
> http://mail.zope.org/mailman/listinfo/zope-pas
> 
> 
___
Zope-PAS mailing list
Zope-PAS@zope.org
http://mail.zope.org/mailman/listinfo/zope-pas


Re: [Zope-PAS] Problems Upgrading PluggableAuthService

2008-01-30 Thread Jens Vagelpohl


On Jan 30, 2008, at 17:39 , Mark Phillips wrote:

I figured out where the plugins are - acl_users for my plone site, not
the root level acl_users, right?


Plone has the annoying habit of replacing the root user folder as  
well, so it might be helpful to look there as well.




I then removed Unauthorized from the swallowed exceptions, and added
verbose-security to zope.conf. I then tried to login, and no error
messages.

I am reading the "How to debug Plone" using pdb, but I don't know  
where

to start with a break point. I don't know the process for login in
plone/zope. Any tutorials on that? I couldn't find any.


I can't say much about Plone, but in many cases you can "follow the  
code" by looking at the source of that login page. From there you see  
where it posts to, and what code is invoked to check credentials, or  
which conditions must be met for the login page to be shown again, etc.


You may find more helpful answers by asking on a Plone-specific list,  
by the way.


jens



___
Zope-PAS mailing list
Zope-PAS@zope.org
http://mail.zope.org/mailman/listinfo/zope-pas


Re: [Zope-PAS] Problems Upgrading PluggableAuthService

2008-01-30 Thread Jens Vagelpohl


On Jan 30, 2008, at 15:40 , Mark Phillips wrote:

In a case like this I would start by manually inspecting the user
folder instance to make sure the plugin registrations are still
correct.


How do I do this? Through the ZMI? My apologies for being so new to
zope.


Yes.



It may help to enable the verbose-security setting in
zope.conf and remove "Unauthorized" from the swallowed exceptions in
the error_log object in the ZMI,
you may get tracebacks that point to
the issue then. If that doesn't provide enough clues I would use the
Python debugger to step through the login process.

jens


Thanks. I tried


And..?

jens



___
Zope-PAS mailing list
Zope-PAS@zope.org
http://mail.zope.org/mailman/listinfo/zope-pas


Re: [Zope-PAS] Problems Upgrading PluggableAuthService

2008-01-30 Thread Mark Phillips
On Wed, 2008-01-30 at 08:50 -0500, Jens Vagelpohl wrote:
> 
> On Jan 30, 2008, at 14:01 , Mark Phillips wrote:
> > I looked at the bug reports and found 2 that relate to this error:
> > http://plone.org/products/remember/issues/44
> > http://plone.org/products/remember/issues/32
> >
> > The suggested solution is to upgrade
> > PluggableAuthService to version 1.5.2, which I did. I stopped zope,
> > removed PluggableAuthService v 1.4.2 from the Products directory,
> > installed the new PluggableAuthService v 1.5.2, and restarted zope.
> >
> > However, no one can log in now. The remember members are still alive
> > and well, but entering the use name and password does nothing -
> > no error, no logged event, just return to the login page.
> >
> > What else do I have to do to upgrade PluggableAuthService?
> 
> There are no additional steps.
> 
> In a case like this I would start by manually inspecting the user 
> folder instance to make sure the plugin registrations are still 
> correct. 

How do I do this? Through the ZMI? My apologies for being so new to
zope.

> It may help to enable the verbose-security setting in 
> zope.conf and remove "Unauthorized" from the swallowed exceptions in 
> the error_log object in the ZMI,  
> you may get tracebacks that point to 
> the issue then. If that doesn't provide enough clues I would use the 
> Python debugger to step through the login process.
> 
> jens

Thanks. I tried
> 
> 
> ___
> Zope-PAS mailing list
> Zope-PAS@zope.org
> http://mail.zope.org/mailman/listinfo/zope-pas
> 
> 
___
Zope-PAS mailing list
Zope-PAS@zope.org
http://mail.zope.org/mailman/listinfo/zope-pas


Re: [Zope-PAS] Problems Upgrading PluggableAuthService

2008-01-30 Thread Jens Vagelpohl


On Jan 30, 2008, at 14:01 , Mark Phillips wrote:

I looked at the bug reports and found 2 that relate to this error:
http://plone.org/products/remember/issues/44
http://plone.org/products/remember/issues/32

The suggested solution is to upgrade
PluggableAuthService to version 1.5.2, which I did. I stopped zope,
removed PluggableAuthService v 1.4.2 from the Products directory,
installed the new PluggableAuthService v 1.5.2, and restarted zope.

However, no one can log in now. The remember members are still alive
and well, but entering the use name and password does nothing -
no error, no logged event, just return to the login page.

What else do I have to do to upgrade PluggableAuthService?


There are no additional steps.

In a case like this I would start by manually inspecting the user  
folder instance to make sure the plugin registrations are still  
correct. It may help to enable the verbose-security setting in  
zope.conf and remove "Unauthorized" from the swallowed exceptions in  
the error_log object in the ZMI, you may get tracebacks that point to  
the issue then. If that doesn't provide enough clues I would use the  
Python debugger to step through the login process.


jens


___
Zope-PAS mailing list
Zope-PAS@zope.org
http://mail.zope.org/mailman/listinfo/zope-pas


[Zope-PAS] Problems Upgrading PluggableAuthService

2008-01-30 Thread Mark Phillips
I have a plone site running:

Plone 2.5.5, 
CMF-1.6.4, 
Zope (Zope 2.9.8-final, python 2.4.4, freebsd6), 
Five 1.4.2, 
Python 2.4.4 (#2, Sep 26 2007, 13:07:27) [GCC 3.4.6 [FreeBSD]
20060305], 
PIL 1.1.6
membrane 1.0
remember 1.0
PluggableAuthService-1.4.2

The members cannot add portraits to the site, and I get the error
"ValueError: Property portrait: unknown type"
when I do a search for all users in site setup.

I looked at the bug reports and found 2 that relate to this error: 
http://plone.org/products/remember/issues/44
http://plone.org/products/remember/issues/32

The suggested solution is to upgrade
PluggableAuthService to version 1.5.2, which I did. I stopped zope, 
removed PluggableAuthService v 1.4.2 from the Products directory, 
installed the new PluggableAuthService v 1.5.2, and restarted zope. 

However, no one can log in now. The remember members are still alive 
and well, but entering the use name and password does nothing - 
no error, no logged event, just return to the login page.

What else do I have to do to upgrade PluggableAuthService?

Thanks!

Mark
___
Zope-PAS mailing list
Zope-PAS@zope.org
http://mail.zope.org/mailman/listinfo/zope-pas