Category: 19.x

The idea is a basic DB management panel from within the Admin.
Same stuff exist for Wordpress and they come very handy to perform maintenance task and even auto-maintenance task.

Should do:
*Green checklist (db exist, db version, host, path to backup folder, last backup, etc)
*Table list (name, number records, data usage, etc)
*Optimise/Repair (one by one, all)
*Backup DB (manual, auto, where [folder, email... maybe dropbox ?], duplicating ?)
*Restore DB (folder listing, delete old, same as original, different name [same user/pass])
*An option page (path to backup folder, etc)

I believe there is also some stuff we can add if we look for a wider "maintenance panel".
As we'll have a scheduling system, we can have automatic backup + optimise tables + optimise search index + flush caches, etc.

As long as we don't introduce danger (like get the system stuck waiting for a question) would be great for Tiki to perform better.
Wordpress has something very similar: http://wordpress.org/plugins/wp-dbmanager/screenshots/

{sign user="pascalstjean" datetime="2013-08-18T18:11:45+00:00"}
After brainstorming, it was also suggested that maybe packaging Adminer would be a potential way to accomplish this feature request

http://www.adminer.org/

dev.t.o 13.x: add some scrollbar at the top of wide tables in Bootstrapped themes, since they look as with less content for new users or unexperienced visitors

Example: see for instance
http://dev.tiki.org/tiki-tracker_view_history.php?itemId=5162

{img fileId="940" thumb="y" width="600" rel="box[g]"}

Column related to new content is not shown, and there is no clear indication that some more content is hidden in the right-hand side of that table.

