Category: Search

To reproduce.

As your Unified Index:
* Use Elasticsearch for a few days
* Switch to MySQL

Your setting will stay say that date of last re-index is the one from Elastic

* a file gallery with images
* a wiki page
* both no categories and no object permissions applied
* a LIST plugin on a wikipage filter the gallery, show a slideshow

A Tiki15.1 and a Tiki(pre16)Trunk - both last week upgraded
On both sites the images from the gallery are super positively visible in all cases on wikipages or directly ex: example.com/display7

Permissions:

Tiki 15 => restricted permissions for Registered, minimal permissions for Anonymous
LIST on a wikipage show the slideshow

Tiki(pre16)Trunk => several setps from same as above until grant ALL permissions to Anonymous
=> in only one single case the slideshow is visible for Anonymous:
==> when Anonymous positively has applied tiki_p_admin
Even if all other permissions are granted and tiki_p_admin is not, Anonymous will not see the slideshow, despite the Registered user or group member can indeed have limited access and still see the LIST and things can be worked out with category perms.

Just Anonymous needs tiki_p_admin to be able to view the LIST result/output (at least with template=carousel).

On a Tiki25 I have tracker items created yesterday and today.


If I set a plugin List and filter using "day" argument to filter a date range it is working as expected for the "modification_date" but not for the "creation_date".

IE: These are the dates outputted by tiki-pluginlist_experiment.php
modification_date => "2023-02-28 06:01:22"
creation_date => "2023-02-27 14:05:01"

If I use
{filter range="modification_date" from="-2 day" to="-1 day"} ~~#090:it will output the items~~

If I use
{filter range="creation_date" from="-2 day" to="-1 day"} ~~#F00:0 results~~
(I also tried from="-3 day" to be sure it was not a timezone issue) ;-)

Both should work the same.

1- Visit http://dev.tiki.org/item4677?status=op&sort_mode=f_41_desc&filterfield=26&filtervalue%5B26%5D=redact&filter=Go

and see:
{img fileId="513"}

Search index rebuild fails. I've tracked it down to the file and it fails at php:s function rename. Where the code tries to rename the index-new folders content to the current index. This used to work in version 11. Possible issue with file-permission systems, php is not allowed to access the folders. The file in question is searchlib-unified.php and rows close to 250. rename($index_location, $swapName)) this fails.
I'm not sure if this is a problem on Linux servers.

Settings:
Windows server 2008 R2 Standard
MySQL server 5.6
PHP 5.4.19

Workarounds:
1: Comment out the rename and delete lines from code.
2:
Build a batch file to do your file transfer.
OR
Move the files manually if you don't have to build indexes very often
OR
build indexes with previous versions and move the files
OR
Fix the code by making a recursive loop that moves the files from the folder to another folder.

{syntax type="tiki" editor="plain"}
Comments to tracker items can be very a useful way to gather ideas, code snippets, links, etc. from the community regarding an a problem or an idea.

It would therefore seem to be natural to include tracker comments in search - otherwise there is a risk of losing valuable community contributions in a black hole of tracker comments.

Tracker comments should of course be included in "Entire Site", and maybe even have their own search category.

{syntax type="tiki" editor="plain"}
Full thread is here:
http://tiki.org/forumthread47305

"So should we have a new pref "unified_index" and add it as dependency for these features (PluginList, PluginListExecute, etc.), and thus people whose servers don't work with it have the option to turn them off? (effectively acting like a Tiki6)"

There are issues at: ((Unified Index with MySQL Full Text Search))

Also, there should be warnings when site hits limitations of MySQL, that the admin needs to change to Zend_Lucene or ElasticSearch. Ideally, these warnings would come before hitting the limitations but this may not be easy to do.

Nelson (note to self): To make this bug actionable: these are the following actions. Many other things like excluding plugins by default are already done.

1) Make the logging use a different log file when triggered from the console vs the web (this will avoid any file perm problem).

2) Provide remarks box about including plugins in the admin panel.

3) Provide remarks box explaining that MySQL Full text search will only search first x characters of content (might affect large files in the file gallery for e.g.) - this is handled in item4641 already

http://dev.tiki.org/tiki-searchindex.php?find=maketoc


{flash type="url" movie="display522" width="846" height="711"}

In an updated Tiki25 using ElasticSearch I have a customSearch that displays orders.
When I receive a payment I use a button to create a payment item (in a different tracker) and set a relation between the 2 items (order <-> payment).

On Tiki25 the operation is completed and the initial item (the order item) is at the same place in my customSearch results.

---

On the same Tiki (same database and same server) using Tiki26 and Manticore I have a different behavior.

After saving the payment item and going back to the results page the initial order item it is related to is gone.😳
I refreshed the index but still couldn't find it.

In the trackers payments and orders I can see the items exist so the operation was completed.
However the placement of the item I just related another item to has been changed in the customSearch results.

This item (order item) has been moved to the end of the results list after I related to this item another item from a different tracker.

It shouldn't, I have a sort filter here based on order item date `{sort mode="tracker_field_productsboughtDate_ndesc"}`.

