Bugs

Users that are set to "Internal Viewer" can generate an article via "Create Article Via AI" from the Chrome Extension

If we use "Mark as Published" or "Change Access Level" the changes aren't applied

Although all images have the exact same size and alignment, they all look different in the editor and frontend

Here are the details of our setup and the issue: API Calls Used: Delete: DELETE https://ksr.helpjuice.com/api/v3/articles/{id} Publish: PATCH https://ksr.helpjuice.com/api/v3/articles/{id} Body: json { "article": { "published": true } } We have tried both PUT and PATCH for these operations. The actions themselves (deleting or publishing articles) work correctly, but the webhooks for these events are not triggered. Webhooks Configuration: We have the following webhooks set up: question_create → working question_update → working question_delete → not triggered question_publish → not triggered When publishing, the question_update webhook is called and we can work with it. However, the specific question_publish event is never fired. For deletions, the question_delete webhook is also not triggered at any point. Could you please check if there is an issue with these webhook events on your end or let us know if additional configuration is required? Thank you for your assistance!

When we search for a keyword on the main page, the top search result is the article we expect. However, when we search the same keyword on a category page, that same article is 18th in the results.

If we do the exact same search on the extension, sometimes it finds results and sometimes it doesn't. On the KB, the search works as expected.

When the glossary article is manually published, it triggers a bug where the search functionality and alphabetical filtering stop working as expected.

In the glossary article, both the search functionality and alphabetical filter (A–Z) are only working when the article is accessed with the en_US language code in the URL.

When the Swifty chatbot tries to fetch popular questions from a customer’s KB (e.g., /popular_questions.json), the request fails with a CORS error in the browser. However, this is not due to missing CORS headers on our end (If the user set the allowed origin successfully). Instead, it’s caused by the customer’s SSO configuration, which redirects unauthenticated users to their Microsoft login page (302 redirect). Since the response is HTML (login form) instead of JSON, and lacks the expected CORS headers, the browser blocks it. Root Cause: The /popular_questions.json endpoint is behind SSO protection. The embedded script runs on unauthenticated sessions, triggering an automatic redirect to Microsoft SSO. This redirect leads to a CORS error due to the unexpected response type and missing headers.

I can't seem to find the option to use alternate row shading in tables in the new editor. It is present when switching to the old editor (which I did as a work around) but for some reason was not carried over into the new editor.