Plugin Support
slash1andy
(@slash1andy)
Automattic Happiness Engineer
Hey there!
There have been a few responses there in the ticket since this was posted, so I will mark this as resolved here for now at least (so that we can keep working on the ticket).
Hey Andrew.
Just for the record marking it resolved here doesn’t mean it’s solved.
Disabling https://wordpress.org/plugins/advanced-woo-search/ solved this issue. I’m leaving it here as a temporary workaround until a fix is released.
-
This reply was modified 5 years, 7 months ago by
progital.
No solution and the support isn’t actively trying to fix it.
Hi there @progital,
I do see that we’re having a conversation via our ticketing system now.
We’re experiencing longer than usual response time at the moment, but please be sure that your concerns will be addressed in the next ticket update.
Enjoy the rest of your day and stay safe!
Plugin Support
slash1andy
(@slash1andy)
Automattic Happiness Engineer
We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.
Guys, really?
This was the last response from your support!
We're not the authors of the Advanced WooCommerce Search plugin, and don't have any special integration with them, so it's hard for me to tell in what way a search plugin could affect product import results. Having that said, I've passed all my test results and observations to our developers and I'm waiting for their feedback now. We'll let you know about any news on this.
The ball is in your court and has been there for almost two weeks now. Why don’t you actually fix issues instead of closing the ticket? Oh, I get it, simply closing the ticket is much easier.
-
This reply was modified 5 years, 6 months ago by progital.
Hello @progital
I took a look at the ticket you’ve referenced in the original post (#3250161) and it was automatically marked as solved by the system since it did not receive a response from you for ~ 6 days.
Having said that, I see that my colleague has indeed forwarded the details over to the developers. I just wanted to give you a quick update here and let you know that this issue is on the developers’ list.
I do not have an ETA on the fix yet, so I’d recommend keeping an eye out for the changelogs to confirm if the behavior is fixed.
Howdy!
We haven’t heard back from you in a while, so I’m going to go ahead and mark this thread as resolved. If you have any other questions please start a new thread.
Cheers!
Hey Aashik.
You seem to be contradicting yourself because you confirmed in the previous post that “this issue is on the developers’ list”. I’m not your developer so it’s not clear what exactly you want to hear from me. I can only re-iterate that there is no fix and you are consistently trying to sweep it under the rugs.
Hi there!
The issue I referred to in my previous post regarding the ticket you have with us at WooCommerce.com is still on the developers’ list.
The GH repo is private, so you would not have access to the repo itself, which is why I requested to keep an eye out for the changelogs.
This ticket was closed as there were no new questions regarding the same. Is there anything else we could assist you with – in this forum topic?
This topic refers to a specific issue that hasn’t been solved even though it has been confirmed and “is still on the developers’ list”. I believe the status of this topic should reflect the status of the problem and that is “not resolved”. In case someone arrives here via search and so on.
Closing the woocommerce.com ticket and marking this topic as resolved produces a false impression that the problem has been solved.
I believe the status of this topic should reflect the status of the problem and that is “not resolved”. In case someone arrives here via search and so on
I hear you. That said, the best way to keep an eye out for a fix regarding a particular bug is not by looking at the status of the forum topic, but the changelogs.
This is because even if the forum topic doesn’t get a response henceforth, the changelog will always be updated every time there’s a new update for the extension.
Sorry, but I don’t understand this. Why would you mark this topic resolved when it’s not? It’s very misleading. There is a bug, you haven’t fixed it and you close this topic as “resolved”.
I don’t know, maybe something is wrong with me but check this out https://www.merriam-webster.com/dictionary/resolve
– you haven’t dealt with this issue successfully
– there is no answer or solution
Clearly it’s not resolved.
