Category: Search

I upgraded a Tiki21 (Tiki created somewhere Tiki16/17) to Tiki22 and started to use elasticSearch. (it is possible somewhere in the past elasticSearch was used once).

I have errors with the elasticSearch not being found while it recreate one for each index rebuilt

Using the shell (fallback is not working):
{CODE()}
bernardsfez@server001:~/public_html$ php console.php i:r -p --log
[15/10/2020 09:12] Started rebuilding index... logging to file: /tmp/Search_Indexer_elastic_bernardsfez_console.log

Unified search
--------------

Engine: Elastic, version 7.9
< 1 sec/< 1 sec [>---------------------------] -- Rebuilding...
In Connection.php line 568:

no such index [bernardsfez_main_5f87e83d6e0c7]


index:rebuild [--log] [--cron] [-p|--progress]


bernardsfez@server001:~/public_html$ php console.php i:r -p --log
[15/10/2020 09:12] Started rebuilding index... logging to file: /tmp/Search_Indexer_elastic_bernardsfez_console.log

Unified search
--------------

Engine: Elastic, version 7.9
< 1 sec/< 1 sec [>---------------------------] -- Rebuilding...
In Connection.php line 568:

no such index [bernardsfez_main_5f87e8502c33a]


index:rebuild [--log] [--cron] [-p|--progress]


bernardsfez@server001:~/public_html$ php console.php i:r -p --log
[15/10/2020 09:12] Started rebuilding index... logging to file: /tmp/Search_Indexer_elastic_bernardsfez_console.log

Unified search
--------------

Engine: Elastic, version 7.9
< 1 sec/< 1 sec [>---------------------------] -- Rebuilding...
In Connection.php line 568:

no such index [bernardsfez_main_5f87e855170e6]


index:rebuild [--log] [--cron] [-p|--progress]


bernardsfez@server001:~/public_html$ php console.php i:r -p --log
[15/10/2020 09:12] Started rebuilding index... logging to file: /tmp/Search_Indexer_elastic_bernardsfez_console.log

Unified search
--------------

Engine: Elastic, version 7.9
< 1 sec/< 1 sec [>---------------------------] -- Rebuilding...
In Connection.php line 568:

no such index [bernardsfez_main_5f87e857ac63c]


index:rebuild [--log] [--cron] [-p|--progress]
{CODE}

If I use the web interface I have a different warning (no error but it may use the fallback):
{CODE()}
Warning

Elasticsearch does not support optimize.

Rebuild Index

Your index was last fully rebuilt on Thursday 15 October, 2020 09:12:58.

Unified search engine: Elastic, version 7.9, index bernardsfez_main_5f87e86a73dfb

Unified search engine fallback: MySQL, version 10.3.23-MariaDB-0+deb10u1, index index_5f87e86c95c36
Indexed

trackeritem: 97
tracker: 11
trackerfield: 72
blog post: 3
article: 50
file: 218
file gallery: 18
comment: 6
user: 7
group: 8
wiki page: 39
category: 19

Fallback search engine

Fallback search index was rebuild.
Execution Statistics

Execution time: 4 secs
Current Memory usage: 13.3 MiB
Memory peak usage before indexing: 2.8 MiB
Memory peak usage after indexing: 15.2 MiB
Number of queries: 14088
{CODE}
On Tiki admin search page I see:
{CODE()}

Client Node: server001
Elasticsearch Version: 7.9.2
Lucene Version: 8.6.2
Cluster Name: elasticsearch
Cluster Status: yellow
Cluster Node Count: 1
Index bernardsfez_pref_en: 2374 documents, totaling 1,486,770 bytes
Index bernardsfez_main_5f87e86a73dfb: 548 documents, totaling 1,662,738 bytes
Node server001: Using 733,190,144 bytes, since 2020-10-15 09:33:10
Field Count Tried on Last Rebuild: 184
{CODE}
But the field "Elasticsearch current index" show a different index being used "bernardsfez_main_5f87ece0dd927". I keep reseting this field to the default (empty) but index id keep coming-in.

