On Thu, Aug 2, 2012 at 8:15 PM, Melvyn Sopacua wrote:
> On 1-8-2012 21:52, Larry Martell wrote:
>> On Wed, Aug 1, 2012 at 1:38 PM, Kurtis Mullins
>> wrote:
>>> Sorry for the double-message. Anyways, if you do want to do what that other
>>> person recommended, simply find the View that the user i
On 1-8-2012 21:52, Larry Martell wrote:
> On Wed, Aug 1, 2012 at 1:38 PM, Kurtis Mullins
> wrote:
>> Sorry for the double-message. Anyways, if you do want to do what that other
>> person recommended, simply find the View that the user is redirected to
>> after logging in. Then, modify the "contex
Ahh okay, Then yeah, something similar to the messages framework may work
well for you in this case. You could even use the messages framework
directly in a "hackish" sort of way just by putting some code in your
template that looks for a Messages Warning and spits out javascript
accordingly. Shou
On Thu, Aug 2, 2012 at 9:24 AM, Kurtis Mullins wrote:
> Sorry I didn't catch this part. You could modify your "Login" view to check
> the user agent and if it's an incompatible browser, and simply return a
> template that tells them their browser is unsupported. I'd do this before
> they even hit
On Thu, Aug 2, 2012 at 9:13 AM, Andreas Schosser wrote:
> Hi Larry
>
>> They want the dialog to pop up on top of the login screen before the
>> redirect. I don't know where the code that does this would live or how
>> it would get invoked.
>>
>> As far as to why they want this, it doesn't really s
On Thu, Aug 2, 2012 at 8:18 AM, Kurtis Mullins wrote:
> Hey Larry,
Thanks for the reply Kurtis.
> Okay, let me make sure I understand this correctly. This is, essentially,
> the flow of control you'd like to implement:
>
> 1. User signs in successfully
> 2. User is redirected to some other (any
Sorry I didn't catch this part. You could modify your "Login" view to check
the user agent and if it's an incompatible browser, and simply return a
template that tells them their browser is unsupported. I'd do this before
they even hit the Login Form just to be courteous to the user. But this
modif
Hi Larry
> They want the dialog to pop up on top of the login screen before the
> redirect. I don't know where the code that does this would live or how
> it would get invoked.
>
> As far as to why they want this, it doesn't really support IE, and
> they want to alert the user to that if that's w
Whoops, quick fix in my message (Item #2):
> 1. User signs in successfully
> 2. User is *redirected* to some other (any other) page
> 3. User is presented with a one-time-only popup
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post t
Hey Larry,
Okay, let me make sure I understand this correctly. This is, essentially,
the flow of control you'd like to implement:
1. User signs in successfully
2. User is prompted to some other (any other) page
3. User is presented with a one-time only popup
The simple way to implement something
On Wed, Aug 1, 2012 at 3:57 PM, Larry Martell wrote:
> On Wed, Aug 1, 2012 at 1:56 PM, Larry Martell wrote:
>> On Wed, Aug 1, 2012 at 1:52 PM, Larry Martell
>> wrote:
>>> On Wed, Aug 1, 2012 at 1:38 PM, Kurtis Mullins
>>> wrote:
Sorry for the double-message. Anyways, if you do want to do
On Wed, Aug 1, 2012 at 1:56 PM, Larry Martell wrote:
> On Wed, Aug 1, 2012 at 1:52 PM, Larry Martell wrote:
>> On Wed, Aug 1, 2012 at 1:38 PM, Kurtis Mullins
>> wrote:
>>> Sorry for the double-message. Anyways, if you do want to do what that other
>>> person recommended, simply find the View th
On Wed, Aug 1, 2012 at 1:52 PM, Larry Martell wrote:
> On Wed, Aug 1, 2012 at 1:38 PM, Kurtis Mullins
> wrote:
>> Sorry for the double-message. Anyways, if you do want to do what that other
>> person recommended, simply find the View that the user is redirected to
>> after logging in. Then, modi
On Wed, Aug 1, 2012 at 1:38 PM, Kurtis Mullins wrote:
> Sorry for the double-message. Anyways, if you do want to do what that other
> person recommended, simply find the View that the user is redirected to
> after logging in. Then, modify the "context data" of that view to dump
> whatever data to
On Wed, Aug 1, 2012 at 1:36 PM, Kurtis Mullins wrote:
> Is the "Dialog Box" going to be presented using Javascript? If so, why not
> use Javascript for this functionality? I'd typically only use this type of
> functionality to serve pages when javascript isn't enabled or you need to
> show various
Sorry for the double-message. Anyways, if you do want to do what that other
person recommended, simply find the View that the user is redirected to
after logging in. Then, modify the "context data" of that view to dump
whatever data to the template. And then do some magic in the template based
upon
Is the "Dialog Box" going to be presented using Javascript? If so, why not
use Javascript for this functionality? I'd typically only use this type of
functionality to serve pages when javascript isn't enabled or you need to
show various templates based upon the type of browser (for example, a
Mobil
On Tue, Jul 31, 2012 at 8:05 PM, Larry Martell wrote:
> I've only been working with django for 6 months, and I'm not really
> clear on how the login process works.
>
> I have a client that has a login screen created by a template. It has
> a submit button with:
>
>
>
> In their urls file they hav
I've only been working with django for 6 months, and I'm not really
clear on how the login process works.
I have a client that has a login screen created by a template. It has
a submit button with:
In their urls file they have:
(r'^accounts/login/$', login)
In their views file they call login
19 matches
Mail list logo
