Hi folks,
please excuse this long-winded post, but I'm a bit stuck with the
layout of my urls.py. Let me try to explain what the site I'm using
Django for does at the moment: Basically it's a website where local
birdwatchers (the ones with feathers, not boobies ;-) can log their
observations. By "
thanks for your comments guys, I guess I'm more or less on the right
track!
All the best,
Uwe
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, s
Hi folks,
one more thing: In order to allow chaning of countries / regions, I
was thinking of adding a bit of html to the top of each page where a
user can select the country in the first popup, then the region popup
populates (pun intended ;-) the the regions for the selected country,
and one "su
Hi folks,
this posting sort of refers to my previous problem from last week as
I'm still working on the birdwatcher's site. I cannot wrap my head
around how to create intelligent navigation links from the current
context or http request. For instance, if the user enters via the url
/de/observers/
Thanks Bruno,
I'll look into the custom template tags you mentioned. I had no idea
when I started out with this project that I'd be knee deep into
advanced django after a couple of weeks ;-)
BTW, can you recommend the "pro django" book?
All the best & thanks again for your help,
Uwe
--
You rec
On 26 Aug., 15:56, joconnell wrote:
> Hi Uwe,
>
> You might be able to leverage the 'url' template tag which comes with
> django?
>
Hi John & Bruno,
thanks for your answer.
I've looked at the url tag, but sadly it doesn't help me with
customizing the url's in the left navigation. The idea is th
On 26 Aug., 17:08, bruno desthuilliers
wrote:
> > So would it be possible to access the request.path property from
> > within a custom template tag?
>
> Of course, as long as
> 1/ you pass it explicitely or
> 2/ the request.path is available in the context passed to the tag's
> render() method.
>
Hi folks,
some of you may remember I'm working on a site for birders where they
can enter and keep track of their observations of various birds.
Multiple viewings of a species can be entered at different observation
locations, so for the ranking page (which considers only the number of
distinct s
Sorry to follow up on my own drivel, but I think I've found a solution
in the fine django docs:
obs =
Observation.objects.filter(observer=o.id,location__location_area__area_country__country_abbrev=country_code).values("bird_id").annotate(Count("bird"))
seems to do the job nicely for all combinati
Hi folks,
I'm in the process of migrating (or re-designing for that matter) a
Zope-based user database /ranking system over to Django with roughly
30,000 accounts in it. The Zope instance uses SimpleUserFolder for
authentication, so I was wondering if there is a way to authenticate
django users fr
following to your settings.py file to let django use your class
>
> AUTH_PROFILE_MODULE = 'accounts.UserProfile' # assuming you have created a
> accounts application
>
> Op 22-mei-2011, om 17:31 heeft Uwe Schuerkamp het volgende geschreven:
>
>
>
>
>
>
>
Hello Jonas,
thanks again for your reply. I think migrating the database over to
django may be a good idea, however it's still being used as a legacy
authentication database for other projects.
In case I'd decide to migrate the existing users over to the new
database, how could I make sure the pa
On 24 Mai, 00:17, Jonas Geiregat wrote:
> > In case I'd decide to migrate the existing users over to the new
> > database, how could I make sure the passwords end up in django
> > correctly? All I have is the old_password()-crypted user passwords,
> > can I simply insert those as values into th
Hi folks,
this is my first posting in this group, so I'm sorry in advance if I'm
breaking any rules or missing some vital information.
My setup:
Ubuntu Server 14.04.x
Python 2.7.6
Django 1.8.4 (updated to 1.8.5 recently) installed via "pip"
MariaDB 5.5.44
I'm trying to set up a test framework
Hi Mark,
I recently had the same issue, I went from 1.3.x to 1.4.21 and then to
1.8.5 via 1.7.x without any major issues.
Granted my application isn't too complex and doesn't use too many of
Django's internal bells and whistles, but the major obstacles for me were
adding some new entries to s
>
> Hi Mike,
>
thanks for your quick reply.
I tried deleting the test database, but that didn't help either (actually I
tried this several times before I posted here, I even set up a "fresh"
production database on my test machine and re-imported the live data in
order to solve the problem).
Here's some more info in case it helps:
The "manage.py test" call seems to get as far as creating the table
"django_migrations", then things break. The production DB has several more
tables (25 in all) I'm not seeing in the output below, so I guess this
issue must be related to the migrations
>
> I solved it myself... looks like I forgot to create the initial migrations
> for the app. After running
>
python manage.py makemigrations club300
python manage.py migrate --fake-initial
python manage.py test club300
appears to work fine. Sorry for the noise & thanks for your help!
Uwe
-
18 matches
Mail list logo