remove double semi-colons
Add 'County' as region label for UK
* add 'County' as the region label for UK
* Incremented database version, added update routine for next version (13)
Allow save of new custom checkout items
create unique name for custom items so that they can be stored into the database
resolves issue #1239
Added additional missing field to format statement
Make sure checkout form unique name is actually unique
* Make sure legacy data has a value for the unqiue_name column, handle collisions
* Make sure table column index on unique name fields exits
fixed typo
Save check box value fix
* When check boxes are saved the contents of the attribute value are used as the WPeC meta value
* When check boxes are checked/not checked if the meta value is the empty string the check box stays unchecked, otherwise a non-empty string checks the box

Resolves issue #1236
Handle boolean meta value in a more backwards compatible way
The shipping same as billing meta value can be stored in several different ways depending on the version of WPeC that saved it.  Added a utility function to convert an arbitrary value into a bool with just a little more intelligence than a cast or checking a non-empty string.
Merge branch 'master' of github.com:wp-e-commerce/WP-e-Commerce into branch-3.8.14.1
Revert to 157c9762b3fe2e804fa3c710b47815d22d51f35e
Merge branch 'branch-3.8.14.1' of github.com:wp-e-commerce/WP-e-Commerce into branch-3.8.14.1
Merge branch 'master' of github.com:wp-e-commerce/WP-e-Commerce into branch-3.8.14.1
Resolve improper merge of master by simply removing the 2.0 theme engine.  Getting late, getting sloppy.
Remove wpsc_core_store_use_shipping() in favor of wpsc_is_shipping_enabled()
We had inverted logic in wpsc_is_shipping_enabled().  This is why best practices dictate positive flags.
Save data immediately when data map is initialized
* also clear dirty flag when saved
removed debug code
Merge branch 'branch-3.8.14.1' of github.com:wp-e-commerce/WP-e-Commerce into branch-3.8.14.1
Clear temporary data, whether in cache or in transient
* Checks options tables for transients and delete them if appropriate
* Fires action hooks so themes, classes, plug-ins, shipping modules all can know when data needs to be cleared, or has been cleared
* Updated functions to use new clear data function rather than just wp_clear_cache
remember names of transients as they are set so we can clear them specifically
no mass flushing of WordPress cache
handles upgrade automatically by looking at database on first run