grokgui.admin-0.5+megrok.login in Grok-1.0

[Aroldo Souza-Leite]

Hi list,

the grok-1.0.cfg official grokui.admin version is 0.3.2. But
grokui.admin-0.5 seems to be working well in Grok-1.0 in a midsized
application that was developed on former Grok versions and using
megrok.login. Are there any known caveats or general Grok-1.0
compatibility tests grokui.admin-0.5 + megrok.login-0.1 should undergo?

Regards,

Aroldo.
_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Leonardo Rochael Almeida]

Hi,

I don't know anything specific about your question, but I'd like to
take the opportunity to say we should consider releasing 3rd level
revisions (e.g. grok 1.0.1) whenever we figure out a newer set of
package versions that work with grok, even if there is no code change
in grok itself.

Cheers, Leo

On Fri, Oct 30, 2009 at 11:29, Aroldo Souza-Leite <asouzaleite@...> wrote:

> Hi list,
>
> the grok-1.0.cfg official grokui.admin version is 0.3.2. But
> grokui.admin-0.5 seems to be working well in Grok-1.0 in a midsized
> application that was developed on former Grok versions and using
> megrok.login. Are there any known caveats or general Grok-1.0
> compatibility tests grokui.admin-0.5 + megrok.login-0.1 should undergo?
>
> Regards,
>
> Aroldo.
> _______________________________________________
> Grok-dev mailing list
> Grok-dev@...
> https://mail.zope.org/mailman/listinfo/grok-dev
>

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Uli Fouquet]

Hi Aroldo,

Am Freitag, den 30.10.2009, 11:29 +0100 schrieb Aroldo Souza-Leite:

> the grok-1.0.cfg official grokui.admin version is 0.3.2. But
> grokui.admin-0.5 seems to be working well in Grok-1.0 in a midsized
> application that was developed on former Grok versions and using
> megrok.login. Are there any known caveats or general Grok-1.0
> compatibility tests grokui.admin-0.5 + megrok.login-0.1 should undergo?

There should be no problems with it. Naturally, grokui.admin 0.5 had an
even stronger focus on recent grok 1.0 developments. So, I think it's
secure to use 0.5 in your production environment :-)

Best regards,

--
Uli



_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Aroldo Souza-Leite]

Hi Uli,


Uli Fouquet wrote:

> Hi Aroldo,
>
> Am Freitag, den 30.10.2009, 11:29 +0100 schrieb Aroldo Souza-Leite:
>
>  
>> the grok-1.0.cfg official grokui.admin version is 0.3.2. But
>> grokui.admin-0.5 seems to be working well in Grok-1.0 in a midsized
>> application that was developed on former Grok versions and using
>> megrok.login. Are there any known caveats or general Grok-1.0
>> compatibility tests grokui.admin-0.5 + megrok.login-0.1 should undergo?
>>    
>
> There should be no problems with it. Naturally, grokui.admin 0.5 had an
> even stronger focus on recent grok 1.0 developments. So, I think it's
> secure to use 0.5 in your production environment :-)
>
> Best regards,
>
>  

we did find a funny behaviour in the application: the manager user  
"grok" is now authenticated through megrok.login,
but further users with less rights are now refused entrance in the portal.

We can't compare  it with grokui.admin-0.3.2 in Grok-1.0 because with
the official grokui.admin version the site raises an error at start (see
zopectl debug snapshot below).

Best regards,

Aroldo.



----------------------------------------------------------------------------------

Traceback (most recent call last):
  File
"/home/aroldo/.local/lib/python2.5/site-packages/buildout-eggs/zc.zope3recipes-0.11.0-py2.5.egg/zc/zope3recipes/debugzope.py",
line 60, in debug
    globs = zglobals(options.configroot)
...
 File
"/home/aroldo/.local/lib/python2.5/site-packages/buildout-eggs/zope.app.appsetup-3.4.1-py2.5.egg/zope/app/appsetup/bootstrap.py",
line 81, in ensureUtility
    if (reg.provided.isOrExtends(interface) and reg.name == name)]
AttributeError: type object 'ISecurityNotifier' has no attribute
'isOrExtends'
 >
/home/aroldo/.local/lib/python2.5/site-packages/buildout-eggs/zope.app.appsetup-3.4.1-py2.5.egg/zope/app/appsetup/bootstrap.py(81)ensureUtility()
-> if (reg.provided.isOrExtends(interface) and reg.name == name)]
(Pdb) l
 76                            "supported after Zope 3.5",
 77                            DeprecationWarning, 2)
 78    
 79          sm = root_folder.getSiteManager()
 80          utils = [reg for reg in sm.registeredUtilities()
 81  ->                 if (reg.provided.isOrExtends(interface) and
reg.name == name)]
 82          if len(utils) == 0:
 83              return addConfigureUtility(
 84                  root_folder, interface, utility_type, utility_factory,
 85                  name, asObject, **kw
 86                  )
(Pdb) reg.provided
<class 'grokui.admin.interfaces.ISecurityNotifier'>
(Pdb) type(reg.provided)
<type 'type'>
(Pdb)

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Uli Fouquet]

Hi Aroldo,

Aroldo Souza-Leite wrote:

> we did find a funny behaviour in the application: the manager user
> "grok" is now authenticated through megrok.login, but further users
> with less rights are now refused entrance in the portal.

This sounds a bit like you lost the local utility that holds the
principals during upgrade.

> We can't compare  it with grokui.admin-0.3.2 in Grok-1.0 because with
> the official grokui.admin version the site raises an error at start
> (see zopectl debug snapshot below).

This is really strange: according to your debug log there is an
interface ISecurityNotifier. But this interface does not exist in
grokui.admin 0.3.x (it was introduced in 0.4). Maybe you mixed up
something here?

Best regards,

--
Uli



_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev