Category: 17.x

On module creation :
( ! ) Fatal error: Class 'convertToTiki9' not found in /Users/Bernard/Documents/Shocksite/www/htdocs/retroRGB/lib/modules/modlib.php on line 76

The module is created.

__Setup:__ tiki 17.1 on Linux, nginx, mysql, php 5.6
I have standard text editor and default file gallery stuff..

Short story: I cannot put images into blog post via "Choose or upload images" button. The files are being downloaded instead of inserted into opened blog post.
It is something regarding __SEF URL__ feature.. when I enable it .. the bug is being triggered.. when I disable it it works as before.

The other strange thing is that I cannot edit already inserted images via double clicking.

__Steps to reproduce:__
1, open blog post
2, click "Choose or upload images" - three squares behind each other icon
3, Upload screen is opened in another window
4, click Browse Galleries
5, choose gallery and hover on the particular image
6, popup with thumbnail of image and caption "Download" shows
7, after clicking the image starts downloading via browser

This is the screenshot showing that it will download instead insert:
{img fileId="1143" thumb="box"}

This is the failed-to-construct edit image dialogue:
{img fileId="1144" thumb="box"}

__What I was doing:__
Enabling SEF URL..
Fiddling with some settings, not sure if related - user settings, permissions, batch directory, disabled image gallery etc.
I tried Batch directory in File Galleries, it worked via syncthing.. then I processed the files.. probably it caused the thing..
Moved files from database to directory.

__Show tiki instance:__
I was not able to demonstrate bug so far (I have SEF URL set)

Password for admin: 12345 .. test/test123 set/set123 if anybody is interested in playing with that.

Wiki Page properties "Show Page Title" Off

When choosing to turn off page titles on a per page basis by page properties and toggling Show Page Title to Off, this action has no effect on the wiki page title, the title still displays.

Using the following code in a Wiki Parsed module

{CODE(caption=>example module code)}
{if isset($objectCategoryIds) and in_array(42, $objectCategoryIds)}
In category
{/if}
{CODE}

should show the text "In Category" when the wiki page currently shown in the center column is in the category with id 42.
--This works only on pages without spaces in their names.-- Things seem to have changed. This works with pages that have spaces in their name, but not if the spaces are being replaced by dashes.

The above code should also work when on a wiki page with spaces in it's name.

Tiki smileys are so 90s... It look very bad.

:)
;)
(:santa:)
(:twisted:)

Really ?

--drsassafras begin--
This seems related to : https://dev.tiki.org/item6191 and https://dev.tiki.org/item6189

I looked into the issue not so long ago. Almost all browsers now support emoji. Desktop and mobile. If we enable the saving of emoji in our database, they will all show nicely, and will always be kept up to date with the OS/Browser.

A little emoji selector could be made for users who dont have a emoji keyboard set up, and the existing similes used here could be integrated.

Although, it might be easier to replace the emoticons with new ones in the mean time.
--drsassafras end--

Hi, I just want to get a fresh pre-17 trunk show instance to have a look wether and how the H5P integration proceeds and how to use.
{sign user="Torsten" datetime="2017-03-13T23:15:30+00:00"}

chosen lib prevents changing the sorted order display of fields from an items-list tracker field with the translation smarty system

Workaround: disable chosen lib temporarily, make your changes to the selection of fields to be displayed, and/or the sort order, save (and reindex if necessary), and you can enable chosen lib again later on.
At least this worked for me so far.

Reproduced in trunk and 16.x:

Inability to post a comment-Issue (due to highlighter)
Reproduced in trunk in:
* Login as admin in http://xavi-9794-3214.show.tikiwiki.org/tiki-view_tracker_item.php?itemId=5
u: admin
p: 12345

And in 16.x in:
http://xavi-9794-6132.show.tikiwiki.org/tiki-view_tracker_item.php?itemId=5
u: admin
p: 12345

It's currently also affecting https://dev.tiki.org bug tracker comments. {sign user="xavi" datetime="2016-10-14T10:17:35+00:00"}

When codemirror highlighter is on (desired behavior in some setups, and the one produced by the new profile "Bug_Tracker_15" by default) when you click at submit your comment, you get: "__content is empty__", so you need to disable the highlighting before you can safely submit your comment.

This feature works as expected in Tiki15.

Configuration Wizard, setting not applied (WYSIWYG) on the HomePage, the very first page Admin will land and will want to change.

Tested on new install of Tiki15.x, 16.x and trunk.

Step to reproduce:
Install Tiki : tiki-install.php.
At the end of the install go to Configuration Wizard to Select Editor type.
Enable WYSIWYG => save and continue.

The Wysiwyg editor screen show:

Compatible Wiki mode Use wiki syntax for saved pages.
This is the most compatible with Tiki functionality and the most stable editor mode.
Tools and functions in the editor toolbar will be limited.

Full WYSIWYG editor is displayed by default : enable
__So all is set and the wizard tells you that WYSIWYG will be used by default on the Wiki page.__

Exit the wizard, edit the HomePage.
It is not WYSIWYG but Wiki syntax. The HomePage is created by the install process and an extra step is missing in the wizard (it should change the HomePage editor to WYSIWYG).

When the Strasa theme is selected, the tiki edit structure page is unusable. The Page Alias box(es) background is the same color as the text within. Making the text invisible on the screen and thus impossible to edit / update / review.

To use Tiki as a real content management system where people can add or change wiki pages securely, it will be a feature, if they (compared to mediawiki or wikipedia) first can store changes or new wiki pages as a draft. A chief editor checks it before it will be published. If it is possible to add this feature, I promise there is no reason left to choose mediawiki as a software.

The process could be:
1. somebody changes content in a wiki page or adds a new wiki page. Chenges will not be visible to everybody but the admin and the chef editor.
2. admin and chief editor will be informed about changes automatically
3. admin or chief editor check the content
4. if admin or chief edito agree they will publish the changes
5. if admin or chief editor do not agree they will not publish it and contact the editopr.

I am creating a huge portal with tiki as an alternative to wikipedia. Unfortunately I found out too late that this feature is missing. I can imagine the usability of tiki will be increased tremendously if this feature will bne available.

See: https://tiki.org/forumthread51287
---
Addendum: Make a plugin in Tiki to display the basic d3.js-based charts already developed in the past (in through PluginChart or other means)

Related: https://dev.tiki.org/item6263 - Make PluginChart optionally reuse some other lib already in Tiki to make js-based charts (raphaeljs, chartjs, d3.js, etc)

See:
https://dev.tiki.org/Data+Visualization#d3.js

Basic d3.js-based charts already made in Tiki:
http://marclaporte-11197-5155.show.tikiwiki.org/
u: admin
p: 12345

I just rolled back to version 49 of https://dev.tiki.org/Semi-automatic+merging+period and the comment indicates

{CODE()}"fix [Rollback by Chealer9 to version 49]"{CODE}

__It should be marclaporte. not Chealer9__

And my previous rollback has disappeared. Perhaps the system has problems with multiple rollbacks?

Perhaps related to [item6397|Some wiki page history versions are getting lost on doc.tiki.org (Tiki 17.x) (data loss)]

A tracker is created using Date Only field, after the tracker is displayed in a wiki page with a user submitted date, the date format looks something like this.
-1167609600

A show instance will be created with a tracker to use to display date in a wiki page.
Thank you for inspecting this bug.

For example for [https://suite.tiki.org/tiki-pagehistory.php?page=Tiki%20Suite%20alternatives&compare=1&oldver=84&newver=85|this diff] change in the e-mail notification there is this empty HTML plugin shown instead of showing its content:

{CODE()}
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -Lines: 143-146 changed to +Lines: 143-150 @@
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
!!!! Freedombone
{HTML()}{HTML}
+
+ !!!! Cloudron
+ {HTML()}{HTML}
+

!! Services
{CODE}

display a single chart with plugin sheet fails (with mode simple=y or n)

Related to this other bug report:
https://dev.tiki.org/item6265 - "Page with many PluginSheet calls should respect their own uses of parameter 'simple=y/n' "

After bug6265 is fixed, you now display only the sheet which were displaying charts normally, but when shown in mode "simple=y" charts are not shown.

Well, in fact, chart is not shown even if simple=n.

How complicated is it to get the charts shown?
See:
* http://xavi-9794-6265.show.tikiwiki.org/tiki-index.php?page=Spreadsheet-demo-instructions#Show_Only_Charts
* http://xavi-9794-6265.show.tikiwiki.org/tiki-index.php?page=Spreadsheet-demo-instructions#Display_only_One_Chart
u: admin
p:12345

Thanks!

When nested more times, it stops working and breaks the whole page parsing.
This works:
{CODE()}{DIV(class="level1")}
{DIV(class="level2")}
{DIV(class="level3")}
{DIV(class="level4")}
{DIV(class="level5")}
{DIV(class="level6")}
{DIV(class="level7")}
Foo Bar
{DIV}
{DIV}
{DIV}
{DIV}
{DIV}
{DIV}
{DIV}{CODE}

This breaks:
{CODE()}{DIV(class="level1")}
{DIV(class="level2")}
{DIV(class="level3")}
{DIV(class="level4")}
{DIV(class="level5")}
{DIV(class="level6")}
{DIV(class="level7")}
{DIV(class="level8")}
Foo Bar
{DIV}
{DIV}
{DIV}
{DIV}
{DIV}
{DIV}
{DIV}
{DIV}{CODE}

See the SHOW instance.

__Expected behaviour:__
Parsing nested plugins should work flawlessly no matter how many levels are nested or be limited to e.g. 20 levels (ideally should be configurable) but should not break up to that max level; only if above the limit, it could show the unparsed syntax instead of breaking whole content rendering.

Any WYSIWYG edit to a WYSIWYG zone (defined using the WYSIWYG plugin) fails quietly if the call to the plugin follows an inclusion (made using the INCLUDE plugin). CKEditor goes away as expected and the contents of the zone are displayed, but instead of the new contents, the old content shows.

This bug exists in Tiki 12 and persists in trunk as of r64360.

If wiki page Parent includes page Child, the following WYSIWYG zone causes the wysiwygPlugin() function to be called at page load with its page parameter set to "Child" instead of "Parent" as should be the case. Which causes the AJAX calls to action_replace() from edits to have the wrong value for their page parameter, causing them to have no effect, and action_replace() to return simply "~np~[]~/np~".

wysiwygPlugin's parameter is wrong because wikiplugin_wysiwyg()'s $sourcepage variable has the wrong value, because it is wrongly set to $wikiplugin_included_page instead of $page. This is due to a parser context management issue.

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}

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)

On a Tiki 16.3 I did :
{CODE()}svn switch https://svn.code.sf.net/p/tikiwiki/code/branches/17.x .{CODE}

Then I did:

{CODE()}sh setup.sh{CODE}
Option c to update composer.

[ErrorException]
rename(/root/.composer/cache/composer-temp.phar,temp/composer.phar): No such file or directory

I retried, did another try on a different tiki after I deleted the folder "vendor" before switching. Same.

I deleted manually "composer.phar " and retried.

The error is gone but another came up:

- Installing matthiasmullie/minify (1.3.44): Loading from cache

[ErrorException]
file_put_contents(/var/www/virtual/xn--8dbcma7a7ale.com/bin/minifycss): failed to open stream: No such file or directory

In /var/www/virtual/xn--8dbcma7a7ale.com/bin/ I have wrong symlink:

lessc -> ../vendor/oyejorge/less.php/bin/lessc
minifycss -> ../vendor/matthiasmullie/minify/bin/minifycss
minifyjs -> ../vendor/matthiasmullie/minify/bin/minifyjs

I corrected minifycss and minifyjs to look into "../vendor_bundled/vendor/matthiasmullie/..."

Run setup.sh again and it complete the instal with 2 last warning:

