HI All,
I upgrade nextcloud to version 31.0.0. Now fulltextsearch is not working anymore.
I get the errors when i try to run elasticsearch (full text search0
Failed to construct console command ‘OCA\Files_FullTextSearch\Command\Configure’: Could not resolve OCP\ILogger! Class can not be instantiated
Failed to construct console command ‘OCA\FullTextSearch\Command\Check’: Could not resolve OCP\ILogger! Class can not be instantiated
Do you mean, perhaps. v31?
files_fulltextsearch has not been released for v31 yet.
Yes,
Im sorry indeed version 31.
When will this be released? Also nemories app is not showing thumbnails for pictures. Is this also a bug
hmm,
i also got some issues with the memories app. Pictures are not opening normal. Also picture previews is not working as expected. i restored my early version of nextcloud and will wait some time till everything is upgraded for nextcloud 31.
Yeah, I mean, Memories is not yet listed as compatible with Nextcloud 31 either: Memories - Apps - App Store - Nextcloud
I’d say take this as a lesson to always check that all apps you rely on are compatible before upgrading to a new major release.
Also, in my experience, it is generally a good practice to wait for at least the first point release before upgrading your production instance to a new major release, because at least in the past, X.0.0. releases have more often than not required, shall we say, some additional polish to be ready for prime time 
Not a bug. The Memories app should have been uninstalled from your instance as it is not compatible with Nextcloud 31 yet. In fact, in all three instances I manage, Memories was uninstalled automatically.
If it was not uninstalled, your upgrade might not have been done properly.
@ckruijntjens - Do you have memories and files_fulltextsearch force enabled (and likely listed in app_install_overwrite in your config). That would override all compatibility checks during upgrades and explain how you ended up in this state.
Indeed. i got this in my config thats why memories and other apps are working with the newest nextcloud. (or try to work)
Anyone run into the incompatibility with Elasticsearch already?
I upgraded my instance to v31yesterday and noticed that every Elasticsearch command crashed with an “OCI/ILogger something not available” message.
After some back and forth I noticed that it’s the Elasticsearch file plugin which creates the error. When disabled the error message is gone, but obviously without file indexing Elasticsearch is of not much use.
I also found this note Upgrade to Nextcloud 31 — Nextcloud latest Developer Manual latest documentation which confirms that the iLoger API has been discontinued with NC 31.
So I guess the Elasticsearch files plugin needs code changes to make things work again.
@tomz I moved you post to a thread which you could have found yourself using search
upd: maybe relevant problems existed with nc30 already Using Nextcloud 30 - search modules become more and more incompatible
Thank you,
Indeed. when will the search modules be upgraded so we can use them again?
Which version of fulltextsearch_elasticsearch do you have installed?
There was a new release published yesterday for both 30 and 31.
Yes indeed.
However the modules for files and tesseract are not upgraded. So the fulltextsearch does not work as it should.
Right now none, because when trying to download earlier today the message said that versions are not compatible.
I meanwhile also stumbled over this get rid of ILogger by ArtificialOwl · Pull Request #285 · nextcloud/files_fulltextsearch · GitHub which probably is the fix you mentioned.
Checking the projects website GitHub - nextcloud/files_fulltextsearch: 🔍 Index the content of your files I can see that the last release is v24 and 3 years old, while my Nexctloud shows me the last update to be v30 and 6 months old?
Am I looking at the right thing?
Nevertheless, the git repository shows a commit which seems to address the logger issue posted yesterday.
But given that there is no release to download, what’s the best way to install this update?
Edit: Sorry, just realized you were talking about a different plugin, the fulltextsearch_elasticsearch plugin I am running is on v31. If I now find a way to get the files plugin, I mentioned higher up, updated from the git repo I may be good to go again.
Edit2: There is progress Incompatibile with NC 31 / iLoger · Issue #319 · nextcloud/files_fulltextsearch · GitHub
If you are like me and don’t like to wait:
Thank you. This worked perfect. How will this continue with official nextcloud upgrades? can i use the normal upgrade procedure and will it the upgrade fulltextsearch_files? Of do i have to do this manual ?
Again thank you for your feedback!
I am as impatient as you
composer install --prefer-dist --no-dev
make: composer: No such file or directory
Where’s that composer binary supposed to come from? Anything else I’d need to install?
Edit: Nevermind got it sorted out. If someone else is as ignorant as I am, check this page to get composer: Composer
I am running docker so had to install compose inside the container, but things worked out in the end. No more errors and the indexer is happily indexing my data again.
No, when the official release comes out it should just update. Do check if nextcloud has write permissions on the manual placed app dir!