Try the mkdocs search hack

[decentral1se]

Something for #3376.

Unfortunately, I couldn't test this (because mkdocs search actually works locally). For someone who has access to the RTD builder, I think you can build off a branch and view the documentation. Then just try to search something and see if you get the mkdocs search bar and not the broken RTD one.

\cc @mgsloan @borsboom

[mgsloan]

Haven't tested it, but it looks to me like this function won't be run, needs another () on the last line.

[decentral1se]

Ah yes, you're right. I should have listened to my JavaScript linter ;)

[borsboom]

@lwm I've copied your fixup-search branch to the main repo, and told readthedocs to build it. Unfortunately, all documentation builds seem to be failing for the last day with "An unexpected error occurred", so we can't actually test it yet. You should be able to push changes to the fixup-search branch yourself too.

[decentral1se]

all documentation builds seem to be failing for the last day with "An unexpected error occurred"

Hmm, seems like the RTD build needs some attention then. Any stack trace?

Feel like adding me to the RTD account so I can play around with it or?

(I pushed my fixups to the upstream branch as well in case the error is resolved).

[borsboom]

RTD seems to be failing most builds, but occasionally passing. I've made lwm a maintainer there.

[decentral1se]

Ugh, seems to be a bunch of these 'unexpected error' messages plaguing people, as far as I can see in readthedocs/readthedocs.org#2985. I'll keep an eye there but can't seem to get any good of it now.

[decentral1se]

I'll close this off for now and try to fix when things are clear on the RTD side.