Going through some of the various threads, this seems like something that you don't mind doing, so what would your thoughts be on merging the content type and content restrictions from Search Config and the UI options to match? Then I can put Search Config back to sleep (again).
More specifically:
* Merge in features of block_search / search_config for restricting individual nodes (or entities if you are keen) from the search.
I've done this via a single join in the access check query, so no significant overheads.
* Both a soft (form checkbox removed) and hard restrictions to content types (or bundles if you are keen).
Soft still allows results, just that the type can not be selected. Hard never shows the results. Any hard restrictions should also reduce available types on the form.
* Custom content type groupings to make the types filter more UI friendly.
Search config allows you to specify options like:
[] Standard pages (ie: page, book,etc) >> searches page,article,book
[] Personal blogging pages (ie: blog, forum, etc) >> searches forums,blogs
[] News items (ie: media_releases, etc)
[] All other pages (computed list not including page, book, blog, forum, news content types)
rather than
[] Pages
[] Books
[] Articles
[] Blog
[] Forum
[] Media releases
[] Random content type a
[] Random content type b
[] Random content type c
[] Random content type d
[] Random content type e
By the nature of the Search Config module, it is UI alters with restrictions added. However, all that we really require is the 3 features mentioned above and the maintainer of Search Restrict was impossible to work with, so I took this over and expanded the module to include these. With the concerted effort to merge features here, it would be great to remove what is now a nearly complete feature overlap.
Both modules are getting a fairly steady stream of new users, 100 to 200 per week
Closed: outdated
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.