Full text search 0.8.0 - better integration & bugfixes


Thumbnails, menu and the possibility to edit your files directly from the search result

Almost RC

Status of the app was supposed to be upgraded to Release Candidate however I wanted to release that last beta including a lot of improvement, despite knowing there is still few issues with some remote file system.

Changelog

  • Better UI.
  • Better integration to the Files app.
  • in:filename and in:content will search only in the name of the file or only in its content.
  • show:hash will display for each result an hash of the indexed content; useful to find duplicate.
  • Improvement: Search is now triggered slowered while typing your request in the input field.
  • Bug fix: You can now search on the first word of a new line.
  • Bug fix: User never logged in: meta data of a shared file to a new user.
  • Bug fix: searching exact word.
  • Miscellaneous: OCR can be done on some images if using the Full text search - Files - Tesseract app.

Instructions

  1. Upgrade all apps
  2. re-index your content using:
./occ fulltextsearch:reset
./occ fulltextsearch:index
  1. Enjoy (or report issues)

How can i search for duplicates @cult?

Which image types should be supported?

Thank you!

It finds siamese instead of thai

:wink:

As of today, you have to manualy look at the hash and compare them :]
As said previously, searching for duplicate is an interesting feature but not for the near future

They look the same to me :smiley:
I will have a look to this issue.

@Cult, as you can see in my above screenshot, i don’t have any thumbnails and the menu on the right side is missing.

Screenshot of a search with the icon top right:

I have installed it on 2 different instances, both same same?

I’m running NC 13.04.

Do you have specific app or theme installed ?
Can you see if your browser have issue loading some css file ?

No, i don’t think so. I’ve tried to disable the Theming app, but it had no effect.

Here is a list what i have installed:

Enabled:

  • activity: 2.6.1
  • audioplayer: 2.3.0
  • bookmarks_fulltextsearch: 0.8.0
  • bruteforcesettings: 1.0.3
  • calendar: 1.6.1
  • comments: 1.3.0
  • contacts: 2.1.5
  • dav: 1.4.7
  • dicomviewer: 0.0.6
  • federatedfilesharing: 1.3.1
  • federation: 1.3.0
  • files: 1.8.0
  • files_external: 1.4.1
  • files_fulltextsearch: 0.8.1
  • files_fulltextsearch_tesseract: 0.1.0
  • files_reader: 1.2.3
  • files_sharing: 1.5.0
  • files_texteditor: 2.5.1
  • files_videoplayer: 1.2.0
  • firstrunwizard: 2.2.1
  • fulltextsearch: 0.8.0
  • fulltextsearch_elasticsearch: 0.8.0
  • gallery: 18.0.0
  • groupfolders: 1.2.0
  • impersonate: 1.0.4
  • logreader: 2.0.0
  • lookup_server_connector: 1.1.0
  • metadata: 0.6.0
  • nextcloud_announcements: 1.2.0
  • notifications: 2.1.2
  • oauth2: 1.1.1
  • password_policy: 1.3.0
  • previewgenerator: 1.0.9
  • provisioning_api: 1.3.0
  • quota_warning: 1.2.0
  • serverinfo: 1.3.0
  • sharebymail: 1.3.0
  • systemtags: 1.3.0
  • theming: 1.4.5
  • twofactor_backupcodes: 1.2.3
  • updatenotification: 1.3.0
  • workflowengine: 1.3.0

Disabled:

  • admin_audit
  • encryption
  • files_pdfviewer
  • files_trashbin
  • files_versions
  • survey_client
  • user_external
  • user_ldap

No, only warnings about HSTS. https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Strict-Transport-Security

I’m having the same issue. No special theme installed and all CSS files are loading with a 200 response code.

ok, was able to reproduce the bug.