Foxy Forum Status

We're no longer responding to questions via our forum, but we will keep it up for historical reasons. If you can't find the answer you're looking for, please visit our knowledge base or contact us. If there's enough interest in the future, we may bring the forum back.

1.0 / 1.1 bug for {{ custom_cart }} introduced on 2/7/2013 and fixed today.

lukeluke FoxyCart Team
in Important News edited February 2013
A couple of weeks ago, we made a mistake.

A significant performance improvement for the way stores handle templates was discovered and, against better judgement, we implemented a quick change to versions 1.0 and 1.1. The change involved pulling something from a cache instead of hitting the database with every store request.

Because of our excitement about the potential improvement of this change, we pushed it out quickly on 2/7/2013 and did not go through as rigorous of a testing process as we should have. The change impacted stores who are taking advantage of the custom cart include template in twig and the {{ custom_cart }} place holder. The custom cart text was not being stored in the cache correctly so, at times, the cart template would be empty. Because some requests are served by fresh data in the database and others come from cache, it was a tricky issue to discover.

We just pushed out a fix for both 1.0 and 1.1 and are watching things very closely.

We sincerely apologize for any negative impact this has had on your store. Please let us know if you see any other issues related to this thread.
  • Thanks again for looking into this one. Glad to hear you were able to track down the issue and release a solution while still maintaining the performance improvements. :)
Sign In or Register to comment.