Exclude pages in indexed search - typo3

I have a TYPO3 6.2.31 instance. How can I exclude pages from the search?
And if they are already indexed how can I remove them from index?
Thanks

Depending on your search engine you could use the flag "exclude from search" in the pages properties (your search engine should respect this flag).
Removing pages from an index normaly needs a rebuild of the index.
Some search engines check and respect visibility at the time of search, but as your pages still are available the finding will not be removed from results for you.
Disabling indexing based on the field no_search ("exclude from search"):
[globalVar page|no_search = 1]
page.config.index_enable = 0
[global]

Related

TYPO3 backend searches

There are two different search fields in TYPO3 backend - as in attachement.
1 - search displayed above list and page module
2 - main TYPO3 backend search
(https://ibb.co/vQZGTq0)
Does those searches use different configuration?
I have some custom table and field which I want to be searched against in case of search 1 and 2. In my table TCA I have added my field to searchFields.
I can find my record by search 2. but not 1.
Search 1 only searches on current page, while search 2 searches within whole installation.
Therefore if you record is on a different page then currently selected, it will only be found by global search (2).

TYPO3 Extension ke_search, results from news and tt_content

I try to config extension ke_search. I created Indexer Configuration for tx_news, pages and tt_content.
For Page Indexer, in area "Content element types which should be indexed" I wrote "text,textmedia,textpic,bullets,table,html,header,uploads,tx_news,news,gridelements_pi1"
When I Start Indexer I get result for indexing for page, news and content. So I think thats all good.
But when I search any word from news or tt_content, in the fornt-end, I have no result. If I search page - I have result.
Ensure you set pid in "Record storage page of search data" in News indexing record. It seems to 4 news was indexed successful, so this may be a reason it doesn't find it later.
You don't have to set "tx_news,news," in Page indexing. These content types doesn't contain anything valuable to index, it's only plugin instance, so it will index things like header of that plugin element. But no news records, for that you use your News indexing config.
Check backend module Faceted search -> droplist option Indexed content. Select your Search Storage and investigate what's indexed for Type: news, does the field Abstract / Content contains anything? Are the pids correct?

List all "incoming" internal links / references to a TYPO3 element

I need to get a list of elements linking to a specific TYPO3 page or element (all IDs oder pages, that link or refer to a this element). I thought this was at the Info module, but I can't find it.
I have spent hours finding this info on the web and even in my oldschool TYPO3 manual book... nothing, but I know that I once had this list.
Thanks a lot in advance! (version is TYPO3 4.6, I am preparing an upgrade right now)
You could search your database manually to find such links. I will start to give you a list where you could search for.
Find tt_content headers which link to a page, element or any url:
SELECT * FROM tt_content WHERE header_link NOT LIKE '' AND deleted = 0;
In RTE fields, you could manually check.
Go to backend modul 'Configuration', choose '$TCA (Tabel configuration array)' and search for 'RTE'.
Then you schould get all RTE fields, which could have links set to any TYPO3 pages or elements.
Like fx: tt_content.bodytext.config.wizards.RTE...
These fields you could search for any links vis MySQL
SELECT * FROM tt_content WHERE bodytext LIKE '%<link%' OR bodytext LIKE '%<LINK%' AND deleted = 0;
Maybe someone can add more default fields not listed above.
I think you have seen the references of a record normaly seen in the list module.
If you hover your mouse over the count you get a list of origins.
That list is not always up to date and the usability of the origins differs from version to version. Sometimes you can use the origins as direct link to edit the origin record.
Maybe you had an extension which enhances the usage.
In gerneral: if records are used with TYPO3 (TCA group fields which build relations to other records with uid-lists, or mm-records) this is also stored as refrence.
As links are also relations they are not always stored as referenes, espeacially if the link is inside a textfield.

Typo3 - Indexed Search how to order results by page title?

Inside the advanced options of the Indexed Search result page, there is an option to order results. While all other options are working fine, the two fields inside "Order by" have no influence on the results order.
The configuration page of indexed search has an option "basic.flagBitMask" where it says you can increase the importance of and tags, but setting it to "128" to increase the title importance has no influence at all.
How to get this options working or is there another option to show results with the searchword in the title on top of the results list?
I used the default index_search.tmpl which comes along with the extension.
The Typo3 version is 7.6.6, Indexed Search version is 7.6.0.
This problem seems to be a bug. In current versions of Indexed Search ordering is not possible when MySQL driver for Indexed Search Engine (indexed_search_mysql) is used.

Search pages with a Tag in CQ5

I am working on a custom search component in CQ5. I need to search for 1 or more tags selected by user using checkboxes. I tried using an earlier query to search text (select * from cq:Pagecontent where...)
I tried using :
select * from cq:PageContent where cq:tags like '%mytag%'
but it is not working. There are 2 pages which have 'mytag' as tag.
Any suggestion on how to do it ?
The following query is working for me. I'm searching here for for the following tags marketing:interest/services and marketing:interest/product
//element(*,cq:PageContent)[#cq:tags='marketing:interest/services' or #cq:tags='marketing:interest/product']
At the moment I would still go for XPATH, because of the better performance then SQL2.
When searching for a tag I also would avoid wildcards as they are not necessary if you are searching for an exact tagname.
Wildcards can negatively influence the performance of your query.