We’ve been making some major updates to Folksy recently and wanted to let you know what we’ve been doing and why you might have been seeing some errors.
As part of our focus on improving the buyer experience for buyers:
- we have just launched a new dedicated Christmas page at Folksy Christmas on Folksy
- we’re redesigning the item pages
- we’re working on a better search experience
To make these changes possible, we need to make some significant changes to Folksy’s full system. As a result, we have seen a few issues in the past couple of weeks:
‘Shop Search’ was broken for a while on Thursday night. This was a bug caused by an update to our search libraries that we hunted down and fixed as quickly as possible.
‘Item Search’ has also been affected. We will be making updates to the search strategy to give more refined results but, in the meantime, when a user searches for an item they will be shown many more results than usual, with the most relevant items still appearing first.
Some people experienced issues on the homepage this weekend, particularly those browsing on (possibly older) phones. We think this is because there have been changes to Folksy’s assets (such as images and styles) that older devices haven’t picked up.
In this situation we’d advise people to clear their browser caches for Folksy.
We tested the changes pushed last week on a selection of modern browsers on phones and desktops before deploying them, but when making any changes at this scale there are always edge cases that are difficult to check. However, we will be looking into identifying which devices/browsers were struggling and potentially finding a way to include them in future tests for significant releases.
Earlier today (Monday 1 Nov), we had a 10-minute window when people were unable to sign in. This was due to a bug in a low-level change that we were unable to identify until it went live. We rolled back the changes as soon as we spotted the issue.
We are continuing to push low-level updates this week. While we are constantly monitoring site performance, please email our support team at firstname.lastname@example.org if you spot any serious issues (eg broken pages) and mark the ticket as ‘urgent’.