Bug? You're viewing documentation for a previous version of this software

[heitorlessa]

Hey @trevorblades,

I'm hitting an odd issue that I can't quite reproduce in my own laptop, and I suspect it might be a deployment issue (GitHub pages).

This wasn't happening before I enabled DocSearch but I can't seem to draw a connection, and find it must be something else.

Supporting files/info

• Gatsby config
• page-layout.js LOC where this notification appears
• Recent changes
  • Enabled Search
  • Removed gatsby-offline-plugin

Reproducing

It doesn't work for me but somehow happens in other people's browser (chrome, firefox)

• Visit: https://awslabs.github.io/aws-lambda-powertools-python/
• Search for “metrics”, click in any result and see if you hit either of these
  • “You’re viewing documentation for a previous version of this software” might appear at the top
  • Side effect: search focus might remain despite you clicking on a result

Any pointers is more than appreciated - Screenshot below

[heitorlessa]

Managed to reproduce it! This only happens when you hit a search result that goes to a sub-directory (not Gatsby) that hosts other HTML files.

If you search for metrics, and select any result that has Module in its subtitle it'll hit this issue.

[heitorlessa]

I've updated docSearch to no longer show results for non-Gatsby website, and that works.

[trevorblades]

Oh this is an interesting bug either way. Thanks for reporting this. Is your current solution sufficient, or would you ideally still like to surface non-Gatsby results in your search?

[heitorlessa]

Hey Trevor, It’d be great to surface non-Gatsby results as I initially had the crawler to show both doc content + API reference (generated by another tool) For now, I’ve updated Docsearch to not index /api content: algolia/docsearch-configs@9406b63 —- That also made me curious about how to have docs for different branches (develop, master) — Is there somewhere I can learn how to do that? I think I saw WP GraphQL or another project example doing that with your theme. Thanks again for the support

…

On Fri, 29 May 2020 at 19:24, Trevor Blades ***@***.***> wrote: Oh this is an interesting bug either way. Thanks for reporting this. Is your current solution sufficient, or would you ideally still like to surface non-Gatsby results in your search? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#118 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZPQBBJYPVWKRNUQM4KV2TRT74UDANCNFSM4NNCLOZA> .

[heitorlessa]

Reopening as I've just noticed this also happens when you use footerNavConfig

                footerNavConfig: {
                    'API Reference': {
                        href: 'https://awslabs.github.io/aws-lambda-powertools-python/api/'
                    },
...

If I were to click on the link it causes this issue

If I refresh the page after hitting the issue, it works

[heitorlessa]

Reopening as I've just noticed this also happens when you use footerNavConfig

                footerNavConfig: {
                    'API Reference': {
                        href: 'https://awslabs.github.io/aws-lambda-powertools-python/api/'
                    },
...

If I were to click on the link it causes this issue

If I refresh the page after hitting the issue, it works

I shadowed the docset-switcher after some digging, and I add an explicit target attribute if known -- Full commit here

aws-powertools/powertools-lambda-python@29a6704