New
- Highlight search query on click
You can now interact more easily with search results. When you click on a query, it’s automatically highlighted so you can instantly see what you searched for. - Visual updates to the default template
We’ve made visual improvements to the default template. You can now customize the price field in the filters by adding a currency prefix and choosing whether it should include an input field.
Improvements
- Easier SDK selection in custom templates
We’ve improved the dropdown for selecting an SDK. The newest version now appears at the top, making it quicker and easier to choose the latest option. - Faster, smoother search experience
We fixed an issue where repeated searches could slow things down. Searching is now faster and uses less memory, especially on the staging environment. - Enhanced Younium Integration and Testing
- Enabled Younium to run on a second development environment for more robust testing with test data, allowing for better validation before production rollout.
- Added the
last_seenfield to the settings column for Younium integration, ensuring that each usage update is accurately tracked. - Conducted comprehensive testing of various Younium scenarios, including order linking, usage key handling, and integration table updates, to ensure all edge cases are covered and logged appropriately.
Restored and improved search settings
We’ve brought back and fixed two settings: Allow empty queries and Enable result item click. These now work as expected again. We also fixed an issue with the Google search setting, so your search queries are now handled correctly.- Removed chargify subscription creation when adding new sites
To simplify site onboarding, the process of automatically creating a Chargify subscription when adding a new site has been removed. - Script to put all active chargify subscriptions on hold
A new script was developed to place all active Chargify subscriptions on hold, making it easier to manage subscription states in bulk. - Change from id to ordernumber for Younium
To improve data handling and clarity, the system now uses order numbers instead of IDs for Younium, making it easier for users to track and manage orders. - Simpler process for adding a new site
We’ve made it easier to add a new site by removing an automatic step that could cause confusion. The process is now more straightforward and easier to follow.
Bug fixes
- Fixed an issue where the default template did not respect the results limit set in the user experience configuration, ensuring the correct number of results is displayed as configured.
- Resolved a problem where the style attribute was not removed when switching view attachment types in the Javascript Client V2, leading to a cleaner and more predictable UI.
- Fixed an issue where the Allow empty queries and Enable result item click settings were not working in the V2 User Experience page, ensuring these options are now available and functional. The Google search query parameter in preferences has also been restored to working order.
- Fixed an issue where questions 1 through 5 were not being displayed in the Laravel performance email, ensuring all questions are now visible as intended.
- Fixed an accidental merge that caused the system to use Keycloak for authorization instead of AWS Cognito, restoring proper login functionality by switching back to Cognito.
- Resolved an issue where v2 user experience settings did not update the default custom template, ensuring that changes in user experience are now reflected in the snippet as expected.
- Fixed a bug where not all code was using the new average counter for SKU on the dashboard, ensuring consistent metric calculations.
- Addressed a performance email issue where users with subscriptions on multiple periods (daily, weekly, monthly) received duplicate daily emails on the weekly day, ensuring correct email delivery.
- Resolved an SQL error that occurred when adding a new site, caused by a missing default value for the 'v2_allow_empty_query' setting. A default value was added, preventing the error from recurring.
- Resolved an issue where analytics clicks data would not load on first view for Mertens; now, only the top 500 clicks are fetched to prevent timeouts, and users are prompted to contact support for exports. Additionally, protected images now display the title if the image cannot be loaded.
- Fixed an accidental merge that caused the system to use Keycloak for authorization instead of AWS Cognito, which prevented logins; the system now correctly uses Cognito for authentication.
- Fixed a build pipeline error by resolving the missing 'node-sass' (CSS compiler) module for the Recommendations frontend, ensuring successful builds and deployments.
For slower browsers, the template now waits for the correct language to load before rendering, improving consistency.
We’ve also updated how languages are handled: en_US is no longer the default fallback, and if you’re not using custom translations, the template won’t try to load unnecessary language files.
We fixed an issue where customers couldn’t change the language in Settings.
We resolved a problem with template files not loading correctly due to a configuration issue.
SDK’s above .9 where not selected for default template because of order in finding the latest.
We fixed an issue where changes to the Language setting could cause V1 customers to be switched to their browser’s default language.