Hi Joseph,
Joseph schrieb:
[...]
So
when logged in as "admin", it's just silly to be asked if you're sure
you want to check-in since "admin" is still logged in.
thanks for the pointer, the message is now not displayed anymore if the
user IDs are identical.
Regarding the problem itself - I'm trying to find out what's wrong.
Unfortunately I can't reproduce it on my machine, only on the Zones
server :(
[...]
2) Problems with login
Next, in the First publication it appears I often am directed to login
again when accessing anything past the top-level Home page. That is, I
"Login for authoring", get the Home Page, attempt to access anything
(including a simple refresh) and I must login once more. The second
time sticks. This doesn't happen with the Default publication but I've
not yet determined what may be awry with First. Any ideas?
This issue has also been reported by Rudolf. I can't reproduce it on my
machine. The problem has disappeared after they have moved the setup to
a different machine.
But it gets even more interesting. The tutorial (at present) suggests
building First with no modules or resource-types. I'm not certain you
can really progress through the tutorials as such. There is Default
with its configuration. But one must wonder what minimal configuration
is required for the tutorials. These are supposed to be modular,
right? Note to self: for true pub-to-pub inheritance, remember to copy
these things since they're not inherited.
Actually the module and resource type declarations should be inherited.
I'll try to reproduce the issues you mentioned below as soon as I find
the time.
Well, when I add the "usecase" module the relogin behavior goes away.
Whew! But if I add the "homepage" resource-type, the relogin behavior
appears again. Hmm... So if I stick in the complete set of the Default
pub, I still have this issue where I don't with Default? What's still
different? Well... access-control and policies. But I have an
interesting challenge here. Per the tutorial for First, I set up this
to use a separate directory for the policy-manager. I didn't touch
Default. But as per the tutorial, I set up the authorizer to
aggregate-fallback to Default. Hmm... does this make sense? It's sort
of OK since we're defining the same roles and such. But something is
lacking. And I'm trying to imagine this in the real world. I imagine
this is just an oddity of the tutorial suggesting how to set this up for
First but inheriting some stuff from Default via aggregate-fallback.
If I switch (first/config/access-control) to use Default's
accreditable-manager and policy-manager (grabbing its authorizer via
aggregate-fallback), this relogin thing goes away. Plus BXE now works
in First. Doesn't fix One-Form Editor, but I already mentioned that is
broken in Default as well.
OK. I can continue experimenting here, isolate what's required for BXE
and try to determine what's behind the relogin behavior. But any quick
pointers from those more familiar with this would be greatly appreciated.
If docs are frozen, I cannot tell if anyone is updating the tutorials.
You find the new docu (at least the published pages) at
https://lenya.zones.apache.org/cms/docu/live/index.html
But I imagine this needs some attention. Furthermore, I'd recommend NOT
inheriting from Default. Default's there. People can play with it. I
think we'd be better served with a complete from-scratch approach with
everything explained along the way. Then a separate tutorial could be
used to demonstrate publication inheritance. It doesn't seem it'd be
too much work to modify the current stuff accordingly.
Joe H.
Thanks for your detailed report!
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
