Version 3.5.3: Whitespace, Add-on Order

On October 22 FoxyCart rolled out a change to the entire system which may affect your store. All strings coming into FoxyCart are now being trimmed for whitespace at the beginning or end. If your product name or code has whitespace at the end, this will cause validation to fail and your product won’t be able to be added to the cart. In FoxyShop 3.5.3 this has been patched so that product names and codes are being trimmed before being written out to the $product array. It’s recommended that you upgrade now.

If you had dropdowns that were hidden by a dkey, the JavaScript was still using these dropdowns to select price, code, and ikey. The system has been adjusted so that any hidden select or radio buttons will not be used when calculating price or ikey and will also be ignored by the shopping cart so you don’t get the values of hidden dropdowns in your product attributes in the cart. If this breaks your current functionality, there is a workaround. You can set a javascript variable on the single product template (near the top of the page) to disable the new functionality: var foxyshop_skip_hidden_selects = 1;.

There’s a new feature that lets you customize the order in which the product add-ons are displayed. You can simply enter the ID’s separated by comma in the order in which you’d like them to appear.

There was also a bugfix where add-on products weren’t working properly in the admin if the “related products” feature wasn’t also selected.

Version 3.5.2 was released last week which removed some erroneous “NOT FOUND” text on the order management page and added responsive CSS to the admin so that the variations look better on narrower screens.

FoxyShop Starter Theme for Twenty Eleven

If you’ve tried to install FoxyShop with Twenty Eleven (the current default theme for WordPress) you already know that things look a little wonky. It’s not terrible, but the margins are off and everything just takes some tweaking before it looks right.

To help you get started faster, I’ve put together a starter theme that you can use as a child theme for Twenty Eleven. Or, you can just grab the header and footer files and chuck the css into your existing stylesheet. Either way, this should save you at least an hour getting Twenty Eleven and FoxyShop to play nicely.

Download Theme

Dec 2011 UPDATE: Theme updated on December 19, 2011 to add z-index: 1; to #branding. TwentyEleven 1.3 changed this so that the header was floating over top of the cart modal.

Jan 2012 UPDATE: The downloadable version has this included, but as of version 3.9, you will want to change line 8 of the included foxyshop.css file from #foxyshop_container #content to .foxyshop #content since moving the #foxyshop_container inside the header includes affected this theme. This only applies if you are running a version of this theme you previously downloaded.

April 2012 UPDATE: I’ve made some responsive updates to this theme so that it will scale better at lower resolutions. These changes are at the bottom of foxyshop.css if you’d like to upgrade your existing theme.

Version 3.5.1: Patches

Here’s a rundown on some patches in the just-released 3.5.1:

We received a report that FoxyShop wasn’t working with WordPress Multisite. The problem had to do with some of the plugin’s filenames causing WordPress to do some unexpected things. This has been solved and it looks like FoxyShop is working fine in Multisite now. Just be aware that any constant definitions will be applied across all sites on the network. There may also be an issue with the product sitemap in the root. Let me know if you run into anything.

FoxyShop recently started using a preg_replace shortcut for newline splitting on dropdown variations which wasn’t working as expected at all times. This has been corrected.

Pricing adjustments have been added to the price totals in the default receipt template.

I got a report that if mcrypt wasn’t installed the tools page won’t load properly. I’ve added a check on tools page to ensure that mcrypt is installed and display a notice if it isn’t.

In testing for WordPress 3.3 (scheduled for the end of November) FoxyShop was throwing one notice regarding a stylesheet insertion. This has been corrected in this patch and FoxyShop is now fully 3.3 compatible.

The upcoming FoxyCart 0.7.2 has added user-editable transaction attributes. FoxyShop has been updated to support this feature. Additionally, if you are running 0.7.2 you’ll now have an added tool in the FoxyShop Tools page–you can update your FoxyCart templates from directly within the FoxyShop admin thanks to the new API tools in 0.7.2. Remember, 0.7.2 isn’t available to the public yet, but when it is, FoxyShop will be ready for it.

Tutorial: Color Swatches

If you’ve ever wanted to have color swatches with your theme, here’s a guide and some sample code to turn this feature on. This method allows you to set HTML color codes and/or set color swatches for each color. Then it looks for any variation called “Color” and turns it into a clickable color swatch list. If you set ikeys, the main image will change also!

(continue reading…)

Version 3.5: Saved Variations

Version 3.5 is a smaller release but has a feature which will really help out stores that make a difference for stores with a lot of complicated variations.

Saved Variations
Go to the FoxyShop Tools page and you can add saved variations. These are just like normal variations but can be saved and added to many products. Then, when you change the saved variation, it will automatically change all the products at once. It’s a simple way to quickly roll out or manage a complicated variation structure across multiple products quickly.

Product Paging on All Products Page
Up until now, the FoxyShop paging wouldn’t work on the All Products page. That has been corrected–make sure to grab updated code from the foxyshop-all-products.php template if you want this feature and have customized your all products template code.

A Few More Things:

  • Rolled back filter that was removing spaces from variation modifiers. Caused inventory bug with codes that had spaces in them.
  • Added uninstall.php to properly clean up after plugin files are deleted
  • Recommended plugins tool improved
  • Added more filters