New: A library has been found to solve this problem: [https://www.jqueryscript.net/other/Double-Scrollbar-For-Scrollable-Container-jQuery-DoubleScroll.html] . License is MIT.

For some reason, some edits to tracker items are lost in dev.t.o . I just noticed that.

I made (I thought I had made) an edit to this tracker item:
https://dev.tiki.org/item6668-Incorrect-integer-value-for-column-healed-at-row-1-when-adding-a-Tiki-Scheduler-task-in-mysql-strict-mode

Adding this extra content (below) to the "Description" field of the bug report:
{CODE()}
---
Tested again (using latest 18.x svn again), same failure, also with the task to do some list:execute action, which runs fine otherwise through the console.php command on a cronjob directly at the crontab level. {sign user="xavi" datetime="2018-09-10T08:05:06+00:00"}

I stop attempting to use Scheduler (Web interface) at all in my projects since I never managed to get it running, nor a simple task. Maybe it's not mysql 5.7 ready? {sign user="xavi" datetime="2018-09-10T08:05:06+00:00"}
{CODE}

After saving, I saw the new page reload, no reporting of succeful edit nor anything (no remarksbox at the top indicating that the edit was successful), and I saw no changes in the field "Description".

Tracker item history is shown as blank, also:
https://dev.tiki.org/tiki-tracker_view_history.php?itemId=6668

Several (all?) of my recent edits to ((Tiki18)) page here in dev.t.o send me (user "xavi") to the dev.t.o homepage . That's new, it didn't happen to me months ago (nior in earlier tiki versions).
Regression?
---
Update: reproduced similar issue in trunk (from yesterday) {sign user="xavi" datetime="2018-09-28T09:22:41+00:00"}

I attempted to upload a simple image to a doc.t.o page (it seems to be using 19.x and elfinder) and I got error message about CSRF
{QUOTE()}
Potential cross-site request forgery (CSRF) detected. Operation blocked. Reloading the page may help.
{QUOTE}

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

I had to disable elFinder to allow uploading images to doc.t.o.

Feel free to re-enable elFinder feature in doc.t.o anyone once it's confirmed to have been fixed.

(Seems dev also have issues, I couldn’t upload screenshot in the file galleries due to multiple timeout)

Doc is very slow and got very bad ranking on speed page test.

__Google: ranked 14/100, Time to Interactive 19.6 s__
https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fdoc.tiki.org

__GTmetrix (Vancouver, Canada): ranked E(58%), 5.6s to load__
https://gtmetrix.com/reports/doc.tiki.org/OJessE4M

__Pingdom (San Francisco, USA): ranked C(73), 4.99s to load__
https://tools.pingdom.com

---

Update 1/06/2021 on https://doc.tiki.org/ (worst)
https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fdoc.tiki.org
__Google: ranked 12/100, 15.8s to load__

__GTmetrix (Vancouver, Canada): ranked E(51%), 7.2s to load__

__Pingdom (San Francisco, USA): ranked C(73), 4.99s to load__

While trying to insert a file or image into a tiki page, the editor user interface will not load that image using "Browse Gallery" when that file is clicked on.
Please see show instance for 19.x and the same issue is present in tiki 20.x

To keep the whole (responsive) table in view in large displays, a CSS rule was added to break words (and other character strings like multi-digit numbers) anywhere in the string. This does help to narrow the table, but also makes content readability much worse in some cases. If a solution better than "word-break:break-all" can't be found, I would at least like it to be optional (a Look and Feel preference) so site admins who prefer better typography in scrolling tables can have that option.

not OK: https://nextdev.tiki.org/Staging-and-Approval

OK:
https://nextdev.tiki.org/Tiki17
https://nextdev.tiki.org/How-to-Submit-a-Merge-Request

What could be killing the page?
https://nextdev.tiki.org/tiki-editpage.php?page=Staging%20and%20Approval

New feature about duplicate alias;
[ENH] Display error in wiki pages with duplicates alias links

Page https://doc.tiki.org/Tracker+Synchronization show multiple errors.

×
Error
Alias Tracker Sync link already present in 트래커 동기화 page(s)
Alias TrackerSync link already present in 트래커 동기화 page(s)
Alias TrackerS15n link already present in 트래커 동기화 page(s)
Alias Tracker S15n link already present in 트래커 동기화 page(s)
Alias S15n link already present in 트래커 동기화 page(s)

Also on : https://doc.tiki.org/Dynamic%20items%20list

Also on : https://doc.tiki.org/Requirements#PHP
Alias Requirements and Setup link already present in Anforderungen, 요구 사항 page(s)
Alias Requirement link already present in Anforderungen, 요구 사항 page(s)

On Tiki19
Last update from SVN (19.0svn): Thursday September 27, 2018 12:59:03 IDT - REV 67702 (InnoDB)

I create a first tracker after enabling the feature.

It show the following error:
Field tracker_id does not exist in the current index. If this is a tracker field, the proper syntax is tracker_field_tracker_id.

It shouldn’t show and error.
Eventually an info about re-indexing but would be better to do the job (first tracker is likely to be done by a new guy).

I was doing some changes in the tiki.org look and feel => custom css field on one save I got this:

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

The field was emptied, I turned totally green and was ready to jump out of the window ! By change (as I had many unsaved work while using "save as minor") I had the content pasted in a text editor by security and could restore. (lost time)

Seems we have some preg backtrack limitation (http://php.net/manual/en/function.preg-last-error.php)

I could get over it by shorting (shorthand?) a background style, but one day someone else...

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

I've updated trunk in a server, and I got these error messages after upgrading the database with console.php command:

{CODE(ln="1" colors="shell")}
root@server:/var/www/tikitrunk# php console.php d:u --site=mysite.example.com
PHP Warning: The requested theme's CSS file could not be read. Falling back to default theme. in /var/www/tikitrunk/lib/setup/theme.php on line 100
PHP Stack trace:
PHP 1. {main}() /var/www/tikitrunk/console.php:0
PHP 2. require_once() /var/www/tikitrunk/console.php:59
PHP 3. require_once() /var/www/tikitrunk/tiki-setup.php:150
PHP 4. trigger_error() /var/www/tikitrunk/lib/setup/theme.php:100
Update completed.
Installed: 20111231_change_datetime_defaults_to_null_tiki
Installed: 20180609_change_log_column_type_tiki
Installed: 20180705_fix_calendaritem_tracker_attributes_tiki
Installed: 20180706_remove_menu_reports_tiki
Installed: 20180803_semaphore_value_tiki
Installed: 20180815_merge_topic_read_perm_tiki
Installed: 20180918_remove_poweredby_module_tiki
Installed: 20180923_convert_collation_to_utf8mb4_tiki
Queries executed successfully: 277
Error in unknown patch script
ALTER TABLE index_5a6715b9e9160 convert to character set DEFAULT COLLATE DEFAULT
Specified key was too long; max key length is 1000 bytes
Error in unknown patch script
ALTER TABLE index_pref_en convert to character set DEFAULT COLLATE DEFAULT
Specified key was too long; max key length is 1000 bytes
Error in unknown patch script
ALTER TABLE metrics_metric convert to character set DEFAULT COLLATE DEFAULT
Specified key was too long; max key length is 1000 bytes
Error in unknown patch script
ALTER TABLE metrics_tab convert to character set DEFAULT COLLATE DEFAULT
Specified key was too long; max key length is 1000 bytes
Error in unknown patch script
ALTER TABLE tiki_acct_journal convert to character set DEFAULT COLLATE DEFAULT
Invalid default value for 'journalDate'
Error in unknown patch script
ALTER TABLE tiki_acct_stack convert to character set DEFAULT COLLATE DEFAULT
Invalid default value for 'stackDate'
Error in unknown patch script
ALTER TABLE tiki_banning convert to character set DEFAULT COLLATE DEFAULT
Invalid default value for 'date_to'
Error in unknown patch script
ALTER TABLE tiki_comments convert to character set DEFAULT COLLATE DEFAULT
Specified key was too long; max key length is 1000 bytes
Error in unknown patch script
ALTER TABLE tiki_links convert to character set DEFAULT COLLATE DEFAULT
Specified key was too long; max key length is 1000 bytes
Error in unknown patch script
ALTER TABLE tiki_object_attributes convert to character set DEFAULT COLLATE DEFAULT
Specified key was too long; max key length is 1000 bytes
Error in unknown patch script
ALTER TABLE tiki_profile_symbols convert to character set DEFAULT COLLATE DEFAULT
Specified key was too long; max key length is 1000 bytes
Error in unknown patch script
ALTER TABLE tiki_secdb convert to character set DEFAULT COLLATE DEFAULT
Specified key was too long; max key length is 1000 bytes
Error in unknown patch script
ALTER TABLE users_objectpermissions convert to character set DEFAULT COLLATE DEFAULT
Specified key was too long; max key length is 1000 bytes
{CODE}

The profile feature of Tiki is a really powerful tool, but it could be more flexible in processing user input before applying profiles.
Right now, it is only possible to request string (Input Text) data from the user during applying a profile .
I'm planning to do a really customizable profile, that can be configured via the user request form.
It should be possible to have more supported controls like checkboxes, radio buttons and (single/multi) dropdown selections.
Then these input data should also be used within a condition (IF/ELSE statements) to react on these user input during processing the profile apply.

__Example:__

Show a list of predefined groups an a offer to the admin user.
He can select, what groups are needed and which are then automatically set up by the profile:

[[ ] Group Sales
[[ ] Group Marketing
[[ ] Group Administration

Visuals possibly like:
* list of checkbox (multiple selection)
* radio button group (single selection)
* dropdown (Bootstrap) which can be used with single and multi selection

__Important:__
By having such controls available it is mandatory to be able to use them with conditions (IF/ELSE IF/ELSE) within the YAML code to be able to switch processing on the given selection.

__Further profile related ideas:__
* Secured profile repositories (password required, profile user which can be permitted)
>> Option to hide profile content to public and registered users

At the bottom of this page, the text "News" (and the others) is too close to the external link icon.

tiki-admin_external_wikis.php does not seem to work at this point. Show instance is created. Please see home page.

Hi, I've setup a Facebook application to work with other systems and all is fine I can use the FB login feature. When using Tiki however, I go to Login then Login with Facebook option and straight away I hit this in the browser:

{CODE(theme="default")}Possible cross-site request forgery (CSRF, or "sea surfing") detected. Operation blocked.{CODE}

If I hit "Confirm Action":

1. if no fb_xxxxx user is created then a user called fb_ gets created but without any email or name

2. if fb_ user exists per above then login gets denied with:

{CODE(theme="default")}We were unable to create a new user with your Facebook account. Please contact the administrator.{CODE}

In the log all I see is "cannot connect to facebookGraph".

The userid and pass are both installed in Tiki for my FB app and I have the FB callback URL set to: FQDN/tiki-socialnetworks.php?request_facebook as per the documentation.

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.

I got this error when upgrading a Tiki 15 site to Tiki 19 on a hosted server. The files are a new branch 19 checkout (r68949), and the database is an existing Tiki 15 database I want to update to 19. The error message followed clicking the "Update the database" button in the install screens.

Fatal error: Uncaught Error: Call to a member function set_preference() on null in /home/.../installer/schema/20180410_install_piwik_plugin_tiki.php:17 Stack trace: #0 /home/.../installer/installlib.php(177): upgrade_20180410_install_piwik_plugin_tiki(Object(Installer)) #1 /home/.../installer/installlib.php(132): Installer->installPatch('20180410_instal...') #2 /home/.../installer/tiki-installer.php(1049): Installer->update() #3 /home/.../tiki-install.php(106): include_once('/home/.../...') #4 {main} thrown in /home/.../installer/schema/20180410_install_piwik_plugin_tiki.php on line 17

Any clues on how I should proceed, or if this is site-specific or a general bug?

This salmon background with dark blue selector has not my vote. (at all)
Can’t we have nicer and less agressive colours ?

I upgraded to 18.0 and got this error, then I upgraded to 18.1 and still got this error.

I erase the website, built a new database, and I still get this error.

When I try to upload a file to file gallery
MetArt01s.jpg
File upload failed: SyntaxError: Unexpected token < in JSON at position 0

After a basic PluginListExecute with editable filters, once we submit an action, we are redirected to the page where all filters are duplicated. See GIF below:

https://cl.ly/0698c9a23f29

The "Find" button on tiki-listpages.php only, when clicked, causes some page reloading but no form appears. I didn't see an JavaScript errors reported.