You can’t do this, which is by design. The Django framework authors intended a strict separation of presentation code from data logic. Filtering models is data logic, and outputting HTML is presentation logic. So you have several options. The easiest is to do the filtering, then pass the result to render_to_response. Or you could write … Read more
I will open with “You should not edit settings at runtime“. Having said that, I have exactly this same issue, where I want to create a unique database for each user. The reason for doing this is I am offering the ability for the user to save/access to/from a database not stored on my server, … Read more
It’s very easy with “context” arg for “ModelSerializer” constructor. For example: in view: my_objects = MyModelSerializer( input_collection, many=True, context={‘user_id’: request.user.id} ).data in serializers: class MyModelSerializer(serializers.ModelSerializer): … is_my_object = serializers.SerializerMethodField(‘_is_my_find’) … def _is_my_find(self, obj): user_id = self.context.get(“user_id”) if user_id: return user_id in obj.my_objects.values_list(“user_id”, flat=True) return False … so you can use “self.context” for getting extra params. … Read more
I’m assuming you’re currently using the built-in login view, with (r’^accounts/login/$’, ‘django.contrib.auth.views.login’), or something similar in your urls. You can write your own login view that wraps the default one. It will check if the user is already logged in (through is_authenticated attribute official documentation) and redirect if he is, and use the default view … Read more
GeoDjango looks like it will suit your needs. I’m not sure exactly how you would want to direct users, but using the GeoIP API, you can do something like: from django.contrib.gis.utils import GeoIP g = GeoIP() ip = request.META.get(‘REMOTE_ADDR’, None) if ip: city = g.city(ip)[‘city’] else: city = ‘Rome’ # default city # proceed with … Read more
Here’s a scaleable solution. My starting point was this gist, https://gist.github.com/michelts/1029336 i’ve enhanced that solution so that multiple forms can be displayed, but either all or an individual can be submitted https://gist.github.com/jamesbrobb/748c47f46b9bd224b07f and this is an example usage class SignupLoginView(MultiFormsView): template_name=”public/my_login_signup_template.html” form_classes = {‘login’: LoginForm, ‘signup’: SignupForm} success_url=”my/success/url” def get_login_initial(self): return {’email’:’[email protected]’} def get_signup_initial(self): return … Read more
After setting up your STATIC_ROOT and STATIC_URL, you may have to run python manage.py collectstatic
HTTP is inherently a “pull” protocol–i.e., a client pulls data from a server, waits around for a while and then pulls more data later. There’s actually no strictly HTTP way to “push” data to a client from a server. You have basically three options when you need to “push” to a client. (1) Do polling–use … Read more
After digging through the pip issue 3939 linked by @muon in the comments above and then the PEP-508 specification, I found success getting my private repo dependency to install via setup.py using this specification pattern in install_requires (no more dependency_links): install_requires = [ ‘some-pkg @ git+ssh://[email protected]/someorgname/[email protected]#egg=some-pkg’, ] The @v1.1 indicates the release tag created on … Read more
You need to add django.template.context_processors.request to your template context processors. Then you can access them like this: {{ request.session.name }} In case you are using custom views make sure you are passing a RequestContext instance. Example taken from documentation: from django.shortcuts import render_to_response from django.template import RequestContext def some_view(request): # … return render_to_response(‘my_template.html’, my_data_dictionary, context_instance=RequestContext(request)) … Read more