2:00pm (yesterday): While reviewing site changes with our designer one day prior to launch, I noticed that the shopping cart functionality was screwed up. Badly. The site is using Commerce for Drupal 7, and when you change options for a product prior to clicking “Add to Cart”, it’s supposed to refresh the form with new details and an updated price. Instead, the form disappears. Obviously, this can’t be launched and fixed later. Continue reading Timeline of a bugfix
Probably not too practical in real life, but I wanted to see just how easy it could be to implement this. If you want a lazy way to automatically convert any normal HTML POST form (send email, submit information, etc.) into a quicker-looking AJAX form, here’s the quickest way to do it:
Continue reading How to AJAXify any POSTed web form
How to make your AJAX content crawlable by Google — as always, good stuff for developers to know.
However, if your application tends to hit the same addresses over and over again — say, to plot the location of restaurants near your business address — it’s possible to cache these lookups in a database. You’ll still be using Google to look up new addresses, but any user hitting the same address twice in the same day will use your database instead of Google’s service. Continue reading Caching Google Maps geocoding lookups
Solution: Use a server-side script that will retrieve the same data, requesting it over and over if an OVER_QUERY_LIMIT error occurs.