Smart filtering by date not working in WooCommerce Orders
Hi,
We’re filtering WooCommerce orders by date https://snipboard.io/AmDRqS.jpg but we never find results.
I disabled all the other plugins except for Admin Columns PRO + addons and WooCommerce. I’m using the latest version of all the plugins. I also disabled our theme to test this.
Can you check if it is a bug of your plugin?
Thanks
Can you tell me what type of column you used for your date column?
Is this the default Order column from WooCommerce or did you create your own column with our custom field column based on another field? I’ve tested the default Date column, and it seems to be working fine at a clean installation.
Ok, I see we’re using the post publication date for this. We use it because the client wanted to show the date in a date and time standard format and not the format “1 minute ago” or similar. Do you know if we can do this with the WooCommerce Order Date field?
Thanks!
Thanks for the input.
It seems that when you’re using the Publish date, it only will perform the search on posts with the ‘Publish’ post status set. This is the behavior you want when you’re on the post table, but in this case, it is now what you want.
As a workaround, you could add our Date column (with the purple icon before the column name) and select the ‘Created date’. It seems that the create date is the same as the publish date on my environment. Smart Filtering does work correctly for that column.
I have tried the field you mention and using the Date field https://snipboard.io/DA0Bsw.jpg (the one with the purple icon in front) with Creation option, it breaks my columns: https://snipboard.io/DAlrRF.jpg. I can’t see any php error in the log. Do you know what can cause the issue in this case? Thanks
I tried to reproduce the error with the same column settings, but I did not get any errors.
Since your overview really breaks, I expect a record in your error.log file.
Can you make sure if there is no information available related to this error in your logs?
You must be logged in to reply to this topic.