I'm new to django cms and I'm really lucky that I was able to install it. If I go to the backend of my site (http://localhost:8000/admin), then the django cms admin panel shows up.
If I want to edit some cms pages then I can see that the browser tries to get some files like "/static_media/cms/jquery.dialog.css", "/static_media/cms/pages.css", "/static_media/cms/ui.core.js" and so on...
Unfortunately the browser only gets a HTTP 404 response and I do not know what I have to configure in "settings.py" or "url.py" to get things working. Can anybody help me?
Found the solution at http://djangosnippets.org/snippets/2401/
Related
I am developing a webpage for my college where we will show ouur investigations, to solve that i decided to use the admin panel. The problem is that when I deply in production the webage I get a 500 Bad request
I have left the deault admin path
Also changed the path for admin and still having the same issue
Try opening on a different browser like chrome etc
When a 404 error is thrown in a project that uses Wagtail, I'd like to have the site redirect to a page in the CMS. How do I do this?
I know Wagtail has a redirects feature, but that doesn't seem to do what I want; if I were to use that I'd need to have some kind of wildcard selector that would be superseded by more specific redirects.
I searched around the issues but this was as close as I found. But that seems to be more related to admin 404s if I'm reading it right.
Web site functioned normally , I tried to login to admin page and suddenly when I access admin page it display:
404 - An error has occurred.
Component not found
No new extension/module/component and theme has been installed.
No changes on PHP or mysql on the server side. ( I did check with hosting providers).
It's like it works today and tomorrow when you want to login , you'll see the above mentioned error.
Renaming .htaccess did not solve the issue.
Restoring DB backup did not solve the issue.
I checked the Joomla logs ( in log folder) there isn't any related report.
Joomla version info:
$RELEASE = '2.5';
$DEV_LEVEL = '16';
Please help!
I managed to sloved this long time ago but I forgot to update!
It is solved by running repair and optimize operations on the database via phpmyadmin.
I'm working with mezzanine for a django project, and I can't figure out how to turn back on the DEBUG=True url configuration output that django usually produces on 404 pages.
With mezzanine installed, even with DEBUG=True, all I ever get is a blank 404 page.
Steps tried without success:
Googling around for "mezzanine 404 url" and various implementations
Skimming Mezzanine documentation
Disabling the custom mezzanine 404 handler
Any ideas on how to get the standard django url report back?
Thanks
Mezzanine contains a "catch all" urlpattern for pages. That is, the pattern for Mezzanine pages could be anything - example.com/foo, example.com/foo/bar, etc. So what you get is a standard 404 error.
What you're looking for is the error that occurs when no urlpattern matches the url requested. This can't actually occur with Mezzanine, since its patterns can match any url.
I have a website done with Django, that was previously done with PHP and CodeIgniter. I've moved the website to Webfaction, changed the DNS and all other configurations, but now my email is full of errors like this:
Error (EXTERNAL IP): /index.php/main/leer/7497
I don't know why the Django app is looking for pages from the PHP app, specially since the PHP app was in another host.
Are those URLs from your old site? That's probably a case of people having stale bookmarks, trying to navigate to them, and getting 404s. You might want to consider catching those, and redirecting to the new URL with response code 302.
I can't imagine those errors are caused by Django (except in the sense that the reports are from Django reporting 404s, which it does for free).
I agree with above. Just want to add you should use django.contrib.redirects to move the redirects.
You can read more about it here