I tried to set this field value to "bernardsfez_main_5f87e86a73dfb" (as displayed in the elasticSearch node info but after a new rebuilt it is changed again.

dev.tiki.org is not very usable with unstable Elasticsearch :(

The preference "Except included plugins" no longer appears to work. Put another way, plugins listed in the preference are not indexed.

This could also be by via category system (with perms)

Seen on dev.tiki.org {sign user="marclaporte" datetime="2013-11-26T13:18:26+00:00"}

{img fileId="745"}

Hello,

On my system :

__feature_sefurl don't functions normally.__

Important : Subject feature_sefurl : last version 5.1rc1 (current yesterday but may be before). The feature_sefurl don't functions normally (I have not searched why, I don't look at in details to this part).

__So if the option is activated all url(s) as

__''site/<page name> ''__

fail and any action, particularly page-object-display (magnifier icon) reaches a 404 error. __

nota : naturally, if the option is not activated the url generated for display of pages is :
__
''site/tiki-index.php?page=<page name> ''__

which functions normally.

trebly

ref-B00805-01

Some AJAX services can trigger errors. Since {commit id=33686}, there is a mechanism for services to report such errors. Unfortunately, this mechanism is based on PHP's sessions. Errors are displayed at the next regular Tiki page load, which may or may not be related with the request which causes the errors displayed.

This mechanism used to be implemented in lib/errorreportlib.php. Starting with Tiki 16, it was replaced by the Feedback library, but the approach hasn't changed and remains unreliable in Tiki trunk as of 2018-10-11. The Feedback library uses the tikifeedback element of $_SESSION.

This mechanism was first used by lib/search/searchlib-unified.php, but has since been spread widely, as can be seen in the commits which created the Feedback library ({commit id=58746}, {commit id=58747} and {commit id=58748}). One specific issue which can occur as of Tiki 18 is, after going to tiki-admin.php?page=search (which calls the lookup action of the search controller), to get a "Malformed search query" error at the next page load, which could be on tiki-admin_actionlog.php for example.

''This happens at the same time of this https://dev.tiki.org/item7677-Index-error-on-tiki-tracker-built-in-fields-and-BLOB-TEXT-error-after-recent-update-of-Tiki22 but it look now it is different''

On a second brand new Tiki22 created from scratch (a week ago) on my local I'm improving a previous Tiki21 site adding a new page with a customSearch.

This is a wiki page with a pluginList and 2 smarty templates (searchresults.tpl and search.tpl)
I don’t use lastmodif or sort by date on any of those. During my first work sessions everything was ok.

Somewhere around the end of it I enable the "Search" checkbox on one field at "trackerfields4" (tracker4)
Back to the same a day later and I have an error about lastmodif poping up.

Field lastModif does not exist in the current index. If this is a tracker field, the proper syntax is tracker_field_lastModif.

{img fileId="1512" thumb="box"}

__If I disable the search on this field (uncheck the search checkbox), delete cookies, rebuild index, refresh and login again the error is gone.
__

Logged as user xavi here on dev.tw.o/tracker5 I can't filter by summary (text field): no text input field is shown. Some other type of filter fields work as expected (I didn't try all) but not filter by summary.
Reported April 2nd. Using Firefox 2.0.0.13 ca on GNU/Linux
---
Reproduced as user xavidp (admin rights) using 2.x here again on dev.tw.o/tracker5 using Firefox 3.0 ca on GNU/Linux.

I tried to filter a search (Elastic search) at info.tiki.org and at themes.tiki.org. In both cases I input the search term and got results and then selected Object Type ("wiki page") and Federated search ("local search") to only get results from the site I was at, and only wiki pages. But nothing changed -- the same results were listed, including forum posts and tracker items at other sites.

Using Firefox, clicking the "Filter" button had no effect at all. In MS Edge, the page refreshed but the same search results were shown as before -- no filtering happened.

Is this a know problem, or is there a method for the user to get this to work?

Filter (stored query) feature

At https://tiki.org/forum26 I see 2 search forms.
One at the top (look to me like the website general search)
One inside the forums "boundaries", above the forum title.

When I use the second Search form I redirected to the Tiki search page which doesn't allow me to search by forums, author, etc.
Basic tools a forum should have.

It should be possible to have dedicated tools (or at least how they look like) to search with Forums object fields.
We have everything needed in the unified index
parent_object_type
parent_object_id
lastpost_modification_date
object_typecontents
post_author
score
Etc...

{syntax type="tiki" editor="plain"}
While setting up Tiki 6.0 (upgrading from an earlier version) I found that if you enable Full Text Search but not Tiki search, search is treated as a disabled feature on the admin pages.

Also the top search bar works only for tiki search, while the main search function does work with FT.

CLIP from my whining about why the search doesn’t work in TW.



#1 - why isn’t there a proper SEARCH ?

- to start this off can we at least agree on a couple things:
o standard search for - RED BALL would search on RED AND BALL
o TW does RED OR BALL – which is WRONG!!

- BASIC search should be capable of:
o RED BALL = RED AND BALL
o “red ball” = only match “red ball” as quoted
o and then, maybe RED or BALL = RED OR BALL


with a little more digging and some input from marclaporte, redflow and mose I think I have figured out the problem:

- TW supports the concept of FULL TEXT SEARCH (FT)
- this allows user to (from example above) do a search like “+red +ball” to achieve “red AND ball”.
- but these is a bug in concept in searchlib - function _find()
- if FT is set then _FIND does the right thing by doing a MATCH AGAINST sql query
- HOWEVER – if it doesn’t find any results it ALSO will do a simple (i.e. non-FT) search
o in concept this is silly since it defeats whole point of doing FT in the first place
o also, it generates an sql error because for simple search a REGEXP query is done which will choke on the + signs in the search string

