Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Search Plugin Not Working

See original GitHub issue

Bug Report

Steps to reproduce

fist time open docsify website , search plugin is working correct , after click some page , search-min.js throw error ，and search plugin not working any more , type something to search won’t get any thing response

What is current behaviour

when open some page

search.min.js:1 Uncaught TypeError: Cannot read property '/./IOT%E5%AE%89%E5%85%A8/360/360%20Phone%20N6%20Pro%E5%86%85%E6%A0%B8%E6%BC%8F%E6%B4%9E' of null
    at search.min.js:1
    at Array.forEach (<anonymous>)
    at i (search.min.js:1)
    at search.min.js:1
    at o (docsify.min.js:1)
    at o (docsify.min.js:1)
    at B (docsify.min.js:1)
    at r (docsify.min.js:1)
    at docsify.min.js:1
    at docsify.min.js:1

type something to search

search.min.js:1 Uncaught TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at c (search.min.js:1)
    at r (search.min.js:1)
    at search.min.js:1

What is the expected behaviour

Other relevant information

Bug does still occur when all/other plugins are disabled?
Your OS:
Node.js version:
npm/yarn version:
Browser version:
Docsify version: newest
Docsify plugins: search

Please create a reproducible sandbox

Mention the docsify version in which this bug was not present (if any)

Issue Analytics

State:
Created 3 years ago
Comments:26 (17 by maintainers)

Top GitHub Comments

1reaction

Ares-Xcommented, Oct 18, 2020

weird, from which version this is happening ?

IMHO, I think the problem since we set the search.index in local storage. As we all know, the browsers have default local storage size (about 5 M), and we stored all the markdown files strings as search.index in local storage. If the files strings r humongous (more than 5 M), we can’t set it in the local storage and cause the search err aboved.

https://github.com/wzpan/hexo-generator-search

Maybe you can refer to this save all markdown file strings to a local xml file

1reaction

Koooooo-7commented, Oct 16, 2020

weird, from which version this is happening ?

IMHO, I think the problem since we set the search.index in local storage. As we all know, the browsers have default local storage size (about 5 M), and we stored all the markdown files strings as search.index in local storage. If the files strings r humongous (more than 5 M), we can’t set it in the local storage and cause the search err aboved.

Top Results From Across the Web

How to Fix WordPress Search Not Working (5 Common Errors)

The first thing you need to do is install and activate the SearchWP plugin. For more details, see our step by step guide...

How to Fix WordPress Search Not Working (3+ Issues Fixed)

Use this detailed guide to fix WordPress search not working. Learn how to troubleshoot the common search issues in minutes.

WordPress search not working- How to fix in 5 minutes!

Install WP fastest site search plugin from WordPress plugin store. · Enter your WordPress website URL and click on next-> · The crawl...

Plugin Search problem - WordPress.org

Hi,. I'm having trouble searching for plugins through the dashboard. When searching a keyword it will just show the spinning search icon indefinitely....

Search Plugins not working - qBittorrent official forums

Re: Search Plugins not working ... move the directory named [nova3] to your desktop. start q bittorent click the search tab, and then...