- New SQL enhancement for Scalability Pro to fix WooCommerce long-running query in the product-hero block - August 31, 2023
- Create a static favicon.ico to avoid surplus PHP requests for rush traffic - July 25, 2023
- Breaking Through WooCommerce Restrictions with Super Speedy Filters: The Power of Pretty Permalinks - May 10, 2023
I’m writing this from a ferry about to leave Venice for Greece and to my horror I’ve just discovered that there’ll be no wifi once we leave the port. It’s a 28 hour journey.
I had been planning on using the full day tomorrow to finally release the Faster Woo Widgets upgrade and the other updates that have collected over the past couple of weeks, but now it’s looking like I won’t be able to release these until Friday. I’ve had spotty internet over the past few days and rare chances to do much. Some personal changes meant that I ended up leaving for Greece this week rather than last, so my schedule is a little messed up.
What will be delivered this week?
Essentially the plan is to release Faster Woo Widgets – it’s a major upgrade – but I want to have permanent internet connectivity once it goes live in case any of you experience any issues at all. So that’s further delayed until Friday now.
I’ll take stock on Friday once the release is done to figure out what else can be released and try and get some other plugin updates out then too.
Other improvements coming
This is more of a Super Speedy Plugins development rather than a plugin development, but I’ve been working on my support robots to triage the requests that come in. I’m loving Intercom (the chat system) but it’s not perfect. The main problems are around visibility of issues at a glance, grouping of issues and ticketing. The robots I’m working on basically man the first-level chat support and help customers/visitors to:
- Find documentation
- Create a documentation request
- Create a bug ticket
- Create a feature request
I want to increase visibility and transparency of what’s being worked on as much as possible, and to make it so that when I answer/resolve/complete a doc-request/bug-ticket/feature-request, that the relevant parties are automatically notified so I don’t need to answer everyone individually who asked the same question, or submitted the same bug.
The chat robots will help with all of the above, but priority remains bug-fixes first – with chat-bot development happening at the same time to streamline support more and more.