Lennart Regebro wrote:
Somebody can fix that for 2.8 tomorrow, maybe?
Well, zLOG is totally gone is 2.8, I guess it could do with fixing on
the 2.7 branch, so please submit a collector entry :-)
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.sim
Chris Withers wrote:
You're not doing anything wrong, but arguably it is a config error.
You'll need to tweak your log format string for the log in question in
zope.conf.
The real problem here is that, for some reason that I don't get, zLOG
sticks the "WARNING" in the *message* to be logged when
Lennart Regebro wrote:
OK, Thanks. I'm noticing that (with Zope 2.7.2) when I do this, I do not
get the modulname (whatever) nor the exception level WARNING printed to
the log. Is this a config error, or am I doing something wrong? Because
quite obviously, it should be there, right?
You're not d
Chris Withers wrote:
Lennart Regebro wrote:
Chris Withers wrote:
Is there any chance I could tempt you to change these to be Python
2.3 style logging calls?
Sure. remind me of the syntax. :)
import logging
logger = logging.getLogger('event.whatever')
logger.error('whatever',exc_info=1)
You coul
Lennart Regebro wrote:
Chris Withers wrote:
You do know I have a working CASUserFolder, right?
No, but we wouldn't have been able to use it, since we need CPS support.
What does "CPS support" mean? Why wouldn't CASUserFolder work with CPS?
I've got a customer who wants this to work in a proxied en
Chris Withers wrote:
You do know I have a working CASUserFolder, right?
No, but we wouldn't have been able to use it, since we need CPS support.
I've got a customer who wants this to work in a proxied environment, and
I think they gave me the okay to develop it as plugins for PAS too...
Wanna joi
According to Chris Withers:
> Is there any chance I could tempt you to change these to be Python 2.3
> style logging calls? Zope will be moving to them for 2.8 and it'd be
> great if you can change the code while you're "in there"...
Do you have an example at hand? I remember a posting to this l
According to Chris Withers:
> Could you add this patch to the following collector issue:
>
> http://zope.org/Members/urbanape/PluggableAuthService/Collector/4
Sure!
(i didnt do it in the first place, because it was already in CVS --
but you are right, it should be in the collector)
\wlang{}
-
Could you add this patch to the following collector issue:
http://zope.org/Members/urbanape/PluggableAuthService/Collector/4
cheers,
Chris
Willi Langenberger wrote:
According to Lennart Regebro:
No. Closer inspection seems to show that I actually don't get PAS to do
anything at all. It is simply i
Lennart Regebro wrote:
This is too bad, becuase for the CAS plugin that I started to write, I
need to redirect to an external web-page. No can do at this moment.
You do know I have a working CASUserFolder, right?
I've got a customer who wants this to work in a proxied environment, and
I think the
Lennart Regebro wrote:
If an error happens, a LOG should be printed...
Is there any chance I could tempt you to change these to be Python 2.3
style logging calls? Zope will be moving to them for 2.8 and it'd be
great if you can change the code while you're "in there"...
cheers,
Chris
--
Simplist
According to Lennart Regebro:
> No. Closer inspection seems to show that I actually don't get PAS to do
> anything at all. It is simply ignored, unless I put it into the root, in
> which case I can't do anything, since it doesn't care of emergency_user.
I also had this problem with the emergency
And there I ran into the next problem...
Seems like although there is challenge plugins and interfaces for
creating challenges and everything, they challenge() method on
challenge-plugins doesn't seem to be called from anywhere, ever!
Now, this is a bit strange, so I'm womdering if I'm missing so
Ah.
PAS basically swallow all errors without even logging them, meaning that
if you have an error, it basically makes your plugin "invisible". Not good.
If an error happens, a LOG should be printed...
I need to get myself new commit rights at Zope.org again. ;)
___
Lennart Regebro wrote:
Tres Seaver wrote:
Here is what I just did:
1. Created a folder, 'pas_test' in the root of my Zope, with a
minimal 'index_html'.
2. Changed its security settings, removing "acquire" from the "View"
permission and granting "View" to "Manager" and "Owner".
3. Verifie
Tres Seaver wrote:
Here is what I just did:
1. Created a folder, 'pas_test' in the root of my Zope, with a
minimal 'index_html'.
2. Changed its security settings, removing "acquire" from the "View"
permission and granting "View" to "Manager" and "Owner".
3. Verified that I could not view
16 matches
Mail list logo
