Category: 15.x

It seems some internal code in tiki to use elastic search needs to be updated to work with ElasticSearch 5.x:

Installed a blank new tiki, changed unified search engine to ElasticSearch (using v5.0.2 in Ubuntu 16.04 with their elasticsearch repository to have updated packages), and I applied Collaborative_Community_12 profile. I saw these errors just above the instructions page:

{CODE()}
Error(s)

Indexing failed while processing "HomePage" (type wiki page) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Instructions" (type wiki page) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Community" (type wiki page) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Wiki Help" (type wiki page) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "1" (type forum) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "1" (type tracker) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "1" (type trackerfield) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "2" (type trackerfield) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "3" (type trackerfield) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "4" (type trackerfield) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "5" (type trackerfield) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "6" (type trackerfield) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "1" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "2" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "3" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "4" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "5" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "6" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "7" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "8" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Community Members HomePage" (type wiki page) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Anonymous" (type group) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Registered" (type group) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Editors" (type group) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "SubAdmins" (type group) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Admins" (type group) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
{CODE}

And when I reindex, I get these other error messages:
{CODE()}
Error

all shards failed
×
Error

Indexing failed while processing "Community" (type wiki page) with the error "no such index"
×
Error

Indexing failed while processing "1" (type forum) with the error "no such index"
×
Error

Indexing failed while processing "1" (type file gallery) with the error "no such index"
×
Error

Indexing failed while processing "1" (type trackeritem) with the error "no such index"
×
Error

Indexing failed while processing "1" (type tracker) with the error "no such index"
×
Error

Indexing failed while processing "1" (type trackerfield) with the error "no such index"
×
Error

Indexing failed while processing "admin" (type user) with the error "no such index"
×
Error

Indexing failed while processing "Admins" (type group) with the error "no such index"
Rebuild Index
Your index was last fully rebuilt on Wednesday November 30, 2016 09:55:03 UTC.
×
Indexed

wiki page: 5
forum post: 0
forum: 1
file: 0
file gallery: 3
trackeritem: 8
tracker: 1
trackerfield: 6
comment: 0
user: 1
group: 5
{CODE}

