what AEM version are you using?

 you could define all nodes in the path /apps/cq/core/content/nav/tools/ to nt:unstructured nodes (by providing a proper .content.xml or whatever way you prefer); because then filevault never falls back to its defaults (which is a nt:folder for a folder in your content structure). Then the simplest ...

With the filter root being<filter root="/apps/cq/core/content/nav/tools/general"/>all nodes you declared in the hierarchy (for example apps/cq/core/content) are ignored by the plugin and the content structure is build based on the default node type for structures (nt:folder). That means even when yo...

Do you have versions created for assets?

Are there any versions available for this page at all?

When you build your project locally, your deployment package embeds the JAR files in content packages (typically /apps/<project>/install), and AEM 6.5 and the SDK pick them up from the repository (using the JcrInstaller). In AEM CS this is not done anymore. There the build process extracts these bin...

have you switched on flexible mode?

I don't think that there is a comprehensive list of it. But you can try it out every selector before you choose to implement one on your own.

the connection target for the HttpClient should be the hostname and port of your solr instance.

You don't need to read all these properties manually, the HttpClientBuilder can do that for you if you use the proper methods (as shown in the screenshot). Also it seems that your solr URL looks like this: localhost:3128:URL/solr/...Which seems really odd to me. Please use the recommended way of Htt...