Hello,
Following up on my previous issue, I’d like to offer some targeted suggestions to further enhance the Fast Woo Order Lookup plugin. These suggestions are designed to improve user experience and address specific potential issues:
Performance+Data Validation: Given the concerns raised here , here & in FAQ, implement a feature in the settings page to verify that the plugin does not cause unnecessary slowdowns and that the trigram tables are correctly generated and maintained.
WP-CLI Support: Enable trigram regeneration via WP-CLI to facilitate maintenance during off-peak hours and to allow those with the capability to automate this process, recognizing that not all hosting environments support WP-CLI. Like the other plugin by the author named: Index WP MySQL For Speed
Dependency Declaration: Explicitly state WooCommerce dependency in both the plugin’s documentation (readme) and code, ensuring that users are aware of this prerequisite before installation.
Documentation of Trigram Table: Document that the trigram table is named wp_fwol in the readme.md to enhance transparency, especially as the table size grows.
Compatibility Alerts: Note potential conflicts with other WooCommerce search plugins and provide guidance on reporting these issues for resolution. Example issue for reference.
Order Count Warning: Introduce a warning message for stores with fewer than a certain number of orders, as the plugin may not perform as intended in smaller datasets.
These enhancements aim not only to improve the plugin’s functionality but also to reduce the support burden if the plugin becomes very popular. Such preventative measures can help avoid negative reviews stemming from misunderstandings about the plugin’s requirements and capabilities.
Hoping for continued success and health for many more years! (30 years if you can keep up ?? )
]]>Hello,
I appreciate the Fast Woo Order Lookup plugin, but its use of trigrams has raised some questions for me. I find the concept intriguing, yet it prompts me to consider its implications further. Trigrams like “cat” from “cater”, “caterpillar”, and “category” highlight potential overlaps affecting search relevance, which can be especially challenging for stores with fewer orders.
Given this, it might be beneficial to mention that this plugin is best suited for larger stores. Could we consider an automated system for updating or verifying the integrity of the trigram table to mitigate these issues? Also, how often would you recommend regenerating the trigram table to ensure it remains up-to-date?
Alternatively, it might be helpful to clearly state that this plugin is not suited for everyone and that potential users should understand its implications. This clarity can prevent unnecessary support requests if the plugin becomes very popular. Often, negative reviews stem from misunderstandings, and it’s not fair for an author to face criticism over issues that don’t pertain to every user.
Thanks for considering these enhancements. Looking forward to any updates you might provide.
Link for reference (author article): https://www.plumislandmedia.net/wordpress-plugins/fast-woo-order-lookup/#how-does-it-work-trigrams
]]>Hello,
I have spent 2 hours translating all possible strings from English to French for the plugin (including readme/changelog). The translations are 99% accurate. In cases where they might not align with more veteran translators, I have specified the reasons. I adhered closely to WordPress translation conventions as well as the rules of the French language.
Additionally, I utilized the GPT-4 (old model) to enhance productivity and verify contexts to ensure they were applied correctly. This effort was made to ensure the plugin’s French localization is both precise and contextually appropriate.
Given the quality and accuracy of the translations, I believe they are ready for direct production implementation.
Thank you!
https://translate.www.ads-software.com/projects/wp-plugins/fast-woo-order-lookup/stable/fr/default/
]]>I installed and testing the plugin for staging and live versions. The first thing I noticed is when plugin is installed, it immediately stops the search by name, email, id etc. in admin > wooCOmmerce>orders page. However on my staging site, it did work after taking a several hours. I think it stops the search untill the indexing is done. The orders are around 25K. I installed and gave indexing the same amount of time but still it is conflicting with order search by name, email and others, working for ID though. Could you check and let me know how exactly I can see if indexing is done or not, the progress bar or notice doesn’t sustain or provide any info on that.
After installing it, If I still have option to search the orders by name, email address and so on, even the indexing is not complete yet, that would be a great thing.
Once it is working, the load time is perfect like I can see on staging.
Hi!
After activating the plugin the ability to search order by the order id is not working anymore.
Thanks
Hi Ollie, first of all – thanks a lot for addressing this super urgent issue. We have read this thread here: https://www.ads-software.com/support/topic/backend-edit-products-extremely-slow-80-seconds/ and then decided to install your new plugin. The tables were created in around 3 hours (we have around 400k orders in our database). We can see the action scheduler ran successfully. We can see order lookup appears to be faster BUT we still have HUGE slowness when opening an order (gateway timeouts). Are there any other suggestion on what we can do or why your fix is not working? We are on Woocommerce 8.9.3 and use WP Rocket.
In a message in the above mentioned thread you commented:
That regression disrupted stores with many orders. Root cause: A SQL query was added to fetch the distinct non-private meta_key values from wp_wc_orders_meta. The way it worked was very slow. (A full scan of the table is required to satisfy the offending query.)
Changing it to use the same pattern as a similar query in core resolved the problem. Here’s the place in my plugin that patches the query. That change is in WooCommerce’s 9.0.0 code. (not 8.9.0)
Are you sure this patch is still working with ver 8.9.3?
Thanks a lot and have a nice day
Sebastian
]]>Hi! Love the idea for this plugin. It appears that there should be a tabled called ‘fwol’ that is created by the plugin to index the trigrams. However, I don’t see that happening in testing. Any ideas?
Thanks!
]]>