Thanks, for the hint, Dieter. Unfortunately, I believe this doesn't
apply in our case, as we have that set to the default (on).
Tim
Dieter Maurer wrote:
Tim Connor wrote at 2005-6-5 18:56 -0600:
I also get this error a lot when trying to add an object through the ZMI
in an Apeified
Tim Connor wrote at 2005-6-5 18:56 -0600:
I also get this error a lot when trying to add an object through the ZMI
in an Apeified folder:
* Module ZPublisher.Publish, line 92, in publish
* Module ZPublisher.BaseRequest, line 302, in traverse
* Module App.FactoryDispatcher, line 29,
I also get this error a lot when trying to add an object through the ZMI
in an Apeified folder:
* Module ZPublisher.Publish, line 92, in publish
* Module ZPublisher.BaseRequest, line 302, in traverse
* Module App.FactoryDispatcher, line 29, in __bobo_traverse__
* Module App.Product,
Cool. Good luck. Let me know if you need a tester. ;)
Tim
Shane Hathaway wrote:
Tim Connor wrote:
Thanks, Shane. That fixes the problem of Zope not starting, and better
than the other syntax I tried, but it still doesn't fix the core
problem. My root Ape installs have issues with
I sent roughly this email directly to Shane Hathaway, since I hadn't
asked for any help on Zope, yet, so didn't know where to look. Maybe
this was a better avenue? If you read this list, Shane (or Mr. Hathaway,
if you prefer), respond on whichever seems more appropriate, I guess. I
don't
Tim,
You may want to run Zope in debug mode-- bin/runzope should do it.
Also, be sure you have the event.log configured and enable.
-d
On Wed, 25 May 2005, Tim Connor wrote:
I sent roughly this email directly to Shane Hathaway, since I hadn't
asked for any help on Zope, yet, so didn't
Thanks, I feel like an idiot - running it as a daemon would explain why
I wasn't getting as much feedback. I still don't quite get why it
wasn't writing to the log though, since it is normally doing that fine.
I've had that frustration with Zope before though - some errors seem to
kill it in
Thanks Dennis,
Between your and Shane's reply, I got it fixed:
I just raised an error with the value of app.__ac_roles__, at that point
in lib/python/OFS/Application.py and determined that ONLY the role I had
added was being created. So going in and manually adding those starting
default
I spoke too soon. I don't think it's Zope error on that type mismatch
(or if it is one, it's not that one I thought). It still happens if
there are multiple roles defined. As long as it hits the code adding
the non-existing Owner role* the start-up croaks. So either something
about Ape is
Thanks, Shane. That fixes the problem of Zope not starting, and better
than the other syntax I tried, but it still doesn't fix the core
problem. My root Ape installs have issues with adding a local role, as
then the default roles get axed. If you add this fix then Zope re-adds
Owner (and
10 matches
Mail list logo