Added Cookspin wp-content folder;
Minified scripts and CSS, and added (preliminary) memcached cache;
Fixed permissions issue on signup; other small fixes; sort of made Cookspin into a PaaS, transforming service, website and cost functions into WP plug-ins which can be activated on demand (though it's still very preliminary and no charge is made -- which isn't the ideal situation yet); other small fixes;
Fixed an undefined constant error
Fixed a parse error on single_recipe.php
Fixed several bugs from last update, especially on registration and cost cache (costs are no longer cached unless a cost_index is provided)
Removed caching from get_recipe_total_cost, which wasn't really working
Small improvements in the rendering of cost timeline
Fixed a bug which would insert empty price mods, which would in turn mess up the number formatting functions on orders; fixed a bug which disallowed localized floating points on price mods (would generate warnings or not even register the price mod at all, which was a bit too extreme);
Added a script to fix some Warnings caused by a previous bug
Code clean-up
Fulfilled date on Stream stripes now account for timezone / gmt offset
Complete overhaul of costs timeline: versions are no longer compared in different lines, but plotted in the same line to reflect the actual cost calculated by the Food / Service streams; version changes are also annotated within the timeline, which seem to be what bump or reduce the costs the most (therefore, the most relevant information it can show); also removed plugins from the settings screen, until they become live);
Updated some translation strings
Made important changes in the way we clear the object cache, after discovering that our object-cache plugin was ignoring the request to flush; but it's hopefully even better: now we check what keys the object has cached and we clear only those, thus keeping the rest of the cache intact (which, in theory, has no reason to be cleared);
Restored user management for non-pro sites
More test to mitigate s3 fail
More config changes for s3
Code clean-up;
File uploads and deletions now properly update the storage quotas (and there is also a proper check before uploading files in case user has exceeded his quota), regardless of local vs. S3;