The full text search module should provide means to determine what operators work with it. Perhaps a large tooltip or a link to an "advanced search" page. Syntax for the module is [http://tikiwiki.org/tiki-index.php?page=FullTextSearch|here.]

Using the new search box with the search button leads to a fatal error:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 53215256 bytes) in /home/alphafiv/public_html/lib/tikilib.php on line 5118

Using the Titles button works fine.

{syntax type="tiki" editor="plain"}
I have a search module set as:

advanced_search_option=y
advanced_search_help=y
default_button=go
input_size=25
select_size=20
nobox=y
decorations=n
style=position:absolute;top:0px;left:0px;

The "default_button=go" setting is not being honored. Clicking on any of the buttons works properly. Pressing Enter in the control causes a full-text search instead of a title search.

http://tikiwiki.org/tiki-index.php?page=20040302MarcLaporteInterview&highlight=marc%20laporte

Doing a search should display the result page with highlighted terms.
It partially not working (depending on the engine used).

As improvement, it would be nice that the results links contain also a parameter in the url (ie: result1?highlight=searchedword).

Highlighter code is still in Tiki but is not working anymore when used on pages. It seems to work partially on searchresults pages (mysql or elasticsearch diff).

(info rescued from the nextdev.t.o updated tracker item ;-) {sign user="xavi" datetime="2016-02-25T09:34:07+00:00"} )

Something more than this:
http://irc.tikiwiki.org/

There is a start but can it handle the volume of data we produce?
http://tikiwiki.org/tiki-view_irc.php

The level of integration (all, some or none) with Tiki is to be discussed.

Related/similar software:
http://colas.nahaboo.net/software/irclogger/
http://ircbrowse.com/
http://tools.splitbrain.org/irc/wikiohana/

An RSS feed would be nice.


And some stats:
http://pisg.sourceforge.net/

When I turn on tablesorter, the "Find" form on tiki-listpages.php all disappears except for the "Find" button itself. When I turn off tablesorter, the normal, complete "Find" form displays. This is in trunk on my localhost WAMP server. I'll try a show instance to see if I can reproduce it.

On creation of revision 66 of http://dev.tiki.org/Update, I got:
{img fileId="657"}

{CODE(caption="Error(s)")}Indexing failed while processing "Update" (type wiki page) with the error "RemoteTransportException[[search3][inet[/76.74.203.89:9300]][indices/mapping/put]]; nested: MergeMappingException[Merge failed with failures {[mapper [comment_count] of different type, current_type [long], merged_type [string], mapper [contributors] has different index values, mapper [contributors] has different tokenize values, mapper [contributors] has different index_analyzer, mapper [object_id] has different index values, mapper [object_id] has different tokenize values, mapper [object_id] has different index_analyzer, mapper [url] has different index values, mapper [url] has different tokenize values, mapper [url] has different index_analyzer, mapper [object_type] has different index values, mapper [object_type] has different tokenize values, mapper [object_type] has different index_analyzer, mapper [view_permission] has different index values, mapper [view_permission] has different tokenize values, mapper [view_permission] has different index_analyzer, mapper [title_initial] has different index values, mapper [title_initial] has different tokenize values, mapper [title_initial] has different index_analyzer, mapper [relations] has different index values, mapper [relations] has different tokenize values, mapper [relations] has different index_analyzer, mapper [deep_categories] of different type, current_type [long], merged_type [string], mapper [relation_types] has different index values, mapper [relation_types] has different tokenize values, mapper [relation_types] has different index_analyzer, mapper [categories] has different index values, mapper [categories] has different tokenize values, mapper [categories] has different index_analyzer, mapper [language] has different index values, mapper [language] has different tokenize values, mapper [language] has different index_analyzer, mapper [geo_located] has different index values, mapper [geo_located] has different tokenize values, mapper [geo_located] has different index_analyzer, mapper [allowed_groups] has different index values, mapper [allowed_groups] has different tokenize values, mapper [allowed_groups] has different index_analyzer]}]; "{CODE}

We get {CODE()}Indexing failed while processing “5578” (type comment) with the error “analyzer [sortable] not found for field [sort]”{CODE} on this site.

Hmm, temporary issue? Seems gone after couple of seconds I filled this bug report.

Ah, nope, just replaced by "all shards failed" error while saving this bug report now.

Right now, if you have a multitiki installation with 10 sites, and you want to rebuild the unified search index for them all, you have to run 10 times the command with the "--site=" para adapted to each case.

However, when you run setup.sh, by default setup.sh runs for all sites in a multitiki installation.

It would be nice if console.php had the chance (by default or not) to be run once for all sites in that multitiki installation at once


with some param like "--site=all":
{CODE(colors="shell")}
php console.php d:u --site=all
{CODE}