nullkohol

Hi @jaysupport , we were also wondering about this issue. Maybe you can find out where this comes from or how to solve this with custom css without breaking anything else.

Here you can find the same with the updated plugin (now version 2.4.8). everything else (WP version Theme version etc) is the same. The larger space between the categories is clearly visible.

Hi @mohsinbsf ,

thank you for trying to help. Did you try with different locales? Obviously there’s some kind of “translation” error related to the time.

I don’t know how I can open a ticket at your website. Your links forwards me to the contact page.
I also tried to file an issue on Github, but there you don’t seem to take issue reports.

To be honest, I am very disappointed regarding this lack of service. And I think it’s also inefficient for you. While I understand that this is free software, it’s not necessary to put obstacles for a user who wants to give bug reports. The issue occurred here before and the solution is not visible because you didn’t really help back then either. Maybe the issue was solved, maybe not. Now we have the same problem and we all start from zero again.

Hi @shahzeenfarooq , thanks for your answer. Could you share the link again? It doesn’t work. I’ll be happy to support that request. I actually already started a request myself, but then realised that this new behaviour differs so much from what was there before.

I am sad to hear that there are no plans to change this soon. We have been waiting for the new filters for a year now and were so happy to see they were released! But in this state they are not usable for us 🙁 I really wonder why that was decided because it really breaks the logic and doesn’t make any sense at all to me.

Hi @lovingbro thanks for your kind words. That’s the least I can do for a software that I use for free 🙂 I already reviewed WC, so I cannot do it again I think 😉

Hi @mosesmedh , thank you for trying on 🙂

I switched to Twentytwentyfour theme, but nothing changes in the import (looks like it’s starting, but then nothing happens).

I am currently installing WooCommerce Analytics to see if that helps. However, it says in the plugin details that it’s still in early access/beta stage. That’s not something I would easily install in a productive system. On our test platform I don’t mind.
Also now I see a message “WooCommerce Analytics requires Order Attribution to be enabled.”. If I remember correctly, this is a feature that I didn’t enable for good reasons. This is the kind of tracking I don’t like. As above, I can do this on our test platform, but I hope this is not supposed to be the solution for our prod environment.

While I was looking around to see if this new plugin helps, I thought of something else: Our testing environment is hidden and can only be accessed with credentials. We know that this sometimes causes problems when importing data that was exported from another WP environment. In this case here, we import data from the same database, right? But there seems to be some external process involved because … switching off this security feature actually solved the problem!!! I was able to import historical data and now I see statistics :):):)

So I don’t understand why, but in this case the problem was access from outside to our environment.

Thank you, @mosesmedh and @shahzeenfarooq for your support 🙂
I hope this thread will help other people facing the same problem.

Hi @mosesmedh , thank you for trying to help. Yes, I found many threads regarding problems with Analytics and importing historical data, but as you said, it always was a different cause and never fit my circumstances.

Here’s my test setup (most stuff deactivated because of the various problems).

Looking at WC Scheduled Actions, I don’t see any entries at all for wc-admin_import_customers. That’s strange. I see something for wc-admin_import_orders though. Most recent one was completed:

1. 2025-08-14 19:05:16 +0000
   action created
2. 2025-08-15 11:07:31 +0000
   action started via WP Cron
3. 2025-08-15 11:07:31 +0000
   action complete via WP Cron

Hi @saivutukuru,

thanks for looking into this and for explaining. Makes perfect sense to me and that’s very likely the reason for the behaviour I am seeing.

I am trying to adapt my code to WC10, however, unfortunately I directly ran into this old bug. I’ll post my findings there, since from what I see, this bug is still active even though this report I found is from 2021.