DEBUG=False running via mod_wsgi on Apache2 gives 500 error

[akaihola]

I'm hit by the same issue as the one xyz69 mentions in this thread:
http://groups.google.com/group/django-feincms/browse_thread/thread/1539c03a0fef0348

Looks like he solved it, but I can't claim to entirely understand the
solution (or the problem, for that matter).

So why exactly did his site, and now mine, crash totally when
debugging is turned off? What is it that needs to be done to avoid it?
And could something be done in FeinCMS to avoid the problem altogether
or give the developer a better hint at what is happening?

[akaihola]

Ah, just noticed a recent very informational thread on the same topic:
http://groups.google.com/group/django-feincms/browse_thread/thread/7d21e66803c117c8

[Matthias Kestenholz]

On Fri, Mar 5, 2010 at 12:04 PM, akaihola <akai...@gmail.com> wrote:
> Ah, just noticed a recent very informational thread on the same topic:
> http://groups.google.com/group/django-feincms/browse_thread/thread/7d21e66803c117c8
>

Concerning the ImproperlyConfigured exception:

Since v1.0.99, FeinCMS does not raise that many exceptions anymore --
these self checks have been introduced to catch usage errors early,
but they were dependent on the order of modules being loaded which
means they were very fragile. Switching off Django's DEBUG mode causes
model validation not to run, which means that some models files are
imported later than I expected.

Anyway, is it possible for you to update your FeinCMS installation to
current master and test whether you still get an internal server
error?

Thanks
Matthias

[Martin J. Laubach]

> Anyway, is it possible for you to update your FeinCMS installation to
> current master and test whether you still get an internal server
> error?

Yes, that still happens. I had to paste a bit of code from the debug
case validation in django into my wsgi script to make it work in a
production environment. There's still quite some fragility with
regards to loading order in there...

mjl

[demux]

I am having this same problem.

Any ideas on how to fix this or at least to just make it work?

ay

[Carsten Kraus]

Martins approach - using get_validation_errors in the wsgi script - worked for me, as well.

See http://groups.google.com/group/django-feincms/msg/68ff5462061fa84b.

--
You received this message because you are subscribed to the Google Groups "Django FeinCMS" group.
To post to this group, send email to django-...@googlegroups.com.
To unsubscribe from this group, send email to django-feincm...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-feincms?hl=en.