Well if you're writing social-style apps (e.g. friends, invites,
events, groups, forums, blogs, wikis, social-networks) then Pinax.
Otherwise go with Django.
On Tue, Jan 17, 2012 at 6:12 PM, Kevin Miller wrote:
> Dear all,
>
> I have been struggling between using Pinax or Straight django to
> dev
On Mon, Jan 16, 2012 at 11:12 PM, Stuart Laughlin wrote:
> I also note that everyone who advocates
> for apache concedes that the default installation/configuration is really
> not appropriate for django apps. I intend to look more deeply into the
> suitability of the default configurations of ngi
I've found the solution, initially I was looking in wrong direction.
All I needed to do is to use ``Model.clean()`` method and then call
``Model.full_clean()`` in ``save()``:
from django.contrib.auth.models import User
class CustomUser(User)
def clean(self):
""" Clean username field t
On Jan 17, 4:51 am, Venkatraman S wrote:
> On Tue, Jan 17, 2012 at 6:30 AM, cjwalter wrote:
> > This is why I would appreciate to hear about experiences traveling
> > this road. What worked and what didn't?
>
> Have never been a fan of elance etc; you should be lucky to find a good set
> of 'trai
On 01/17/12 01:12, Kevin Miller wrote:
I have been struggling between using Pinax or Straight django
to develop my apps. I have never used Pinax, but was reading
on it. I have already only developed one website in django
although it is not yet launched.
I'm not sure it's an either/or propositi
You would have to work to modularize your design so you can split jobs
in a very much self contained modules for each outsourcing team, if a
module has dependencies with others you may want to create a set of
stubs and hand them that, hell you could even generate the whole set
of stubs for all the
Hi,
I am using PUT method, I get data from request.raw_post_data.
it's possible do that?
a = Article.objects.get(pk=1)
f = ArticleForm(request.raw_post_data, instance=a)
f.save()
Thanks!
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To po
On 16 Jan., 16:36, Sébastien Billion
wrote:
> Hi,
>
> Why don't use help_text argument in your models or formAdmin?
Thank you. That was exactly what I was looking for.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, se
On Tue, Jan 17, 2012 at 3:52 PM, Dilvane wrote:
> Hi,
>
> I am using PUT method, I get data from request.raw_post_data.
>
> it's possible do that?
>
> a = Article.objects.get(pk=1)
> f = ArticleForm(request.raw_post_data, instance=a)
> f.save()
>
>
> Thanks!
>
No.
Forms expect their data argumen
On Tue, Jan 17, 2012 at 3:56 AM, Tom Evans wrote:
> On Mon, Jan 16, 2012 at 11:12 PM, Stuart Laughlin
> wrote:
>> I also note that everyone who advocates
>> for apache concedes that the default installation/configuration is really
>> not appropriate for django apps. I intend to look more deeply
>
> Yes, your caching seems a likely culprit, and so does the asynchronous
> nature of you AJAX (but it seems like you've got a handle on that
> part). I haven't thought through the load balancer bit yet, but
> presumably they are all using the same cache / database / session
> store..?
>
update -
Hi guys, I’m having problem with my login form. The login form will
redirect me to the next page even if I didn’t input anything in the
username and password field. Also it can’t get the username of the
registered users to verify if the user data is wrong or right. How can
I get rid of this problem
With using
@login_required decorator the user needs to be logged in to allow execution,
don't makes much sense for a login :P
Am 17.01.2012 22:23, schrieb coded kid:
Hi guys, I’m having problem with my login form. The login form will
redirect me to the next page even if I didn’t input anythi
How do you mean by that?
Thorsten Sanders wrote:
> With using
>
> @login_required decorator the user needs to be logged in to allow execution,
> don't makes much sense for a login :P
>
>
>
> Am 17.01.2012 22:23, schrieb coded kid:
> > Hi guys, I�m having problem with my login form. The login form
Thorsten Sanders wrote:
> With using
>
> @login_required decorator the user needs to be logged in to allow execution,
> don't makes much sense for a login :P
>
>
>
> Am 17.01.2012 22:23, schrieb coded kid:
> > Hi guys, I�m having problem with my login form. The login form will
> > redirect me
It means, don't use the "decorator" @login_required above your login view.
Your login view cannot require a login, because you'd never get to log in.
Chicken and egg.
On Tue, Jan 17, 2012 at 2:34 PM, coded kid wrote:
>
>
> Thorsten Sanders wrote:
> > With using
> >
> > @login_required decorator
పనిమనిషి నూకాలు పూకు ని పచ్చడి కింద దెంగాను
click to Read Full Story http://www.googlika.com
--
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, sen
Yeah, I've done that, but its not working! Any help?
On Jan 17, 10:37 pm, Mark Furbee wrote:
> It means, don't use the "decorator" @login_required above your login view.
> Your login view cannot require a login, because you'd never get to log in.
> Chicken and egg.
>
>
>
> On Tue, Jan 17, 2012 at
18 matches
Mail list logo
