{"section":"known-issues","requestedLocale":"en","requestedSlug":"something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores","locale":"en","slug":"something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores","path":"docs/en/known-issues/Portal/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md","branch":"main","content":"## Summary\n\n\nIt is expected to search for any term in the Portal's stores; however, the letters \"A\" and \"P\" are not directly searchable via the URL.\nSo, a \"Something went wrong\" message will appear when accessing `/a` and `/p` routes in Portal stores\n\n\n##\n\n## Simulation\n\n\n\n1. Go to a portal store\n2. Go to the link `site.com/a` or `site.com/p`\n3. See a \"Something went wrong\" on the front\n\n\n##\n\n## Workaround\n\n\nN/A to `/a` path\nRegister a redirect in the legacy CMS from `/p` to `/?ft=p`"}