Blog Sections Open
Including Resource IDs in AjaxSearch Results
How to make AjaxSearch find documents by both title and numeric ID when content names are too similar to use alone.
When many resources share similar titles, managers often want search to match not just the page title but the numeric resource ID too. AjaxSearch does not do that automatically, so you need to expose the ID as searchable data.
Practical Approach
If the snippet does not search core IDs directly, copy the ID into a dedicated TV or searchable field and include that field in the extraction logic used by AjaxSearch.
The goal is simple: let editors type either the title or the known resource number and still land on the right document.
Why This Helps
- similar product names become easier to distinguish
- support teams can search by resource number from the manager
- editorial workflows become faster on large installations
Keeping YAMS Pagination on the Current Language
How to stop Ditto pagination from sending multilingual visitors back to the default language when using YAMS.
Fixing EvoGallery Image Paths Inside a Shopkeeper Cart
Why product thumbnails can disappear during Shopkeeper cart recalculation and how to keep EvoGallery image paths stable.