Start typing your WooCommerce question.
These two columns were removed in version 3.11.0 when support for WooCommerce 2.2:
order_discount was removed as well.
These two columns remained after WooCommerce 2.3 was released for backwards compatibility and no longer apply as version 2.3 introduced changes to the coupon system – more details here: https://woocommerce.wordpress.com/2014/12/12/upcoming-coupon-changes-in-woocommerce-2-3/.
Since it’s no longer possible to have both order discounts and cart discount, the WooCommerce Customer/Order CSV Export extension now only has a
I suggest that you apply the required changes in any integrations using the CSV export to work with the current state of columns exported and replaces any uses of
order_discount with just
A good technique to resolve problems is to break them down and simplify them. This is best done by recreating the scenario you are dealing with but with minimum effort.
Lets say you are troubleshooting a WooCommerce Bookings issue. You have this elaborated product with perfect configuration. Everything was working fine yesterday, but today the booking process has stopped working as it should.
You have tried everything. Toggling all different features, tried on different browsers, checking every configuration, but the error pertains.
Sometimes data written to your WordPress installation gets corrupted. This corrupted data impairs the functionality. In that case you cannot alleviate this by editing what you see. Corrupted data must be replaced. It must be written anew.
The fastest way to do so is to create a new instance of what you are working on. Troubleshooting one of your products? Try this:
Do this for all components involved. If you are troubleshooting a WooCommerce product with Product Add ons or a product add on form such as Gravity Forms, create a simplified copy as well.
If that did not change anything, a complete reinstallation of the components involved might alleviate the issue.
Completely deinstall your involved plugins.
Then do a fresh installation.
Here is a checklist for you to go through all steps of resolving conflict on your WordPress and WooCommerce site. Scroll down for detailed information for all steps. Happy troubleshooting.
WordPress is simple and stable out of the box. As you customise your site with a custom theme and plugins and custom code, conflict can occur. Parts that you use to compose your website sometimes collide. They can block each other from resources or have identical names in the code that confuse each other. The result is always the same, something goes south.
Your feature stops working. A page layout capsizes and moreover this can come over night since your site is getting constant updates to maintain stable performance. Therefore you should always have a backup ready to deploy.
Checking for conflict is mandatory for every troubleshooting case. But before you check for conflict, you should always first apply all pending updates.
Update all the things:
Did I mention you need a working backup at all times? Before you do that, please do make a full backup.
If your issue is unfazed by applying all updates then the next step is to check for conflict.
Here is how:
When troubleshooting you need to rule out many factors.
This must be taken out of the equation, when looking for the source of your problem. Only then can you be certain that there is a causality between the cause and effect you are observing.
This post reflects solely my personal opinion. It is not affiliated or supported by Automattic or WooCommerce in any ways.
When you buy an extension at WooCommerce.com you buy three things.
As long as you have a valid subscription these three features get provided. The extensions will not cease their functionality once your subscription has been voided. Meaning you can run the software for as long as you like. You will however loose all access to the above mentioned services once your subscription has run out.
You may also install all software on as many sites as you like. But you can only activate your licence through the WooCommerce helper for the number of sites you have a valid subscription key for.
In summary this is what you get:
Lets look at item number 2.
Most people struggle with a clear definition of what support encompasses. Here are my personal definitions of support and its distinction to similar fields.
For each item there are two roles. Customer and support agent.
From item 1-5 the “who does what” shifts. Lets call the customer ‘You’ and the support agent ‘I’.
From item 1-5 the amount of work that is done for you and the complexity of the task increases. As a result consulting is much more expensive than service. After all knowing what you want is the most challenging task not only in business but in general.
Information on WooCommerce extensions is found in mainly two places.
This defines the scope of the products. If a feature is neither teased in the product page nor described in the documentation it is not included.
If you need features outside the scope of the products, that this is considered a customisation. A customisation is a modification of the product to embed a feature that is not available. The WooCommerce support team does not do modifications for you, because they only offer support for features that are within the scope of their products.
Ideal starting point: You test it until you can reproduce the issue at will. If one of the WooCommerce support team members can reproduce the issue at will as well by following your instructions, it is within the scope of the product. For testing it is mandatory that only WooCommerce.com software is active. Everything else: themes or plugins of different provider or custom code that was added must be deactivated while testing.
You may notice that I refer to WooCommerce.com software as an extension? Why not plugin? It is because an extension plugs-in into another plugin in this case WooCommerce and not WordPress. Since they extend a plugin, they are called an extension.
WordPress and WooCommerce are in a constant state of update. This is good, updates keep your site stable. If all your WordPress site components are built modular and there is no overwriting of files, the updates will keep your site running smoothly, because they all get applied, no problem.
But if there are components that get overwritten they are excluded from the update process. Imagine this example:
Lets say WooCommerce plugin would only consist of two files.
But your theme overwrites one of them. So instead of the structure above we have these files present.
Now WooCommerce receives an update. If there are no overwrites all files get recognised and all updates get applied. The expected result is then.
But an active theme overwrite means the present file is modified and does not get recognised, thus it does not accept the update. In this case we now end up with this.
WooCommerce scans and automatically knows when it gets overwritten. It then serves this message:
Clicking the purple button redirects you to our documentation that explains the concept of template overwrites.
WooCommerce also provides a system report that lists all the overwritten files. You can find it at
Scroll down all the way to “Template Overwrites” to view the file list of overwritten WooCommerce template files. Here is an example screenshot of what this looks like:
The best way is to use WooCommerce template debug mode. This disables all template overwrites while maintaining your current theme active.
You can also selectively dequeue assets your theme loads with the “Asset Queue Manager” plugin. Be careful though, this is for advanced users only. It dequeues assets site-wide, that may render your theme useless.
If this does not change anything you should check for Plugin conflict as a next step. Plugin Organizer is a stealthy way to do so. I made a video tutorial on how to use it.
When your CSV import fails or produces incomplete results, most of the time your CSV file is either missing data or it contains incompatible data.
The first thing you should check are your header columns. We have column header reference help pages that give you a complete overview over supported column titles and the data they accept. Here they are for both extensions:
Check each column title for unsupported or faulty titles. Correct misspelled or incomplete titles. Unsupported titles not listed in our reference must be removed or their column title changed to a supported title.
To get you started faster we also offer sample CSV files:
Oftentimes I find that faulty CSV files contain data that should not be present. Take a look at this screenshot:
As you can see here, data for the column
post_id must be empty in your CSV because they are automatically assigned by WordPress.
Check each column for incorrect or superfluous data. Correct column data by renaming column titles for incorrect data. Superfluos data must be removed.
If you have checked your CSV files and found no unsupported or faulty data, then it might be that your server is not up to the task. Try importing your CSV on a clean test system.
I provide the necessary infrastructure at http://wcdemo.com. Creating a test site is free so feel free to head there now and test your CSV file.
And as always boys and girls, backup your data before you attempt any CSV import.
By RRZEicons – Own work, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=18462316
Ever wondered what the ‘favorite’ button does when you browse the WordPress plugin repository?
I use the feature a lot to bookmark plugins I like.
Here is what it does and how to use it: