nextcloud / nextcloud/fulltextsearch

URL encoded password needed

Open
#851 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
234
Forks
64
Avg merge
6h 18m
Merged PRs (30d)
10

Description

I'm new to nextcloud ( 1 week old) and been battling with getting elastic search working with full text search for the last 4 days. I was often getting errors in the terminal of " username must be a string " or words to that effect , and similar errors like

An unhandled exception has been thrown:
TypeError: array_key_exists(): Argument #2 ($array) must be of type array, false given in /var/www/html/apps/fulltextsearch_elasticsearch/lib/Platform/ElasticSearchPlatform.php

Anyway, what i noticed and how i got around it was ... my password has a # on the end of it , so 123456# for example.
in the UI, i was making the address of servlet : http://larry:123456#@localhost:9200 This was the root of the problem. In the end i had to make it URL encoded http://larry:123456%23@localhost:9200 as it appears not to like having a # in the password field.

More so a tip for others in the future than a bug report as such, but worth taking note of i guess shrug i'm not a guru so this may be common knowledge, but i spent way to long discovering that and wanted to document it :)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no documentation file, test, or entry point. Review the full-text search Elasticsearch configuration and user-facing setup guidance, then verify how a password containing # is represented in the servlet URL. Done means the URL-encoding requirement and example are documented for future users.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch
Domain
search
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.