Is there a way for KOOBOO search function works for, all internal site?
I mean search for contents of pages, views, html blocks and labels...
As I can understand, native search function works for only articles
Thank you, for your answer
I'm assuming that you're using a pretty recent version of Kooboo, V4.4.0 or similar. If you are, there are a number of search options available under the menu option: > Content > Search
Under there you can select which "content folders" are added to the search index. Given that Kooboo is a "Content Management System" this is the logical place to expect most of your data / content to be and how to control the way it is indexed.
I'm guessing that you already know about this options though, and this is where you are indexing your "articles"?
I don't believe that indexing of 'Views' and 'Labels' is supported. They are both too abstract concepts, they are components that are use to build other things. Trying to index them as separate items goes against the aim of the system.
One final area that my provide you an answer though is to look at the settings for an individual page. On the 'Settings' tab there is a tick box to tell the system to include the page content in the search index. This setting should allow "HTML blocks" to be included in the search index and may provide what you are looking for.
Related
On a WP-site I am using some div's with the class .exclude_from_search Therefore I would like these div's not to show up in the list of search-results. Is there any way to achieve this goal?
I found articles about excluding pages, categories, tags... But nothing about how to exclude classes.
The problem is basically that these div's contain always the same information. Something like "responsible: some name" If anybody searches for the word responsible, he will see all pages in the list of results. That is not helpfull.
I would suggest you to use a better search for that purpose. It is not possible to exclude an html element from wp search functionality per se.
The search looks for strings in your WP database. If a match is found, you see the result in your search results.
To get better control over your search results, and to implement a list of stop words and exclusions, you might want to try out the Relevanssi plugin.
It comes with an explanatory GUI and should provide you with needed functionalities.
https://wordpress.org/plugins/relevanssi/
I've yet to find that 2sxc has facilities for entering, browsing, filtering and otherwise allowing keyword based filtering/sorting. If so, is there documentation about this, or sample code perhaps?
I'd think it might also be likely that one could use DNN's pretty good capabilities for tags and categories, and also razor queries would enable this, but I'd sure love to see some examples/guidance on best practices for doing so from within 2sxc.
This is very easy to do, but it's much more advanced that just tags / categories.
Basically you
Create a new ContentType for the related information - like Tag, Category or whatever. It can have more fields than just a title, as a category could also have an icon
Add some of that data
Go to the content type where you want to use it, create a "Entity / Content-Item" field
Then go to the field settings, give it the name of the related info that is allawed and if 1 or more items may be added (category is often just 1, Tags is often many)
that's it :)
I think I've found a start on this at:
http://2sxc.org/en/Docs-Manuals/Feature/feature/2685
and the demo at
http://2sxc.org/dnn-app-demos/en/Apps/FAQ-with-Categories
Is there a module for Drupal that searches the final versions of the rendered pages (in the same way that Google would, for example) instead of all the nodes? The way I have set up my site involves views that display several nodes depending on what the page is. I don't want to search through each of the little boxes, but the finished version of the page instead.
For clarification, you are searching for a way to index the dynamic view content, and keep the search index out of the individual nodes?
I think your best bet is https://drupal.org/project/search_config
A lot has been added to Drupal 7 core, so that many 'search restrict' modules are now obsolete.
If this is still not what you are looking for, and you feel a bit adventurous, you can find various guides from before this was incorporated, and go the way of custom code. http://www.lullabot.com/articles/hiding-content-drupals-search-system
http://www.acquia.com/blog/drupal-search-how-indexing-works
If it is slick and stable, submit it back to the drupal community. They will be your friends.
I'm developing an online magazine, and am using Views to generate blocks for the homepage.
I am using a slightly customized Article as the content type for most of my data, with Views providing blocks with the necessary fields from those Articles. For example: the Latest Blogs View shows the Short Headline and Teaser fields, but the Top Headline View provides a block with the Image and Full Headline fields.
Right now I'm using Views to filter Article by tag, so Articles need to be tagged to show up on the homepage. Most of my blocks are lists and don't need the tightest sorting flexibility. However, some blocks are not lists, or it's important for the end user to have control over the display order of Articles in certain blocks. Is there a way to enforce site-wide 1:1 tagging for term:article relationships. For example, I want to ensure that only one Article is tagged top.news.1 (the first Top News slot), and likewise only one article is tagged top.news.2. When someone wants to add top.news.2 to an Article, the one Article that already has that tag will lose it. Or something like that.
I have played around with Views enough to gather that it is really powerful, so this level of microcontrol might not be necessary with the right configuration, but I think restricting taxonomy versus configuring Views filtration would address the problem more directly.
I've looked around the web and haven't been able to find anything really relevant. Sorry if I missed something obvious.
Thank you!
Is it correct that you (or your site editor) want the ability to:
spotlight a certain nodes
arbitrarily change the order of the spotlighted nodes, or add/remove a node from the spotlight while keeping the position of the other nodes?
If so, your best bet is likely Nodequeue, which does exactly that, and allows you to restrict the number of nodes spotlighted. It's very easy to use and our non-technical clients have no problems with it.
If your use case is different from that or requires more flexibility, Nodequeue may not be the right fit, but it works great for the specific example you're describing.
I'm looking at these two modules for a "Related articles" style listing:
Similar by Terms
Similar Entries
Any opinions on either of them? I have a tag system set up so searching by terms would be fine, but it hasn't been updated as recently as the other module. How reliable is "Similar Entries"? Anyone have any field experience with either?
I would also take a look at Content recommendation modules wiki in the Similar Module Review on groups.drupal.org.
Looking at Comparison of Similiar / Relevant by term block modules, Similar By Terms seems preferable because
There is a version for Drupal 7.
It has been updated at the end of July (Similar Entries has been updated on May 2009).
It caches the results.
If I would have to choose a different module, I would choose Relevant Content, which has also a CCK field that allows you to put a list of related nodes in each nodes you want.