- Applying patches for adodb/adodb-php
../installer/composer-patches/adodb-php__remove_references_to_adodb_extension.patch (Remove references to ADOdb Extension)
Could not apply patch! Skipping. The error was: Cannot apply patch ../installer/composer-patches/adodb-php__remove_references_to_adodb_extension.patch
../installer/composer-patches/adodb-php__remove-the-check-if-the-adodb-php_ext-is-enabled.patch (Remove the check for ADOdb Extension)
Could not apply patch! Skipping. The error was: Cannot apply patch ../installer/composer-patches/adodb-php__remove-the-check-if-the-adodb-php_ext-is-enabled.patch

- Installing jquery/jquery-sheet (3.1): Loading from cache
- Applying patches for jquery/jquery-sheet
../installer/composer-patches/jquery-sheet_fix-visibility-issues.patch (Fix visibility issues)
Could not apply patch! Skipping. The error was: Cannot apply patch ../installer/composer-patches/jquery-sheet_fix-visibility-issues.patch

I though it was done but no:

Fatal error: Uncaught exception 'Symfony\Component\DependencyInjection\Exception\InvalidArgumentException' with message 'You cannot set service "service_container".' in /var/www/virtual/xn--8dbcma7a7ale.com/vendor_bundled/vendor/symfony/dependency-injection/Container.php:170 Stack trace: #0 /var/www/virtual/xn--8dbcma7a7ale.com/temp/cache/container.php(33): Symfony\Component\DependencyInjection\Container->set('service_contain...', Object(TikiCachedContainer)) #1 /var/www/virtual/xn--8dbcma7a7ale.com/lib/init/initlib.php(84): TikiCachedContainer->__construct() #2 /var/www/virtual/xn--8dbcma7a7ale.com/lib/tikilib.php(59): TikiInit::getContainer() #3 /var/www/virtual/xn--8dbcma7a7ale.com/installer/tiki-installer.php(741): TikiLib::lib('smarty') #4 /var/www/virtual/xn--8dbcma7a7ale.com/tiki-install.php(96): include_once('/var/www/virtua...') #5 {main} thrown in /var/www/virtual/xn--8dbcma7a7ale.com/vendor_bundled/vendor/symfony/dependency-injection/Container.php on line 170

---

I check on tiki install side after entering credentials, same :

Fatal error: Uncaught exception 'Symfony\Component\DependencyInjection\Exception\InvalidArgumentException' with message 'You cannot set service "service_container".' in /var/www/virtual/xn--8dbcma7a7ale.com/vendor_bundled/vendor/symfony/dependency-injection/Container.php:170 Stack trace: #0 /var/www/virtual/xn--8dbcma7a7ale.com/temp/cache/container.php(33): Symfony\Component\DependencyInjection\Container->set('service_contain...', Object(TikiCachedContainer)) #1 /var/www/virtual/xn--8dbcma7a7ale.com/lib/init/initlib.php(84): TikiCachedContainer->__construct() #2 /var/www/virtual/xn--8dbcma7a7ale.com/lib/tikilib.php(59): TikiInit::getContainer() #3 /var/www/virtual/xn--8dbcma7a7ale.com/installer/tiki-installer.php(741): TikiLib::lib('smarty') #4 /var/www/virtual/xn--8dbcma7a7ale.com/tiki-install.php(96): include_once('/var/www/virtua...') #5 {main} thrown in /var/www/virtual/xn--8dbcma7a7ale.com/vendor_bundled/vendor/symfony/dependency-injection/Container.php on line 170

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}

Extra site logo (tiki logo) and sitetitle shown at the top left corner after upgrade to 16.2svn (a.navbar-brand)

Workaround?: hide it with custom css. See:
https://doc.tiki.org/Tiki16#Known_Issues

I presume that this is needed for the display of the site logo when in smartphones and tablets, etc. but it should only be shown in that case, not always, and not if the other site logo and site name (from the feature and the module logo) are shown already.

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.

The File Gallery Template feature is still in Tiki, and it seems nobody really knows what it was used for, if you will here is something I wrote a couple years ago on this, at https://tiki.org/forumthread59522
If this is supposed to work somewhere, it sure would be great to have it working if the intentions were to build upload templates from it.
Thanks for looking
John