If some one is having difficulty understanding my question. PLZ ASK.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
Hi Shyam,
Kinda of difficult to help you out without letting people know what Django
version you're using and a traceback of your error ;)
On Tuesday, July 28, 2015 at 5:09:29 PM UTC-4, Shyam Satyaprasad wrote:
>
> Hello,
>
> I get the Timeout error when in my error logs. What is the reason
HOOLY S**T
Thanks so much. That was the culprit
On Tuesday, July 28, 2015 at 10:39:16 PM UTC, James Schneider wrote:
>
> It looks like you are trying to pass a dict to get_context_data(), but you
> forgot the surrounding {}.
>
> -James
> On Jul 28, 2015 3:36 PM, "Nkansah Rexford"
It looks like you are trying to pass a dict to get_context_data(), but you
forgot the surrounding {}.
-James
On Jul 28, 2015 3:36 PM, "Nkansah Rexford" wrote:
> I have this:
>
> class Homepage(FormView):
> template_name = 'index.html'
>
> def get(self, request,
By the way, i'm following the steps
here: http://stackoverflow.com/a/30116519/1757321
I want to have two forms submitted under one submit button.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving
I have this:
class Homepage(FormView):
template_name = 'index.html'
def get(self, request, *args, **kwargs):
ecg_form = GhanaECGForm()
ecg_form.prefix = 'ecg_form'
last_form = FormLastActiveForm()
last_form.prefix = 'last_form'
*return
Hello,
I get the Timeout error when in my error logs. What is the reason behind it
? My code was working fine and suddenly I'm getting this error.
Regards,
Shyam
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group
Thanks a lot! I've ended up using `django-transaction-hooks`.
On Monday, July 27, 2015 at 5:49:40 PM UTC+2, Carl Meyer wrote:
>
> Hi Maciej,
>
> On 07/27/2015 07:03 AM, Maciej Gol wrote:
> > I've been recently working (porting to Django 1.8) on a project where we
> > need to use a few
> Den 28/07/2015 kl. 14.36 skrev Stefan Schindler :
>
>> This makes no sense to me. You want to delete an Item or Order but
>> then immediately create a new one?
>
> My actual goal is this: Whenever an Item object itself is deleted, I
> want to create a LogEntry object
I think it's this bug which will be fixed in Django 1.9:
https://code.djangoproject.com/ticket/24390
On Tuesday, July 28, 2015 at 8:36:34 AM UTC-4, Franck Samson wrote:
>
> Hello,
>
>
> I'm a beginner in Django, I use Django 1.8 in a virtualenv with python 3.4
> and a postgresql database. I
> This makes no sense to me. You want to delete an Item or Order but
> then immediately create a new one?
My actual goal is this: Whenever an Item object itself is deleted, I
want to create a LogEntry object attached to the item's order. If an
order is deleted however, I don't want to do
Hello,
I'm a beginner in Django, I use Django 1.8 in a virtualenv with python 3.4
and a postgresql database. I create my app and my models, and I want to
drop indexes temporarily for inserting data in the database.
But when I use this command :
django-admin.py sqldropindexes app_label
The
> Den 28/07/2015 kl. 09.37 skrev Stefan Schindler :
>
> If the Order object itself is deleted, all post_delete handlers of all
> related objects are fired, including Item. Item however stores a new
> object with a relation to the *deleted Order* object, which will
> result in a
I am making a Django app for email data Analysis, I am using Python
social Auth library for Gmail Login.
After the completion of Login process I want to access user Email and
Access_Token But I am getting how to do that,
Do I need to make new custom user model?
--
Thanks
Arshpreet Singh
I am
Hello James,
Following your advice I turned to using CreateView, and now all the
functionality I wanted seems to work fully. As you suggested there is no
need for a form.py using this method. When I got more time I might
investigate further how to make the original approach work for future
Hey guys,
the post_delete signal is fired before the PK field of the deleted and
all related objects is set to None. This leads to the situation that
one can't determine if a related object has been deleted in a
post_delete handler.
Here's an example:
"Order", "Item" and "LogEntry" are the
I've reviewed your code a bit more and I see what you're trying to do, I
think.
With that being said, I'll recant what I said about the CreateView.
Your trouble stems from the fact that FormView by default does not perform
a form.save() operation anywhere (it only validates the form). CreateView
Right.. I miss read the requirements.txt. Im new to django so started from
a simple app base and building on top. On first look nothing broke when
upgrading to 1.7. Ill check the docs you posted now.
On Tuesday, 28 July 2015 11:54:55 UTC+3, James Schneider wrote:
>
> Are you sure you're using
Are you sure you're using 1.7? Your original error posting begs to differ:
Django Version:1.6.11
The particular portion of docs that you are reading is meant to show how
various mixin's can be used together to address specific edge cases, but
other generic classes exist that are much better
Hello James,
The reason I am following this approach is because this is what was
suggested in the documentation, for the scenario where you need to have a
form within a DetailsView. Although even when I got my code to be identical
to the documentation example, I still dont get an object
Is there a specific reason you aren't just using CreateView rather than
trying to mix in a bunch of classes and trying to roll the post() logic
yourself? You can probably cut a very large portion of code out and make
this super simple.
The override is this, I was experimenting with save..
> class CommentForm(forms.ModelForm):
> class Meta:
> model = Comment
> exclude = ("parent_post","created_at")
>
>
> def create_view(request, **kwargs):
> print "IN VIEW"
> if request.method == "POST":
Thanks your your response. I have now gone past that problem and the form
renders, although on submission of the form nothing happens. The 'POST
-' string is printed, which means I am on the right track, but no new
object is created. I tried to simplify the comment form (remove the FK and
https://github.com/diefenbach/django-permissions
On 27 July 2015 at 17:51, Some Developer wrote:
> I have a need for a more robust permission system for objects in Django than
> the one provided by it in the core distribution.
>
> I want to have users and groups and
Forgot to add, the full backtrace would be helpful, too. It should be
present on the same error page.
On 28 Jul 2015 08:52, "Gergely Polonkai" wrote:
> Hello,
>
> could you show us the relevant part of your urls.py file? I suspect view
> parameters to cause the trouble but
Hello,
could you show us the relevant part of your urls.py file? I suspect view
parameters to cause the trouble but I'd like to be sure.
Best,
Gergely
On 28 Jul 2015 00:46, "Ioannis Latousakis" wrote:
> I am on the exact same situation as the one described in the
I am looking on code that someone else wrote , i am new to tasty pie , so
what i have understood that when ever someone gives a "POST" request then
resource's save method gets called.
what is happening with my code is whenever some gives "POST request" , save
method gets called thrice and for
27 matches
Mail list logo