Okay. I've been making a list of ideas for push enhancement proposals, so I'll put that on there. In the meantime, I need to figure out what's causing this problem.
On Friday, March 29, 2013 4:03:24 PM UTC-4, Chris Moffitt wrote: > > Back in the day, Django's cache was rudimentary and wouldn't support some > of our needs. That's why Bruce created an updated cache tool to simplify > life. I'm not 100% sure what the gaps are with the latest Django cache. > There may be opportunities to consolidate but I honestly haven't looked at > it in a long time to see what the work would be. > > Thanks, > Chris > > On Fri, Mar 29, 2013 at 2:53 PM, Rob Speed <[email protected]<javascript:> > > wrote: > >> That was a good suggestion, but it didn't work. >> >> I looked at payment.models.CreditCardDetail, which is what actually sets >> and retrieves the cached card number, and I'm kinda stuck. I haven't dug >> this deep into the payment module before, so I was surprised to find that >> it uses a library called django-keyedcache. Can anyone explain why satchmo >> doesn't just use django.core.cache? >> >> >> On Friday, March 29, 2013 9:47:10 AM UTC-4, Mike Hostetler wrote: >> >>> I'm away from my serves now so I can't tell you exactly how to fix this, >>> but I did run into it. I think you also have to configure cache the "old >>> way" for Satchmo to pick it up. Look at the Django 1.2 docs on caching. >>> >>> Let me know if it works. If not, I'll look at my setup when I get a >>> chance to get to my server. >>> On Mar 28, 2013 9:11 PM, "Rob Speed" <[email protected]> wrote: >>> >>>> Adding a bit more info. >>>> >>>> Satchmo: 0.9.2 >>>> Django: 1.4.5 >>>> Python: 2.7.3 >>>> python-memcached: 1.48 >>>> >>>> Here's my test to make sure the cache is working: >>>> >>>> $ manage.py shell >>>>> >>> from django.core.cache import cache >>>>> >>> from time import sleep >>>>> >>> def test(): >>>>> ... cache.set('does_this_work', 'Yes it does!') >>>>> ... sleep(60 * 4) >>>>> ... print(cache.get('does_this_**work')) >>>>> ... >>>>> >>> test() >>>> >>>> Yes it does! >>>>> >>>> >>>> My next step is to figure out what they key for the stored number is, >>>> then decrypting the value and seeing what happens. If that doesn't turn >>>> anything up I'll be completely lost. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Satchmo users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to satchmo-user...@**googlegroups.com. >>>> To post to this group, send email to [email protected]**. >>>> >>>> Visit this group at http://groups.google.com/** >>>> group/satchmo-users?hl=en<http://groups.google.com/group/satchmo-users?hl=en> >>>> . >>>> For more options, visit >>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>> . >>>> >>>> >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Satchmo users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/satchmo-users?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/satchmo-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
