Closed (fixed)
Project:
Amazon Store
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Dec 2009 at 21:17 UTC
Updated:
18 Apr 2010 at 23:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
rfayHere's the patch to prevent caching of the cart page.
Committed to HEAD http://drupal.org/cvs?commit=303194
Comment #2
rfayComment #4
usera commentedthe patch errors with 2.0rc1 with
Hunk #1 succeeded at 748 (offset -22 lines).
Hunk #3 FAILED at 1890.
1 out of 3 hunks FAILED -- saving rejects to file amazon_store.module.rej
Comment #5
rfayThis has been long since committed. Please use the dev release and report your results.
Thanks,
-Randy
Comment #6
Terko commentedI still have this problem with the latest dev. Maybe it's something different than caching. I don't have this problem on the same install, different site and UC Cart.
Comment #7
rfay@teri: If you have any of the modules that turn off sessions for anonymous users, you'll get this result as well. See #575526: Amazon Store module incompatible with no_anon (No Anonymous Sessions) module.
If you want to get me a copy of your codebase and database I'll take a look at it when I get a chance. You can put them somewhere and send me a contact telling me where they are.
Please test that turning off page caching in admin/settings/performance solves the problem for you. If it does not, then we have a different issue.
Comment #8
Terko commentedThanks rfay! But the problem ... disappeared. I don't know exactly how. I tried to add $GLOBALS['conf']['cache'] = FALSE; in few places, this didn't worked but after few hours the problem disappeared (maybe there still was caches). So I didn't remember where exactly I've put them. But now it works fine! :)
Comment #9
rfayWell, you shouldn't have to do that.
You can diff your file against the dev version to find out what you did. Just download (I assume it's the dev) and then use any diff tool to check.
If there is in fact a problem, we need to solve it for other people.
Remember, there will be future revisions of this, and if you hack the files and don't know what you did, an update will overwrite... and you'll have your bug again.
Comment #10
rfayMarking fixed - reopen if you have this problem again.