Category: 19.x

When a user is registering on a tiki, within the default template, if there is an error, it is no longer obvious that there is an error. The errors use to be highlighted, but now they are black text that looks like field descriptions.

They are case you want your user to create a tracker item at creation but want them to fill supplemental information later.

When setting tracker to store user information (Log-In, https://doc.tiki.org/User-Tracker) if in the Group setting you don’t assign anything for "Group or User Tracker Registration Fields" (if you don’t need to fill anything more but to save an item with the username) the tracker item is not created.

To reproduce the bug;
Set everything like described at : https://doc.tiki.org/User-Tracker

On the Group page for the registered group let "Group or User Tracker Registration Fields" empty. The registration will work but no item will be created.

Add any field of the user tracker in the "Group or User Tracker Registration Fields" and it will work.

I switch a Tiki18 to a Tiki19.

During the install on the database step, I had a warning about "UTF-8 encoding" while my tables were properly upgraded to utf8mb4_unicode_ci.

Following the links to the doc doesn’t really help
{img fileId="1240" thumb="box"}
---
On a second attempt (local) I didn’t upgrade previously the table and applied the database upgrade. After upgrading the database I checked my database (phpmyadmin) most of the tables were utf8mb4_unicode_ci while a few (see the list below) were still UTF-8 unicode;
tiki_acct_journal
tiki_acct_stack
tiki_banning

The database upgrade process ended successfully but with error report:
{CODE()}
Upgrade operations executed successfully: 668 SQL queries.

Operations failed: 6 SQL queries. Display details.

During an upgrade, it is normal to have SQL failures resulting with Table already exists messages.
ALTER TABLE `sessions` convert to character set DEFAULT COLLATE DEFAULT Table 'tsaharoniki_tiki19.sessions' doesn't exist ALTER TABLE `tiki_banning` convert to character set DEFAULT COLLATE DEFAULT Invalid default value for 'date_to' ALTER TABLE `tiki_acct_journal` convert to character set DEFAULT COLLATE DEFAULT Invalid default value for 'journalDate' ALTER TABLE `tiki_acct_stack` convert to character set DEFAULT COLLATE DEFAULT Invalid default value for 'stackDate' ALTER TABLE `tiki_banning` CHANGE `message` `message` text COLLATE utf8mb4_unicode_ci Invalid default value for 'date_to' ALTER TABLE `sessions` CHANGE `data` `data` text COLLATE utf8mb4_unicode_ci NOT NULL Table 'tsaharoniki_tiki19.sessions' doesn't exist

If you think that the errors of a patch can be ignored, please check the checkbox associated to it before clicking on continue.
{CODE}

I refreshed and they were no more errors.

I'm trying to customize my Tiki instance. On the Look & Feel (tiki-admin.php?page=look) page, in the second tab (General Layout), I want to change the default logo. The only way (I saw) to do so is to specify 'manually' an image path from the img/ folder. I captured the screen, you can have a look ((https://ibb.co/izZ0X7|here)).
UX speaking, it would be better for the user to import an external image (logo) in the img/ folder and select it as a logo easily, through an Image Importer.

Feature Validate users might have become broken, if confirmed by someone else.
This looks serious enough to me to be considered a blocker, if confirmed by someone else.
The user tracker we suggest to setup through profiles has the setting validateUsers: n
http://profiles.tiki.org/User_Trackers?highlight=validateUsers

However, a brand new tiki19 site I did setup in the last days, where I applied that profile, has some users on hold (not being able to login) because they didn't validate the confirmation email, which they never received.

I loged in as admin, went to admin users, and clicked at "confirm user email" for one of them,m and Tiki replied that validateUsers was not set (indeed). However, how come users can't log in the tiki site because they didn't validate their email?

FYI...
---
Update {sign user="xavi" datetime="2018-11-09T11:23:52+00:00"}
* I had to setup validateUsers: y, in order to be able to confirm user emails.
* However, emails were (apparently) not sent from Tiki. Confirmed through the tiki logs (tiki-syslog.php), with the preference to record email sending at the log set ("Control Panels > General > Log mail in Tiki logs").
* email sending from Tiki works, as tested through the feature in the control panel to send test emails (they are received normally)

luci added one line and I received the following:
{CODE()}
---------- Forwarded message ----------
From: <noreply
Date: Tuesday, November 6, 2018
Subject: wiki page "Major Features Missing In Tiki" changed by luciash d' being
To: marc



The page "Major Features Missing In Tiki" was changed by luciash d' being at 07 Nov 18 00:26 CET

You can view the page by following this link:
https://dev.tiki.org/Major-Features-Missing-In-Tiki

You can view a diff back to the previous version by following this link:
https://dev.tiki.org/tiki-pagehistory.php?page=Major%20Features%20Missing%20In%20Tiki&compare=1&oldver=&newver=1


***********************************************************
The changes in this version follow below, followed after by the current full page text.
***********************************************************


+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -Lines: 1 changed to +Lines: 1-72 @@
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ Many open source web applications have a large number of features available as add-ons. They need to be installed separately and there are often several add-ons for the same purpose.

+ Instead, the Tiki community uses an ((tw:all-in-one Model)). One of the consequences is that Tiki is the ((tw:FOSS Web Application with the most built-in features)).
+
+ Not only has this been true for a quite a while now, but Tiki also has a much faster than average release schedule, with 2 major releases per year.
+
+ * 2008-08: ((doc:Tiki2|What's new in Tiki 2.0))?
+ * 2009-05: ((doc:Tiki3|What's new in Tiki 3.0)) LTS?
+ * 2009-11: ((doc:Tiki4|What's new in Tiki 4.0))?
+ * 2010-06: ((doc:Tiki5|What's new in Tiki 5.0))?
+ * 2010-11: ((doc:Tiki6|What's new in Tiki 6.0)) LTS?
+ * 2011-06: ((doc:Tiki7|What's new in Tiki 7.0))?
+ * 2011-11: ((doc:Tiki8|What's new in Tiki 8.0))?
+ * 2012-06: ((doc:Tiki9|What's new in Tiki 9.0)) LTS?
+ * 2012-12: ((doc:Tiki10|What's new in Tiki 10.0))?
+ * 2013-07: ((doc:Tiki11|What's new in Tiki 11.0))?
+ * 2013-11: ((doc:Tiki12|What's new in Tiki 12.0)) LTS?
+ * 2014-08: ((doc:Tiki13|What's new in Tiki 13.0))?
+ * 2015-05: ((doc:Tiki14|What's new in Tiki 14.0))?
+ * 2016-04: ((doc:Tiki15|What's new in Tiki 15.0))?
+ * 2016-11: ((doc:Tiki16|What's new in Tiki 16.0))?
+ * 2017-07: ((doc:Tiki17|What's new in Tiki 17.0))?
+ * 2018-01: ((doc:Tiki18|What's new in Tiki 18.0))?
+ * 2018-10 (planned): ((doc:Tiki19|What's new in Tiki 19.0))?
+ * 2019-04 (planned): ((doc:Tiki20|What's new in Tiki 20.0))?
+ * 2019-10 (planned): ((doc:Tiki21|What's new in Tiki 21.0))?
+
+ Even with all the features, there are still ((All Feature Requests|several hundred feature requests)). But most of these are requests for enhancements to an existing feature. Once a feature is in the code base and is basically usable, it usually evolves naturally/organically. In each Tiki version, most features are refined at least a bit. Some like ((Webmail)) need a lot of work. But at least, it's a start.
+
+ But when a feature is totally absent, it takes a spark to make it happen and take it to the level where is starts evolving naturally/organically.
+
+ What does Tiki __not do__ yet? (please base your answers on latest code). You can also check out the list of ((tw:Use Cases)) for more ideas. See also: ((Interesting Features from other Web apps))
+
+
+ !! Major features totally missing
+ {wishes filtervalue="163" status="op"}
+ * --Desktop publishing as will be needed for the ((Online Publishing House))-- See ((doc:mPDF))
+ * ((Naive Bayes classifier))
+ * --Something like ((kfm)) or ((elFinder))-- Done in ((Tiki11))
+ * ((WikiTrust))
+ * ((Social Bookmarking))
+ * ((Link checker)) (internal and external)
+ * ((Animations))
+ * ((Repository Browser)) for ((Code Review))
+ * --Interface with ((Monitoring)) tools: Nagios, Zabbix- etc. Would also be part of ((TRIM)) and ((Check))-- Code for Nagios was adding. Documention: https://doc.tiki.org/Monitoring
+ * Online Store (out-of-the-box solution like PrestaShop)
+
+
+ * A well-defined API for building applications on top of, or integrating application into Tiki. __People often say this but without a specific example, it's difficult to follow-up upon. Current plugins structure is very efficient to interface with 3rd party services. Can you give 2-3 specific examples of applications or types of applications you have in mind? Thanks! --marclaporte__
+
+
+ !! Major features missing from main code base, but available with 3rd party mods or workarounds
+ * [http://tiki.org/LearningManagementSystemDev|Learning Management] features like Moodle (gradebook, class management, etc.) though Tiki does have some [http://edu.tiki.org/AulaWiki|3rd party mods] for this
+ * ((doc:E-democracy system)) (we have polls and such but it's not the same as a full-fledged voting/election system)
+ * Online Help (not d.tw.o)-dthacker / marclaporte: can you explain a little more?
+ * Event Management system : while most of this can be done by using the wiki, calendar and user trackers, it's too difficult for someone new to Tiki. Added to ((info:Use Cases))
+ * Have a calendar in the main code base. Either including ((doc:Mod extcalculator)), ((doc:Mod calculator)) or another...
+
+
+ !! Incomplete features
+ __Please ((Add to Wishlist)) instead__
+ * External Authentication
+ ** Interface with SiteMinder ([http://www.ca.com]) (similar to InterTiki, except yield to SiteMinder for authentication as an enterprise-wide intranet authenticator)
+ * Debian and Ubuntu ((tw:Packaging Team))
+ * VMware and Xen virtual appliances
+ * Trackbacks in ((blogs))
+
+ See also: ((Interesting Features from other Web apps))
+
+ -=Alias=-
+ * (alias(Major Features Missing In TikiWiki))
+ * (alias(Missing Features))




***********************************************************
The new page content follows below.
***********************************************************

Many open source web applications have a large number of features available as add-ons. They need to be installed separately and there are often several add-ons for the same purpose.

Instead, the Tiki community uses an ((tw:all-in-one Model)). One of the consequences is that Tiki is the ((tw:FOSS Web Application with the most built-in features)).

Not only has this been true for a quite a while now, but Tiki also has a much faster than average release schedule, with 2 major releases per year.

* 2008-08: ((doc:Tiki2|What's new in Tiki 2.0))?
* 2009-05: ((doc:Tiki3|What's new in Tiki 3.0)) LTS?
* 2009-11: ((doc:Tiki4|What's new in Tiki 4.0))?
* 2010-06: ((doc:Tiki5|What's new in Tiki 5.0))?
* 2010-11: ((doc:Tiki6|What's new in Tiki 6.0)) LTS?
* 2011-06: ((doc:Tiki7|What's new in Tiki 7.0))?
* 2011-11: ((doc:Tiki8|What's new in Tiki 8.0))?
* 2012-06: ((doc:Tiki9|What's new in Tiki 9.0)) LTS?
* 2012-12: ((doc:Tiki10|What's new in Tiki 10.0))?
* 2013-07: ((doc:Tiki11|What's new in Tiki 11.0))?
* 2013-11: ((doc:Tiki12|What's new in Tiki 12.0)) LTS?
* 2014-08: ((doc:Tiki13|What's new in Tiki 13.0))?
* 2015-05: ((doc:Tiki14|What's new in Tiki 14.0))?
* 2016-04: ((doc:Tiki15|What's new in Tiki 15.0))?
* 2016-11: ((doc:Tiki16|What's new in Tiki 16.0))?
* 2017-07: ((doc:Tiki17|What's new in Tiki 17.0))?
* 2018-01: ((doc:Tiki18|What's new in Tiki 18.0))?
* 2018-10 (planned): ((doc:Tiki19|What's new in Tiki 19.0))?
* 2019-04 (planned): ((doc:Tiki20|What's new in Tiki 20.0))?
* 2019-10 (planned): ((doc:Tiki21|What's new in Tiki 21.0))?

Even with all the features, there are still ((All Feature Requests|several hundred feature requests)). But most of these are requests for enhancements to an existing feature. Once a feature is in the code base and is basically usable, it usually evolves naturally/organically. In each Tiki version, most features are refined at least a bit. Some like ((Webmail)) need a lot of work. But at least, it's a start.

But when a feature is totally absent, it takes a spark to make it happen and take it to the level where is starts evolving naturally/organically.

What does Tiki __not do__ yet? (please base your answers on latest code). You can also check out the list of ((tw:Use Cases)) for more ideas. See also: ((Interesting Features from other Web apps))


!! Major features totally missing
{wishes filtervalue="163" status="op"}
* --Desktop publishing as will be needed for the ((Online Publishing House))-- See ((doc:mPDF))
* ((Naive Bayes classifier))
* --Something like ((kfm)) or ((elFinder))-- Done in ((Tiki11))
* ((WikiTrust))
* ((Social Bookmarking))
* ((Link checker)) (internal and external)
* ((Animations))
* ((Repository Browser)) for ((Code Review))
* --Interface with ((Monitoring)) tools: Nagios, Zabbix- etc. Would also be part of ((TRIM)) and ((Check))-- Code for Nagios was adding. Documention: https://doc.tiki.org/Monitoring
* Online Store (out-of-the-box solution like PrestaShop)


* A well-defined API for building applications on top of, or integrating application into Tiki. __People often say this but without a specific example, it's difficult to follow-up upon. Current plugins structure is very efficient to interface with 3rd party services. Can you give 2-3 specific examples of applications or types of applications you have in mind? Thanks! --marclaporte__


!! Major features missing from main code base, but available with 3rd party mods or workarounds
* [http://tiki.org/LearningManagementSystemDev|Learning Management] features like Moodle (gradebook, class management, etc.) though Tiki does have some [http://edu.tiki.org/AulaWiki|3rd party mods] for this
* ((doc:E-democracy system)) (we have polls and such but it's not the same as a full-fledged voting/election system)
* Online Help (not d.tw.o)-dthacker / marclaporte: can you explain a little more?
* Event Management system : while most of this can be done by using the wiki, calendar and user trackers, it's too difficult for someone new to Tiki. Added to ((info:Use Cases))
* Have a calendar in the main code base. Either including ((doc:Mod extcalculator)), ((doc:Mod calculator)) or another...


!! Incomplete features
__Please ((Add to Wishlist)) instead__
* External Authentication
** Interface with SiteMinder ([http://www.ca.com]) (similar to InterTiki, except yield to SiteMinder for authentication as an enterprise-wide intranet authenticator)
* Debian and Ubuntu ((tw:Packaging Team))
* VMware and Xen virtual appliances
* Trackbacks in ((blogs))

See also: ((Interesting Features from other Web apps))

-=Alias=-
* (alias(Major Features Missing In TikiWiki))
* (alias(Missing Features))
{CODE}

When you are in edit mode on a Wiki page, when you click on the Help icon in the toolbar of the Wiki page, and then click on the Plugin Help tab. If we choose to open a modal of a plugin and close it, right now, by trying to click on the Help icon, no modal will open.

On the other hand, when you close the modal of a Plugin by saving the changes, you can currently open the Help modal by clicking on the Help icon, but you can't open other modals unless you reload the page or save it.

The problem is that the modals do not open at least at some point to save or reload the page.
The image gives more details
{img fileId="1311"}
Thanks!

Since I upgraded some site to Tiki 18.x (svn), I can't edit properly wiki pages through the mobile phone (using Chrome on Android, in case it matters).

Once the page is open for edition, copy & pasting some url from elsewhere (for example) get your url appended with some extra text each time you click elsewhere in the same edit, or even if you just hit at the save button afterwards.

If you disable codemirror highlighter for the time being in that edition, then no extra text is prepended and you can save as expected.
---
Similar issue still present in 20.x{sign user="xavi" datetime="2019-07-06T17:58:57+00:00"}

Reproduced with an android based device (using chrome) in:
http://xavi-9794-6662.show2.tikiwiki.org/tiki-index.php?page=HomePage
visit with mobile device, enable codemirror highlighter, and attempt to edit the text.

The UI of the Wiki History needs some more love... See the screenshot:
{img fileId="1230" thumb="box"}

After ((rev:67935)):
{img fileId="1232" thumb="box"}

As of r68335:
# The language dropdown remains squeezed.
# When the Advanced/Simple button has focus, the text/background contrast is insufficient (in the theme on dev.tiki.org).
# --The "rows per page" text input field lacks Bootstrap classes it seems-- Should not be an issue as of r68348.

{syntax type="tiki" editor="plain"}
It would be great feature I think if you could quickly mention someone in the wiki pages and anywhere else using syntax like -+@johndoe+- and after page is saved it would make a link to their user info and send a notification to them that they were mentioned on the object.

It should also respect the "show realName" preference when enabled.

Requirements:
* Needs to check if the @ is at the beginning of line, or surrounded by whitespace to not catch regular e-mail addresses
* Needs to match only one @ followed immediately by the username (login name)
* Optionally it would be nice if it matched also mentions in common parenthesis like -+(@username)+- without need to surround them by space

See also ((Freeform Relationships)) with the idea of @@group

Concerncs the current SVN version of tiki.
If you create a link to another wiki page via ((OtherPage)) it will be linked to tiki-editpage.php?page=OtherPage, whereas it should be tiki-index.php?page=OtherPage

Many news sites and blogs use a large image above the article content (see stories at vox.com, dailybeast.com, mic.com, www.bucketlistly.blog, etc. for example), whereas Tiki is by default limited to a small image to the side of the content. It would be great to have an option in the editor to choose either big image above the content or smaller image to the side of the content. For articles this would be the topic image. For blog posts and other cases it would be the featured image.

Infinite scroll automatically loads more articles or posts as the user scrolls down the page, so it isn't necessary to click to retrieve the next article/post. This is a popular feature used at many news and other websites, and would be a nice enhancement for Tiki sites.

One possibility (maybe leading contender, though others could be evaluated) is https://infiniteajaxscroll.com. For open source projects this is available under the MIT license (so ok for Tiki). It's also listed at packagist.org (https://packagist.org/packages/webcreate/jquery-ias).

When a fixed-top navbar is used, the page needs top padding of the same height as the navbar to prevent the navbar from obscuring the page content. Also, when an in-page TOC is used, and a link is clicked to go down the page to the relevant heading, the heading will be positioned at the browser window top, and under the navbar, unless there is an offset (such as margin/padding on the target heading).

Currently there is default pagetop padding for layouts using fixed-top navbars, but there isn't a fix yet in the Tiki stylesheets for the TOC problem (the Tiki project sites have a custom CSS rule as a fix). However, the height of the padding may not be right for all sites because the navbar height can vary depending on navbar content, font size, and so on.

Being able to specify the navbar height would ensure having the right px value for the site. (If there is a JavaScript solution instead that could be automatic and solve the problem, that would also be an acceptable solution, as far as I know.)

Nothing displays when trying to view, for example, http://doc.tiki.org/tracker20 . The page was normal a few days ago. This problem seems to be restricted to doc.t.o.

This seemed to be working correctly on my previous version of Tiki Wiki (18.x). However, some of the primary WYSIWYG buttons are now unusable.
This same behaviour can be seen on the [https://demo.tiki.org/18x/tiki-editpage.php?page=HomePage|demo Site].

In WYSIWYG mode, the link buttons show the dialog, but does not 'insert' and the table builder button show s a dialog without any rows to insert.

The browser console error I'm getting when clicking the Table Builder button in WYSIWYG mode is as follows:
{CODE(theme="default")}
tiki-toolbars.js:92 Uncaught TypeError: Cannot read property 'indexOf' of undefined
at dialogSelectElement (tiki-toolbars.js:92)
at dialogTableOpen (tiki-toolbars.js:394)
at HTMLDivElement.open (eval at <anonymous> (tiki-toolbars.js:50), <anonymous>:1:25)
at $.(/tiki/anonymous function).(anonymous function)._trigger (http://localhost/tiki/vendor_bundled/vendor/components/jqueryui/jquery-ui.js:697:13)
at $.(/tiki/anonymous function).(anonymous function).open (http://localhost/tiki/vendor_bundled/vendor/components/jqueryui/jquery-ui.js:12215:8)
at $.(/tiki/anonymous function).(anonymous function).open (http://localhost/tiki/vendor_bundled/vendor/components/jqueryui/jquery-ui.js:144:25)
at HTMLDivElement.<anonymous> (jquery-ui.js:256)
at Function.each (jquery.js:354)
at jQuery.fn.init.each (jquery.js:189)
at jQuery.fn.init.$.fn.(/tiki/anonymous function) [as dialog] (http://localhost/tiki/vendor_bundled/vendor/components/jqueryui/jquery-ui.js:236:10)
{CODE}

Going to Admin Categories > Bug on dev.tiki.org returns alerts on top of the page:
{CODE()}
ErrorErrorError
Tracker list_items ran out of memory after 0 items.Malformed search query: Parsing search query failed: "org.elasticsearch.common.ParsingException: [_na] query malformed, must start with start_object"Notice: invalid variable value: $_GET["maxRecords"] = undefined
{CODE}

When the wrong URL is entered, such as when an admin page URL is miss-typed, instead of a normal 404 error, this is displayed: "No route found. Please see http://dev.tiki.org/URL+Rewriting+Revamp". Many people who see this will have no idea what it means or what to do with it. Can this be replaced with something more user friendly, like "Error: no page found. Please check the spelling of the URL."? Can it be done within the Tiki interface and not be an empty unformatted page with that one line of geeky text?

Empty date tracker-field shows data through Mathematical calculation tracker field


An item from our intranet (item65 ) has no value at a date field (trkDeliveryDate). trkDeliveryDate is a date field (date picker) with only date, and no default value set in this preference.

Field trkDeliveryMonth is a Mathematical calculation tracker field, extracting the month from that date field, which should be empty, but it's not, it shows some month (current month, I don't know if by chance or by which means).

trkDeliveryMonth:
{CODE()}
(date (str y-m) trkDeliveryDate)
{CODE}

I get an annoying "Error" AJAX: error 0 (rejected) for URL: tiki-search-lookup?... on top of pages when requesting some query/navigating away from the page before it finished loading.

Is this necessary to show when I do not care if something did not finished loading yet and I simply want to take another action than waiting till the page finishes loading ajax in the background?

In 18.x (and probably earlier) you can print the table of contents on the fly in the pdf produced by mpdf (at pdf generation time), regardless of using hardcoded maketoc calls, o hardcoded title calls with wiki argument variable -+{ { page } }+- (no space intended between angle brackets).

^ Preference: Control Panels > Print > mPDF > __Table of contents__ ^

This feature is nice, but if would deserve another minor level of integration, for those cases in which:
# the Wiki page title is hidden by default, and placed by hand in the wiki page where needed (or replaced by human-(more-)readable text), usually at the top with a heading 1 level style.
** current behavior: mpdf places the table of contents at the top, and page title is shown below the table of contents, which is counter intuitive
# A wiki page has the AutoTOC setting disabled at wiki page level, and a hardcoded call to __~np~{maketoc}~/np~__ is placed below the page title (or wherever, with whichever maketoc params for the users like, such as levels="2,3", my favourite, btw).
** current behavior: mpdf keeps the table of contents produced by itself, plus the table of contents that was previously generated in the rendered html page by the wiki markup). therefore, 2 table of contents are shown, which is not what most users would expect.

Potential solution to both issues: (2 birdies in one shot)
__Allow replacing hardcoded call to maketoc in page with the one produced by mpdf__

How? Brainstorm mode on:
* add a new param -+inpdf+- in maketoc plugin, with several values:
** __replace__: -+~np~{maketoc inpdf=replace}~/np~+- Replace that maketoc call in the wiki textarea with the output of the table of contents from mpdf
** __keep__: -+~np~{maketoc inpdf=keep}~/np~+- keep same behavior as nowadays, for those edge cases in which user has custom maketoc for partial sections of the page (or whatever), which want printed also besides the full table of contents at the beginning, etc.
** __ignore__: -+~np~{maketoc inpdf=ignore}~/np~+- ignore the maketoc call when creating the pdf, so that the only maketoc is the one produced by mpdf at the beginning (for cases with wiki page created by Tiki itself, etc, so that placement of the maketoc from mpdf is the expected one, etc)

Opinions?

Attachments are not working.