Jeff @ Pye Brook

the note column would certainly work... did you think about storing the notes as purchase meta? I am using the meta in my forks/plugins and it is working really well...

You might want to consider removing this functionality entirely from the system. If you want to keep it I have a plug-in that I wrote it does a pretty good...

There are a bunch of issues that made me go with a standalone plugin. First and foremost is that the XML attributes for each product type are much different from...

@JustinSainton jshint driven cleanup of changed areas, found and fixed another type/defect

I have some changes in the fork that I run that eliminates all variation related queries if a store does not use variations. I recall the the benchmarking I did...

What I think makes sense to hook the taxonomy update API on the admin side. When taxonomy terms are saved, we should check to see if there are any terms...

Ben, This makes perfect sense. I have been thinking about this also, in combination with multiple coupons and automatically applying coupon conditions. I have a store where we want to...

@benhuson agreed that there is a subtle difference between coupons and discounts, but not sure the manual action of adding the coupon code is the key differentiator. What I have...

The email address changes for the user, but the address tied to the order stays in place. Correcting the data collected checkout is also an issue for typos in shipping...

@JustinSainton along the same lines as the PR we did last night, this PR avoids many similar small unnecessary database calls when product variations are not being used. I recall...