Thanks Mike,

Where did you find this information about the credit card info + cache? For
the life of me, I can't find anything in the docs about this.

I am not feeling the love for the Satchmo docs for a bunch of reasons right
now.... but anyway, I digress.

It is not that I don't want to use caching in production. I have a problem
where the cache doesn't seem to be invalidating in some cases, and I am
therefore diving in to Satchmo's caching and just trying to understand what
is going on (particularly, how it is different from Django's built in
caching, or not).

So, my first step was to work out how to turn caching off...

Also, is it possible to use Johnny Cache with Satchmo? Or, a Redis cache?

I am also wondering, concerned, why could you get a memached backend
working with Satchmo? This is fairly trivial to setup with Django projects
usually.

thanks.

*Paul Walsh*
0543551144



On Thu, Nov 8, 2012 at 4:15 PM, Mike Hostetler <m...@squarepegsystems.com>wrote:

> I'm surprised no one answered this. I'll take a shot . .
>
> You can't. Or you can, but then you can't sent credit card info to the
> payment processor. One of the decisions made in Satchmo was to use the
> cache to persist the credit card number from one screen to the next. I'm
> not going to express my opinion on that decision . . .
>
> But why don't you want to use caching in production? That really doesn't
> make a lot of sense -- a properly configured caching system is worth the
> time in any Django app. I did have some problems with Memcache so I
> switched it to a database cache and that has helped a lot (YMMV with
> Memcache -- I actually would rather use that than the database cache).
>
>
>
> On Nov 7, 2012 10:14 AM, "Paul Walsh" <paulywa...@gmail.com> wrote:
>
>> I want to disable caching in Satchmo, in production.
>>
>> I can't find anything in the docs that explicitly declares how I can
>> managing Satchmo's caching.
>>
>> I'd love a pointer to the right place in the docs, if there is one, and
>> also if anyone know hows I can disable caching.
>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Satchmo users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/satchmo-users/-/S2MNqFXmnPkJ.
>> To post to this group, send email to satchmo-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> satchmo-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/satchmo-users?hl=en.
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Satchmo users" group.
> To post to this group, send email to satchmo-users@googlegroups.com.
> To unsubscribe from this group, send email to
> satchmo-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/satchmo-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Satchmo users" group.
To post to this group, send email to satchmo-users@googlegroups.com.
To unsubscribe from this group, send email to 
satchmo-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/satchmo-users?hl=en.

Reply via email to