Availability of content search not indicated correctly in capabilities

[felix-schwarz]

Describe the bug

The availability of content search is not correctly indicated in the server's capabilities if content search is in fact not available.

Steps to reproduce

1. Log in at demo.owncloud.com
2. Check capabilities ocs.data.capabilities.search.property for content and it to be enabled - which is the case.
3. Upload file with keyword in content
4. Wait a minute to give the server time for indexing
5. Search for keyword in content

Expected behavior

File is found.

Actual behavior

The file is not found.

Additional context

The property at step 2 should indicate whether content search is actually available - either by omitting content in ocs.data.capabilities.search.property - or by setting its enabled value to false.

This issue was found during QA of server-side search in the iOS app.

[2403905]

I assume that FRONTEND_FULL_TEXT_SEARCH_ENABLED is false by default.

@kobergj Do we want to keep the full text search turned off by default?

[kobergj]

I wasn't aware the demo.owncloud.com is still working. That's good news. It holds 7.1.0 so it seems it is still deployed regularly. We should check why other platforms don't work.

Fulltext search needs an external tika service to run. So we can't activate it by default. But maybe that is the issue. If tika service is not working properly that would explain the behaviour. We need to check what is going on the platform.

[2403905]

I'll change the "content" according to the FRONTEND_FULL_TEXT_SEARCH_ENABLED value. It is still not guaranteed that the full text search if tika is down for some reason. It is not resolved the availability issue.