{mediaplayer src="display2103"}

On a Tiki 26 I have a plugin List that displays results using a smarty template where I have another wikiplugin list embedded.
This plugin has a filter to match a date with a fields that have a list of dates (2023-07-23, 2023-07-24, ...) using "multivalue".

With ElasticSearch (the originaly used search engine) the results are displayed, no error.

With MySQL full-text Search (used to test only) the results are displayed, no error.

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

With Manticore Search the results are displayed after a long error that start with:
"Fatal error rendering template file /home/tsaharoniki26/public_html/themes/templates/holidays_camps_childrenList_inner_days.tpl
TypeError: strpos(): Argument #1 ($haystack) must be of type string, array given in /home/tsaharoniki26/public_html/lib/core/Search/MySql/FieldQueryBuilder.php:24
Stack trace:"


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

I tried to point a finger on something and change/simplify the plugins that displays such results.
In the last wikiplugin list I this filter.
`{filter field="tracker_field_productsboughtHolidays_text" multivalue="{/literal}{$row.tracker_field_holidaycampsDayDay}{literal}"}`

It's the only "multivalue" filter I have for this page.
If I change "multivalue" for "content" or "exact" no error is displayed.

On a Tiki26 using Manticore I have a tracker where the items don't have a value for a field.
In my case the tracker has been emptied to prepare a new season in a business.

On a Wiki page I have a plugin that uses this field as filter:

{CODE()}{filter content="No" field="tracker_field_covidHealthDeclarationApproval"}{CODE}

As there is no item yet, the page displays "Class "Search\Manticore\TikiFilter" not found".
{img fileId="2086" thumb="box"}

This not very good to be displayed.

But the thing is that this problem will also break the index:rebuild action as soon as it hit the page.
This leaves the index partially created.

{CODE()}
xxx@bsfez:~/public_html$ php8.1 console.php i:r -p --log
[16-07-2023 13:44] Started rebuilding index...
Logging to file(s):

* /home/xxx/public_html/temp/Search_Indexer_manticore_tiki26_console.log

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

Engine: Manticore, version 6.0.4 1a3a4ea82@230314 (columnar 2.0.4 5a49bd7@230306) (secondary 2.0.4 5a49bd7@230306)
3 mins/3 mins [==========================>-] -- Processing wiki page documentsA error was encountered while running a command
Class "Search\Manticore\TikiFilter" not found on line 635 of /home/xxx/public_html/lib/core/Search/Manticore/Index.php
{CODE}

-=To help in the diagnostic and what was going on in the same case with previous version=-
I don't recall any issue with such "empty" field in Tiki21 and Tiki24. (no results for the query, I think)
In Tiki25 it was ok also until a few weeks from now where, in such case, an error started to be displayed. (The page is visible and the index:rebuild can complete).

This is the error displayed (re tested today after updating the Tiki25 version of the same site)
{img fileId="2087" thumb="box"}

memory exhausted (even if 1Gb allocated to php processes!) after uploading big pdf (20Mb with images) to file gallery and tiki works server side with pdftotext and others.

Untested in other versions of Tiki.
It might very well be a problem with pdftotext, because the file uploads to the server fine, and the server processes the file with pdftotext after that, before showing the error message. Apache error log says memory exhausted.

After upgrading 1.9.4 to 1.9.5, a search entire site returns the following error. I looked in db/fulltext.sql and didn't see a create fulltext index statement for tracker. What tables/columns should be indexed?

~pp~
in /home/lampp/htdocs/kniki/lib/tikidblib.php on line 134

Context:
File /kniki/tiki-searchresults.php
Url ///kniki/tiki-searchresults.php?highlight=draw&where=pages&search=go
Query:
SELECT ttif.`itemId` AS name, LEFT(tt.`name`, 240) AS data, tt.`trackerId` AS hits,
tti.`lastModif` AS lastModif, tti.`itemId` AS pageName,tti.`itemId` AS id1,1 AS id2,
MATCH(`value`) AGAINST ('draw') AS relevance FROM `tiki_tracker_item_fields` ttif LEFT
JOIN `tiki_tracker_items` tti ON (ttif.`itemId`=tti.`itemId`) LEFT JOIN `tiki_trackers`
tt ON (tti.`trackerId`= tt.`trackerId`) LEFT JOIN `tiki_tracker_fields` ttf ON
(ttf.`fieldId`= ttif.`fieldId`) WHERE ttf.`isSearchable` = "y" AND MATCH(`value`)
AGAINST ('draw') ORDER BY relevance desc, tt.`trackerId`

Values:
Message:
Error Message Can't find FULLTEXT index matching the column list
~/pp~

When selecting unified search, the default Unified Search Engine: is "MySQL Fulltext search".

This is the default even if InnoDB < 5.6 is installad, i.e. MySQL Fulltext search is not supported.

When InnoDB and the MySQL version < 5.6, Lucene should be selected as a default and MySQL FT Search should not be an option.

{img fileId="644"}

