Re: Newforms makes unicode String from a dictonary
On May 24, 4:20 pm, Christian Schmidt <[EMAIL PROTECTED]> wrote: > Hi, > > I have a form touploada picture and i try to validate it innewforms. But i > can not read the content-type. I get the error > "'unicode' object has no attribute 'get'". > I had the same problem. I was using a forms.CharField with a widget=forms.FileInput. This was causing django to turn the file upload dictionary into a unicode string. I changed forms.CharField to forms.Field and now it is working fine. --Ray --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Pop-up forms
In the Django admin, there is a feature where you can click a "+" symbol and it will pop-up a form in another window that when you fill it out an submit, it will add that item to the current form. I'm not sure what you call that. I would like to add a similar functionality to an app that I am developing, but I don't know the correct term to search for. I have tried searching for "dynamic forms" and "pop-up forms" and several combinations of the two, but I can't find anything like it. Does anyone know what you call that feature? --Ray --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Pop-up forms
You wouldn't happen to know a good resource of where I can learn more of how to create a form like this would you? I'd like to implement a similar capability and would like to read up on how to do it. --Ray --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Database replication question
Please forgive my ignorance. I am not the sharpest knife out of the web development drawer. I have a question about database replication as it relates to Django. I used to work at a place that had a somewhat high availability/performance/whatever application where we had a MySQL db replicated across multiple machines. All of the writes were done to the master and all of the reads were spread out across mulitple slave systems.This worked out well because the number of reads far exceeed the number of writes. Some time ago there was a thread(http://groups.google.com/group/django-users/browse_thread/thread/d08f4975da831bb/42a458eba506cda9?q=database+replication&rnum=1#42a458eba506cda9) on the Django list that alluded to adding this type of capability to Django. Where you could have one db host setup to handle the writes and have Django read from a different host. At least that is how I read the thread. I did a search and could not find any other info out there on this. Is this still something that is on the table? Or am I was off base and is this something that is not even needed/wanted? Again I apologize if I sound ignorant. I don't know any better. --Ray --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Database replication question
Joseph Kocherhans wrote: > It's certainly wanted, but I don't think anyone has worked on it yet. > There's a ticket open at: http://code.djangoproject.com/ticket/1142 Nur. I completely neglected to search the tickets! --Ray --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Google-like API keys
Nowadays(is that a word?) a lot of fancy web services use API keys to allow an individual access to a service without requiring a username and password. Google, flickr(I believe), Akismet, so on and so on. If I wanted to make a Django app that utilized a custom authenticator and my own "API key" what would be the best way to generate unique API keys for my app. Would running a md5/sha sum on username + randomstring + email be safe? Or is that stupid thinking? I apologize if this is the wrong place to ask such a question. I searched google and the mailing list archives and I didn;t see a similar subject anywhere. Thanks in advance for any help and ideas. --Ray --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Google-like API keys
Thanks for all of the help and responses. You have helped give me ideas on how to implement something like this. --Ray --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Strange 'caching' issue
First let me say that I loathe using the term 'caching' to describe this problem as it probably has nothing to do with caching. But my primitive vocabulary is at a loss for a better word. I have a very simple Django blog app that I'm using to learn more about the Django framework. I notice that when I add a blog entry, it doesn't show up right away. Sometimes it takes more than a day before it will show up. Other times it will post right away. If I add a post and it doesn't show up right away, all I need to do is to bounce Apache and boom there it is. I'm not sure what exactly I am doing wrong. I don't have any caching enabled. I'm not loading the caching middleware or anything like that. I wonder if my Apache config might not be as correct as it should be. I have tried tweaking the maxrequestsperchild, but I still see the same behavior. Would anyone know what I should be looking at? I am certain that this is my fault. i have been googling the mailing list and I don't really see anything that looks the same as my problem. Thanks in advance for any help. --Ray --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Strange 'caching' issue
I don't think this is it. If I restart Apache then the post will appear. I would think that it had to do with my browser's cache, but clearing the cache doesn't help, plus if I use a browser that has never been to my site, I have the same problem. It almost seems as if the response is cached somehow, and whatever is caching that response takes a really long time to expire. The weird thing is, I don't have the caching middleware enabled or in use in any way. --Ray --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Strange 'caching' issue
Malcolm, I made a new post and then tried out your curl idea. i got back two different ETAG(I have etgas enabled) values: HTTP/1.1 200 OK Date: Tue, 15 Aug 2006 19:53:38 GMT Server: Apache/2.2.2 (Unix) mod_ssl/2.2.2 OpenSSL/0.9.8b DAV/2 mod_python/3.2.8 Python/2.4.3 PHP/5.1.4 Vary: Cookie,Accept-Encoding ETag: 1005ded9726e14ef4c5dab08a55f21c7 Content-Type: text/html; charset=utf-8 HTTP/1.1 200 OK Date: Tue, 15 Aug 2006 19:53:30 GMT Server: Apache/2.2.2 (Unix) mod_ssl/2.2.2 OpenSSL/0.9.8b DAV/2 mod_python/3.2.8 Python/2.4.3 PHP/5.1.4 Vary: Cookie,Accept-Encoding ETag: a1ca8032c757c0d70d431a0cdf2b66fd Content-Type: text/html; charset=utf-8 Sometimes I would get one, and other times I would get the other. It was strange. I'm still looking into this issue. i haven't quite gotten to the point of putting in debug statements, but I won't rule it out. --Ray --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Planet Django
I noticed that a lot of projects out there have "planet" websites, where they aggregate blog feeds from people that are working on that particular project. Some examples are: http://planet.gnome.org/ http://planet.python.org/ http://planet.twistedmatrix.com/ http://planet.mozilla.org/ http://planetapache.org/ Just to name a few. These are great places to get a feel for a particular user community and a good way to provide a single place to find info on a particular project. I was wondering if there were plans for a planet.djangoproject.com? I thikn it would be a great idea. --Ray
Re: Planet Django
stinger wrote: > I second that > > ;) Does anyone know who the contact is for the djangoproject.com website? Does anyone know if they read this mailing list? I'd be willing to chat up the right person to see this happen. --Ray
Re: Planet Django
I've seen a few people blogging about django. Ideally it would be nice if there were people involved with the project that were providing feeds to it. --Ray
Re: Planet Django
This is gonna be sweet! --Ray
