nextcloud / nextcloud/fulltextsearch
JavaScript error in /apps/fulltextsearch/ with Nextcloud 34
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Steps to reproduce
- open /apps/fulltextsearch/
Expected behaviour
Search works
Actual behaviour
JavaScript error. Search doesn't work
Server configuration
Nextcloud version: 34.0.2
Details
fulltextsearch.v1.js?v=08c771df-2:20 Uncaught ReferenceError: $ is not defined
at new FullTextSearch (fulltextsearch.v1.js?v=08c771df-2:20:3)
at fulltextsearch.v1.js?v=08c771df-2:30:27
at fulltextsearch.v1.js?v=08c771df-2:32:3
FullTextSearch @ fulltextsearch.v1.js?v=08c771df-2:20
(anonymous) @ fulltextsearch.v1.js?v=08c771df-2:30
(anonymous) @ fulltextsearch.v1.js?v=08c771df-2:32
navigate.js?v=08c771df-2:490 Uncaught ReferenceError: $ is not defined
at navigate.js?v=08c771df-2:490:1
(anonymous) @ navigate.js?v=08c771df-2:490Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the error at /apps/fulltextsearch/ with Nextcloud 34.0.2 and inspect fulltextsearch.v1.js around line 20 and navigate.js around line 490, where both failures report that $ is undefined. Trace those files to their source or asset configuration and verify that search loads without either JavaScript error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100