{syntax type="tiki" editor="plain"}
When I evaluated the software for my project, I was very happy when the documentation said that it was possible to create a workflow with categories, transitions and watches. But I realized that watching a category only triggered a mail notification when the transition was made in the tiki-admin_categories.php page. It was useless for me!! :-((

At : tiki-admin.php?page=textarea "Open external links in new window" is enable.

So all the following create a link that will open in a new-tab or new window;

{CODE()}[http://www.u2.com|U2]{CODE}
[http://www.u2.com|U2]

As well as:
{CODE()}[http://www.u2.com|u2|_blank]{CODE}
[http://www.u2.com|u2|_blank]

As well as:
{DIV(class="external_link")}[http://u2.com|{img type="src" src="https://dev.tiki.org/img/icons/large/mytiki.gif" height="32" width="32"}|_blank]{DIV}
{CODE()}{DIV(class="external_link")}[http://u2.com|{img type="src" src="https://dev.tiki.org/img/icons/large/mytiki.gif" height="32" width="32"}|_blank]{DIV}{CODE}

However if I use the last one in a template called by a trackerlist plugin, it is not working.
Trying to set the link within the img plugin doesn’t work neither.

Check instance.

{syntax type="tiki" editor="plain"}

[Edit, 2 April 2016, Torsten]
The bug seems to be fixed by rjsmelo r58016 - ( thx Nelson for emailing me).
Before I close, I want to do a more in-depth test later to night or so, but it really seems to work (did resend out a wikisyntax-wysiwyg html+ txt version newsletter, that previously caused false encoding when received and today it was sent and received smoothly and intact).

Before I describe in detail, I`ll setup a show instance.

When trying to Upload Translations using a Custom Translations file I got the following (tested on Mac and Windows).

Error
Invalid file type (expected file type: php)

Export Spreadsheet as csv with code to produce svg chart includes the svg output tags in the csv cell instead of the tiki syntax to generate the chart

Reproduced when attempting to export sheet4 in doc.t.o, which is part of the sample charts generated from the tiki spreadsheet feature:
https://doc.tiki.org/tiki-export_sheet.php?sheetId=4

When exported (as csv with comma, and utf8) the content is like:
{CODE(colors="htmlmixed")}
Chart Type,Example,Chart,Data,Month,Year
Vertical Bar,"=BARCHART(D2:D13),<div class="jSheetChart"><svg height="172" width="421" version="1.1" xmlns="http://www.w3.org/2000/svg"><desc>Created with Raphaël</desc><defs></defs><path d="M80,139L58,139L58,127L80,127Z" stroke="none" fill="#1751a7"></path><path d="M108,139L86,139L86,1,4,Jan,2001
Horizontal Bar,"=HBARCHART(D2:D13),<div class="jSheetChart"><svg height="148" width="421" version="1.1" xmlns="http://www.w3.org/2000/svg"><desc>Created with Raphaël</desc><defs></defs><path d="M53,27L53,20L95,20L95,27Z" stroke="none" fill="#1751a7"></path><path d="M53,36L53,29L116,29L116,,6,Feb,2002
Pie,"=LINECHART(D2:D8, F2:F6)",<div class="jSheetChart"><svg height="220" width="421" version="1.1" xmlns="http://www.w3.org/2000/svg"><desc>Created with Raphaël</desc><defs></defs><text fill="#000000" stroke="none" font="12px Arial, sans-serif" style="text-anchor: middle; font: 12px A,7.2,Mar,2003
Line,"=PIECHART(D2:D8, E2:E8)",<div class="jSheetChart"><svg height="144" width="421" version="1.1" xmlns="http://www.w3.org/2000/svg"><desc>Created with Raphaël</desc><defs></defs><path stroke-linejoin="round" stroke-width="1" style="stroke-width: 1; stroke-linejoin: round;" d="M210.5,7.5,Apr,2004
,,,8.2,May,2005
,,,9.1,Jun,2006
,,,14.1,Jul,2007
,,,16,Aug,2008
,,,17.9,Sep,2009
,,,22,Oct,2010
,,,30,Nov,2011
,,,32,Dec,2012
,,,,,
,,,,,
{CODE}

And in my honest opinion, it should be something like:
{CODE()}
Chart Type,Example,Chart,Data,Month,Year
Vertical Bar,"=BARCHART(D2:D13)",=BARCHART(D2:D13),4,Jan,2001
Horizontal Bar,"=HBARCHART(D2:D13)",=HBARCHART(D2:D13),6,Feb,2002
Line,"=LINECHART(D2:D8, F2:F6)",=LINECHART(D2:D8, F2:F6),7.2,Mar,2003
Pie,"=PIECHART(D2:D8, E2:E8)",=PIECHART(D2:D8, E2:E8),7.5,Apr,2004
,,,8.2,May,2005
,,,9.1,Jun,2006
,,,14.1,Jul,2007
,,,16,Aug,2008
,,,17.9,Sep,2009
,,,22,Oct,2010
,,,30,Nov,2011
,,,32,Dec,2012
,,,,,
,,,,,
{CODE}

When you have more than one calendar, and you have user watches enabled, the display of the icons to watch calendars is not shown. I tagged this as a dogfood a tiki.org site since this is an improvement needed for tiki users to get notified on Tiki fests, for instance. Currently, most powerusers don't know that they can monitor the tiki calendar.

In order to monitor calendars right now, you need to deselect all calendars, re-select just one, refresh, and then you will see the icon to watch / monitor /subscribe to the calendar. And you need to do that one by one.

Expected behavior: some way to see the list of all calendars with the icon to subscribe to each of them next to its name. Maybe through similar popup with the full list of calendars that you have the right to see and monitor, and then, you expose those icons/actions there?

Show.t.o instance:
http://xavi-9794-5877.show.tikiwiki.org
u: admin
p: 12345

There are 3+ calendars already, and when all are selected for display (default behavior), no icon to monitor them is shown:
http://xavi-9794-5877.show.tikiwiki.org/tiki-calendar.php

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

But when you select just one, you can see the icons to monitor it:
http://xavi-9794-5877.show.tikiwiki.org/tiki-calendar.php?calIds%5B%5D=3&todate=1459860043&refresh=Refresh

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

expose more validation methods for tracker fields: numeric range, for instance (or positive value, etc)

Example:
http://jqueryvalidation.org/range-method/

Plugin TrackerIf doesn't seem to accept nesting so far, and we need it to allow customization of the interface to edit data with Pretty Trackers.

*If field_1 is A
** if field_2 is not empty, display value of field_2
** if field_3 is not empty, display value of field_3
** if field_4 is not empty, display value of field_4
** ...
* if field_1 is B
** if field_10 is not empty, display value of field_10
** if field_11 is not empty, display value of field_11
** if field_12 is not empty, display value of field_12
** ...

{CODE(ln="1")}
{TRACKERIF(test="(f_1='A')", ignore='n')}
{TRACKERIF(test="(f_2 ='')", ignore='n')} {ELSE} {$f_2|output} {TRACKERIF}
{TRACKERIF(test="(f_3 ='')", ignore='n')} {ELSE} {$f_3|output} {TRACKERIF}
{TRACKERIF(test="(f_4 ='')", ignore='n')} {ELSE} {$f_4|output} {TRACKERIF}
{TRACKERIF}
{TRACKERIF(test="(f_1='B')", ignore='n')}
{TRACKERIF(test="(f_10 ='')", ignore='n')} {ELSE} {$f_10|output} {TRACKERIF}
{TRACKERIF(test="(f_11 ='')", ignore='n')} {ELSE} {$f_11|output} {TRACKERIF}
{TRACKERIF(test="(f_12 ='')", ignore='n')} {ELSE} {$f_12|output} {TRACKERIF}
{TRACKERIF}
{CODE}

When viewing a tracker on a wiki page, an extra word 'Label' is showing in Tiki 15x (12x this is not / never was a problem). Is there any way to hide this word? It seems to be something in the back-end.

Pic of how it was before in Tiki 12x:

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

Pic of how it looks now in Tiki 15x:
{img fileId="1112" thumb="box"}

Parameters:
- browser: Opera mini (& beta mini), with parameters (very important) -
1) single column view (Settings > Page Layout > Single column view)
2) extreme mode data savings (Settings > Data savings > Extreme mode)
3) no images (Settings > Data savings > Images > off)
(all versions of Opera mini to through latest, v.21 & v.22)


- Android 5 and 6

I understand that most people do not use Opera mini, particularly with these parameters (which strip out all formatting for fast loading under 2G/GPRS environments), and this is a minor annoyance that users an get used to, but submitting as maybe it's an easy fix (this does not occur in any other browsers, or Opera Mini if 'Extreme Mode' data savings is turned off).

Thanks,
Mike

I believe there may be a bug with the Fade plugin in Tiki 15 (15.4) as it worked in 12x.

It does not open when used on a wiki page, and that page is used as a template for EDITING a pretty tracker (it opens for editing in the modal dialog).
(it works, i.e. opens, when VIEWING a tracker item as a wiki page template).

This problem occurs with or without the 'Icon' selected.
The hyperlink is there (cursor changes) but the Fade does not open up.

Within that Fade I have text, links, a fancy table, etc.

thanks,
Mike

__Update:__
To reproduce:
#Go to http://mikeua-11714-6308.show.tikiwiki.org/tiki-view_tracker_item.php?itemId=117&from=farming2+Review
#Enter show:show
#Login as admin:12345
#Click "Edit" button
#Click "Planting" under the "status:"

When a page which calls the FADE plugin is printed via tiki-print.php, the call's body is not printed by default. To print the content in my Tiki 18 and 19 installs, once I am in tiki-print.php or tiki-print_article.php, I must cancel the automatic printing, click on the label, and then have the browser print. Having revealed from tiki-index.php does not suffice.

It is arguable how much of a bug this constitutes, but the fact the hidden content is quietly hidden when printing is in my opinion already a problem. I believe if the content is not printed, there should at least be a warning displayed, and ideally an offer to reveal hidden zones ("This page contains hidden zones. Should the content of these zones be printed?").

The current way to reveal the zones - to click in tiki-print.php - is very strange, since one would not expect tiki-print.php to be interactive.

There is some failure to get geolocation from searching an address either manually typing address through tracker field location ui or in the backend with params to get address from other tracker field.
No point selected for that address, even for simple cases that used to work in previous tiki versions.

When the TRACKERITEMFIELD plugin is called trying to access a tracker item which does not exist, a fatal error like the following occurs:
{CODE()}
Fatal error: Call to a member function getConfiguration() on boolean in C:\xampp\htdocs\tiki\18\lib\core\Tracker\Item.php on line 200
Call Stack
# Time Memory Function Location
1 0.2009 192464 {main}( ) ..\route.php:0
2 0.2617 4607672 include( 'C:\xampp\htdocs\tiki\18\tiki-index.php' ) ..\route.php:306
3 0.5479 18560680 Tiki_Render_Lazy->__toString( ) ..\route.php:645
4 0.5479 18560712 call_user_func:{C:\xampp\htdocs\tiki\18\lib\core\Tiki\Render\Lazy.php:22} ( object(Closure)[521] ) ..\Lazy.php:22
5 0.5479 18560752 WikiRenderer->{closure:C:\xampp\htdocs\tiki\18\lib\wiki\renderlib.php:346-356}( ) ..\Lazy.php:22
6 0.5480 18560984 WikiLib->get_parse( string(16), bool, ??? ) ..\renderlib.php:349
7 0.5484 18565728 WikiLibOutput->__construct( array(34), string(58), array(3), string(1) ) ..\wikilib.php:802
8 0.5484 18566056 ParserLib->parse_data( string(58), array(3) ) ..\wikilib.php:2155
9 0.5485 18568760 ParserLib->parse_first( string(58), array(2), array(2), ??? ) ..\parserlib.php:1667
10 0.5537 18774536 ParserLib->plugin_execute( string(16), string(0), array(3), long, bool, ??? ) ..\parserlib.php:439
11 0.5562 18785784 wikiplugin_trackeritemfield( string(0), array(3), long ) ..\parserlib.php:1031
12 0.5670 20145512 Tracker_Item->canView( ) ..\wikiplugin_trackeritemfield.php:193
13 0.5670 20145664 Tracker_Item->canSeeOwn( ) ..\Item.php:88
{CODE}

Objects which contain such calls cannot be viewed, and reindexing for search is also broken.

This happens since {commit id=37583} and persists in trunk r68584.

Fatal error: Uncaught exception 'Exception' with message 'language library not found. This may be due to a typo or caused by a recent update.' in /xxxxxxxxxxxxxx/lib/tikilib.php:80 Stack trace: #0 /xxxxxxxxxxxxxxxxxxxxxxxxx/installer/tiki-installer.php(765): TikiLib::lib('language') #1 /xxxxxxxxxxxxxxxxxxxxxxx/tiki-install.php(96): include_once('/xxx/...') #2 {main} thrown in /xxxxxxxxxxxx/lib/tikilib.php on line 80


as discussed on the dev list

fixed in57848 - thanks Jonny {sign user="eromneg" datetime="2016-03-11T08:27:00+00:00"}

when accessing rss feeds eg with:
tiki-wiki_rss.php?ver=5
or
tiki-blogs_rss.php?ver=5

a fatal error occurs as follows:
Fatal error: Uncaught exception 'Zend\Feed\Writer\Exception\InvalidArgumentException' with message 'Invalid DateTime object or UNIX Timestamp passed as parameter' in /XXXXXXX/vendor/zendframework/zend-feed/src/Writer/Entry.php:189 Stack trace: #0 / XXXXXXX /lib/rss/rsslib.php(281): Zend\Feed\Writer\Entry->setDateCreated('1457350549') #1 / XXXXXXX /tiki-wiki_rss.php(109): RSSLib->generate_feed('wiki', 'wiki', '', Array, 'tiki-index.php?...', 'previous', 'pageName', 'Tiki RSS feed f...', 'pageName', 'Latest wiki pag...', 'data', 'lastModif', 'user') #2 {main} thrown in / XXXXXXX /vendor/zendframework/zend-feed/src/Writer/Entry.php on line 189

Favorite is not working.
On my Tiki15x I got an error in red at the top of the page.
--On the instance I got nothing and it is nowhere to be found.--

There is no doc about the exact location where I should see my user favorite.

Feature to discuss wiki pages in forums sends a notification email (user watches) each time the use clicks at the button 'Start discussion' (even if the discussion and thread was already started by someone else previously)

Reproduced:

http://xavi-9794-6188.show.tikiwiki.org/tiki-index.php?page=HomePage
u: admin
p: 12345

u: user1
p: user1

Mail sending is logged in the syslogs
Login as user1 and click at access discussion of the homepage (link above bottom bar). Registered users (through group watches) will receive an email as if you started the thread. But thread was started already, and you didn't post anything else to trigger a new email sent.

I must be missing something... yes?

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.

The "Upload New Version" action item in file galleries is no longer reliable. Clicking it opens a file selection dialog, but if the wrench icon controlling the menu of action items is not clicked, the dialog disappears quietly, without reporting any error. This is not too misleading, since there is no false confirmation.

http://bsfez-11581-5668.show.tikiwiki.org/tiki-list_file_gallery.php?galleryId=1
Can't upload a new version....

The usability bug appears while updating the newer version of the file.
There is a field for a comment given to the newer version of the file being uploaded, however, what is being typed is not displayed:
{img fileId="1062" thumb="box"}
{img fileId="1061" thumb="box"}
If we then look, it displays what I typed as metadata (works properly here):
{img fileId="1062" thumb="box"}

I believe that the feature is unimportant and the bug it comes with confuses a non-technical user, the feature is to be fixed or got rid of

auto categorization does not work in drag an drop. This can be a huge problem for those who use category jail, as all files will become invisible.

This bug occurs when using multiple workspaces, where each have a perspective with a category Jail.

Consider each workspace to have a main file folder (that belongs to it`s main category, and is only acessed by a certain group when it enters the workspace).
If you upload a file with the normal way, it will acquire the category by the autocategoriation pref.
But if you use the drag and drop feature, it will have no category, and will become invisible to the users, even if is inside the main group folder (because it has no category, and the category jail pref is on)

Show instance: http://fvtorres-11800-5950.show.tikiwiki.org/
User: admin
Pass: 12345