Since MyISAM is always used (Ref LP's comment), this is a non-issue.

{syntax type="tiki" editor="plain"}
Error "Out of range value for column 'entryId' at row 1" appears whenever modifying almost any content.

I have documented the problem and a workaround here:
* [https://doc.tiki.org/Troubleshooting?page_ref_id=4835#Ancient_Tiki_triggering_error_Out_of_range_value_for_column_entryId_at_row_1_on_every_change_advanced_|https://doc.tiki.org/Troubleshooting]

Maybe we should add a way of doing this automatically whenever necessary (every 10 years or so?)

On Tiki23 at tiki-admin.php?page=articles I discovered a feature I didn’t knew exist (is it new and went under "my" radar ?)

I was about to think about an accordion to hide the BIG top search area that is eating the top part of the screen. ????

^
"Use new articles"
Use the new CustomSearch-based article lists rather than database information
^

The feature naming should be improved. ;-)

Look an awesome start but I found some issues
* Garbage in search field added depending on background color
* Author is not properly populated
* Article_content (?) return not found

See the screenshot
{img fileId="1572" thumb="box"}

May be it is a kind of work in progress ?
I see an interest for people to customise the template.
The path of the template OR some help to customise it mytheme/templates/articleCustomsearch should be added in the feature tooltip.

In the early days of TikiWiki, we used a bunch of modules (last_modified_wiki_pages, last_articles, Last this, Last that, etc.) to show recent changes to visitors. We ended up with many modules and it was cluttered.

All this became a lot better once the "Since your last visit" module came around to adding all the features. As a bonus, it checks permissions and shows the information since the user's last login. Very sweet.

Now, I am hoping to get to the same result for the many edit/input boxes.

In version 3.0, the quick_edit module checks (with Ajax) for names of existing wiki pages to edit. This avoids duplication. Great stuff. Wikipedia does something similar when you are searching for a page name.


I almost always have the search box on.

However, I also add "search page name" because the general search engine may not return the page I am looking for as the search result.

Here is an idea:

A new module which combines three modules:
search_wiki_page
search_new
quick_edit

See top right of http://moinmo.in/ for an example.

The action buttons are grayed out until text is entered in the text box. -> Very nice


Button should be WYSIWYCA


See top-right search box at:
http://www.ohloh.net/projects/tikiwiki
http://www.wikicreole.org/



__Alternatively, we could combine search page name and search text, and in the search results, we would first show pages names, and then, search text. This involves more work, but could be better for the end user UI.__

^I think the existing layout for the search top right in TW is fundamentally good. A text box, then a drop-down then a button. Why because the drop down is more future proof than any of the layouts from the other sites you reference.

If we make the contents of the drop down easy to customise or at the very least document how to add to it. For example the CRM function could add items to the drop down for "Contacts" and "Accounts", webmail could add "Mail Messages" and so on.

I do agree the wikipage create/edit module should be included in the top right search function.

I think this is an example of where considering the future openness of the solution would be very important - MatWho^

{THUMB(id=98)}{THUMB}

Sometimes, I want to restrict who uses Tiki's internal search engine. Maybe I have some non-linked pages, that people can discover via the search engine.

TEsting plugin list and plugin pivottable in trunk at nextdev.t.o, I 've just seen these errors in pages that were using plugin list, or plugin pivottable, such as:
* https://nextdev.tiki.org/Tiki16
or
* https://nextdev.tiki.org/Tiki18

{QUOTE()}
Error: Malformed search query: Parsing search query failed: "Field tracker_id does not exist in the current index. If this is a tracker field, the proper syntax is tracker_field_tracker_id."

Error: Malformed search query: Parsing search query failed: "Field trackerId does not exist in the current index. If this is a tracker field, the proper syntax is tracker_field_trackerId."
{QUOTE}

Maybe it's just that the index is not run (or not finished successfully, or some related issue?)
Just in case, I drop this report.

1- Visit http://dev.tiki.org/tiki-listpages.php?find=canon&boolean=on&boolean_last=y&go=Titles

2- You will see No pages found with: "canon&dquot;.

When I type something into the Create/Edit-Search-box there pops up an ajax-autocomplete-box below the search field.

But when I use the regular search box, there is no autocomplete-search. It should also have autocomplete.

This would be a great feature with relatively low effort, because the feature is already implemented for the Create/Edit-Search-box.

#Create a MS word file.
#Enter any word in the file. (In my case, it was "outside")
#Create a table in the word file and enter a text into a cell of the table. (In my case, it was "inside", "insider", "Inside2")
#Save the Word file.
#Upload the file to File Gallery (12.x of demo.tiki.org)
#Rebuild the index and "Reindex all files for search" (Admin -> Admin Home -> file Gallery -> "Search Indexing" tab)
#Search for the words.
#Result
##Tiki found the word "outside" (which is outside of tables)
##Tiki could not find "inside" (and its variants, which are inside of tables)

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}

I am using Tiki for educational scenarios, and frequentñy I (or my students) want to change misspelled words (for instance) on long wiki pages.

Nowadays I'm taking the content out of the wiki-edit form, search and replace on in external program, anb back.
I could be nice to have this feature integrated into the edit page form.