#community-help

Suggested Improvement for Typesense 'Documents' Page

TLDR TJ suggested modification in Typesense documentation where clicking an updated version redirects to the same page, not the release page. Jason agreed and asked for a GitHub issue to track it.

2mo

Join the chat

Jul 26, 2023 (2 months ago)

Photo of md5-3afef4cc9e9291f4f991a88147c78384

TJ

08:13 PM

Hi Jason/Kishore, hope you're both well! Just want to say well done on the work you've done on Typesense and offer one tiny piece of feedback if I may: say I'm on the 'Documents' page on the documentation site and I get a warning that I'm viewing an old version, it would be great if selecting the new version takes me to the 'Documents' page on the new version rather than the version release page. I think the release page should only be a fallback if there's no equivalent page in the new version. What do you think?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

08:16 PM

Yes! 💯

Haven’t gotten around to it, given the complexity of tweaking Vuepress (the static site generator we use) to first check if the same page exists in a different Typesense server version, before routing to it…

08:16

Jason

08:16 PM

Could you create a GitHub issue for this, so we can track it?

TJ

08:18 PM

Thanks Jason! I'll create the issue soon

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Troubleshooting Typesense Document Update Error

Mehdi had an issue with updating Typesense documents which returned a '404 Not Found' error. Kishore Nallan after several debugging steps, discovered Mehdi was using an outdated Typesense version. The issue was resolved after upgrading Typesense.

26mo

Setting Canonical Links in Typesense Documentation

Jeremy suggested setting the default version to latest in typeSense. Dima proposed canonicalization and Jason confirmed its deployment.

1mo

Troubleshooting 400 Error When Upgrading Typesense Firestore Extension

Orion experienced a `400` error after updating the Typesense Firestore extension, causing issues with cloud functions. They traced the issue back to a data type conflict in their Typesense collection schema after updating. With help from Jason and Kishore Nallan, they resolved the issue by recreating the collection.

11mo