Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lunr.jp failed to load at v2.1.1 #605

Closed
cxlwill opened this issue Nov 22, 2017 · 3 comments
Closed

Lunr.jp failed to load at v2.1.1 #605

cxlwill opened this issue Nov 22, 2017 · 3 comments
Assignees
Labels
bug Issue reports a bug resolved Issue is resolved, yet unreleased if open

Comments

@cxlwill
Copy link
Contributor

cxlwill commented Nov 22, 2017

Description

Just upgrade material from v1.1.2 and change the config to new format. Everything works well except site search.

When jp search is configured, 3 Uncaught TypeError happened.

Uncaught TypeError: Cannot set property 'stemmerSupport' of undefined
    at lunr.stemmer.support.js:1
    at lunr.stemmer.support.js:1
    at lunr.stemmer.support.js:1
tinyseg.js:1 Uncaught TypeError: Cannot set property 'TinySegmenter' of undefined
    at tinyseg.js:1
    at tinyseg.js:1
    at tinyseg.js:1
lunr.jp.js:1 Uncaught Error: Lunr is not present. Please include / require Lunr before this script.
    at lunr.jp.js:1
    at lunr.jp.js:1
    at lunr.jp.js:1

Since the code has been compressed, I format them and find that problem may relevant with
_.TinySegmenter = t in tinyseg.js OR r.stemmerSupport = { in ·lunr.stemmer.support.js`

But I cannot see any TypeError, any idea?

@squidfunk squidfunk added the bug Issue reports a bug label Nov 22, 2017
@squidfunk
Copy link
Owner

Will investigate, thanks for reporting!

@squidfunk squidfunk self-assigned this Nov 22, 2017
@squidfunk
Copy link
Owner

Fixed in #607

@squidfunk squidfunk added the resolved Issue is resolved, yet unreleased if open label Nov 22, 2017
@squidfunk
Copy link
Owner

Released as part of 2.2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue reports a bug resolved Issue is resolved, yet unreleased if open
Projects
None yet
Development

No branches or pull requests

2 participants