This is rather common when moving over from the dev server to a
production environment. Sometimes it can be tricky to map all the
static URL paths in the web server serving the static content, such as
the JavaScripts which treemenus uses. I haven't used treemenus
before, but from past experiences with working with different apps and
moving over to a production environment, I can advise the following
steps to troubleshoot.
* Compare the output HTML from both the dev server and the production
server.
* Make sure all the resources pointed to by the production server
exist, eg. /media/js/mycode.js, in Firefox you can click these
resources in the source view.
* If any resources return a Django error, or a 404 page, that's where
your problem lies. You will need to create a few location {} blocks
in nginx to point to the resources on the production server. You
should have already done this for the admin app.
* Make sure you have everything needed installed on the production
server, although if anything was missing Django would have gave an
ImportError exception, it's still good to check.
* Be sure that nginx is passing all the header information to the
application, I'm not sure how wsgi works, I personally use FastCGI
with Django and Nginx.
* Check the nginx log files to see if there are any 404 or 500 error
messages, the page won't display these for resources such as a missing
JS/CSS file.
Hope this helps in your troubleshooting efforts.
On Oct 17, 5:40 pm, Alastair Campbell <ala...@gmail.com> wrote:
> Hi everyone,
>
> I got a surprise when using treemenus, where it worked really well on
> my local dev (django-server) , but disappeared on live (nginx using
> mod_wsgi on debian).
>
> I installed the treemenu app, imported the data (menu items) from a
> datadump of my local app, and uploaded the templates that use
> treemenu.
>
> No error, but no output either.
>
> When I went to the Admin, the menus were there, but editing the items
> resulted in a blank editing area.
> I switched on debug briefly on live (in maintenance mode), but no
> error was reported.
>
> Has anyone else experienced blank output under mod_wsgi but not local dev?
>
> If not, could someone suggest where I could start debugging? Usually I
> check logs for errors or use the django error page, but both are blank
> :-(
>
> I've had to hard-code the navigation across the site in the meantime,
> which is going to get time consuming very quickly!
>
> Kind regards,
>
> -Alastair
>
> PS. a belated thank you to Bruno Desthuilliers for help with my
> category question before, it worked!
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
