We Keep Coding

How is django's default root homepage rendered?

This is a kind of want-to-know itch. Many questions here ask how to replace the default Django homepage (e.g. ). I understand that issue. What I'm curious to know is how the default page is rendered when a new project is created (i.e., in debug mode). Even though my question is not as directly practical as knowing how to replace the default homepage, I have the feeling that if I figure it out, I may understand how Django works a bit better.
I would expect it to be in the default urls.py file, but the only entry by default in urlpatterns of urls.py is path('admin/', admin.site.urls). My first naive expectation would be an entry in urlpatterns that you could remove or comment out. Since there's nothing there besides admin/, I'm guessing there's some other built-in app or middleware that specifies the default homepage, but I don't know where to look.
Here's my progress in understanding this so far:
Commenting out DEBUG=True in settings.py causes the default homepage to no longer appear.
I've seen this documentation about how Django processes requests, which mentions middleware that can set the urlconf attribute on a request that changes the default, ROOT_URLCONF.
So far Django has been pretty straightforward, but this seems like something magical, so I'm trying to figure out what's going on behind the scenes.
I appreciate the help!

The relevant code is here. Django basically has a special case for when no matching URL is found in the URL configuration, and the requested path is /, and there is only one entry in the URL configuration.
In that case it loads a default_urlconf which renders that welcome template in place of a regular 404 response.
This is called from inside the technical_404_response function, which is only called when DEBUG=True.

i can't connect between app URLs in Django

I have a small problem with URLs file in Django,
I'm trying to connect between app URLs, review, and the main urls
I have
python 3.9.1
Django 3.2.0
I have been searching and try many things on StackOverflow but still, I don't find why the server doesn't work just when I put this line with a red arrow on the comment,
please help!!

One typo I can see is in signup/urls.py-
Change URLPattern to urlpatterns. Let me know if that fixes the issue in the comment?

In your signup folder's urls.py file replace URLPattern to urlpatterns.
Try:
urlpatterns = [
...
]
Happy coding :)

Why do I get "No module name users" when trying to run a newly upgraded Django 1.4 project?

I have upgraded my site from Django 1.3.1 to Django 1.4. I have an app called 'users'. I have a URL routing rule for my project as follows:
url(r'', include('users.urls', namespace='users', app_name='users')),
and a specific user profile routing rule:
url(r'^profile/(?P<pk>\d+)/$', ProfileDetailView.as_view(),
name='profile'),
The users app has an empty init.py file. Nevertheless, I receive a template error:
Error during template rendering
In template /home/daniel/python_practice/rainbow/django_templates/user_bar.html, error at line 3
No module named users
when I use the following template code:
{{ user.username }}
I've been stuck on this problem for some hours. The project is named 'rainbow'. I have tried doing things like modifying the url call parameters to url rainbow.users:profile .... Upon doing so, it tells me that 'rainbow' is not a namespace. It's as if it is recognizing the users namespace, but is then looking for a module of some kind and failing.
Does anybody have any insight into this?
Edit:
The directory structure is as follows:
rainbow
--> rainbow - directory that contains global settings and urls
--> users - the relevant app
--> __init__.py
--> ...etc.
--> other apps
--> django_templates (eg. the relevant template would be django_templates/user_bar.html)
Thanks,
ParagonRG

As is so often the case, the problem in my search for an answer was too greatly limiting the scope of my search ad my tests. There were actually two URL config lines with non-existent modules specified. I was simply modifying one at a time to no positive effect.
The lines were:
url(r'^join/$', 'rainbow.users.views.register', name='join'),
url(r'^profile/$', 'rainbow.users.views.self_profile',
name='user_profile_current'),
Removing the rainbow. from each of these views fixed the issue.

Just a suggestion, but when you upgraded you Django to 1.4, have you upgraded your project manage.py ?
Upgrade of manage.py in django 1.4
They talk about path issues you may have now. As okm asked, if you can't start a shell and import user, there's something wrong at the root.

How to use Django-filer(asset file manager)?

Can someone point me in the right direction on how to use Django-filer? I have installed the necessary tools for the filer to work and I get the Filer tab in the admin interface, but when I upload an image to the app I am not able to get the preview thumbimage. The image is also uploaded to the Media_root path(Public files default path). What else have I missed?

Had a similar problem. I had missed that when easy_thumbnails is automatically pulled in by pip, you still have to explicitly add it to your INSTALLED_APPS in settings.py.
I spotted this because when I was uploading images, they weren't appearing in the clipboard, and when inspecting the response from the upload, there was an internal server error complaining that an easy_thumbnails table wasn't available.
tl;dr; check you added easy_thumbnails to your settings and did a migration / syncdb

Take a look in your urls.py. You should have the following code in it:
if settings.DEBUG:
urlpatterns += patterns('', (
r'^media/(?P<path>.*)$', 'django.views.static.serve', {'document_root': settings.MEDIA_ROOT}))
Cheers

Weird django admin importerror

I am getting a weird import error when I try to access admin: http://dpaste.com/292489/ It doesn't seem to be related to my code and I have setup all the proper admin settings and urls, since admin has worked properly before.

The only thing I think to do is to double check your PYTHONPATH and triple check that your ROOT_URLCONF is pointing to the right spot.