Category: 30.x

{syntax type="tiki" editor="plain"}
My "was just fine with Tiki29" tracker forms have now extra space added after a text Area tracker field.

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

{syntax type="tiki" editor="plain"}
When upgrading Cartograf from Tiki 21.x (possibly 24.x?) to 27.x we found that "[https://gitlab.com/tikiwiki/tiki/-/merge_requests/2170|duplicate cascade]" wasn't set on the child trackers to duplicate features when a map is duplicated.

This used to happen always before this option was added but it would be nice, espescially if "Cascade actions" is set to "All" on the ItemLink fields, then -+duplicateCascade+- should be set to "Yes" (1).

{syntax type="tiki" editor="plain"}
When you hover a user name the user avatar is always missing now

{syntax type="tiki" editor="plain"}
Try e.g. hover user names in comments here: https://trunkdev.tiki.org/item8893-Tracker-fields-table-displays-on-empty-page-without-navigation-was-Tracker-fields-table-overflows-out-of-center-column#threadId12031

{syntax type="tiki" editor="plain"}
Trying to select users with user selector is not working at all

{syntax type="tiki" editor="plain"}
We have now 2 new switches that are added at the bottom of an item:
* add comment
* notify to

The UI should be improved

{syntax type="tiki" editor="plain"}
To reproduce, on a Tiki30 on a wiki page add a new plugin.

~np~Near the bottom you will see: 0="[object Object]"~/np~

{syntax type="tiki" editor="plain"}
To reproduce;
When you just create a tracker (no fields yet) and check the properties Duplication you can enable the feature.
Doing so you will see "Field Duplication Rules" but it look like broken or incomplete.

I believe this is because there are no fields yet to apply any rule.

Additionally, if all the field are needed to apply the rules, some text should say: "You need to complete first your fields and tracker then revisit this panel..." (english need wording)

{syntax type="tiki" editor="plain"}
The first problem is that even when the admin preference to display the page title is turned off, there is still an empty h1 tag and heading link in the page. This takes up vertical space and the link icon is visible if the space is hovered over. Turning off the page title display should also "turn off" the heading and link code in the template. When the pref to display the page title is activated, the page title text that displays does have an h1 tag but it has no link code or icon.

The second problem is that the preference option "Display page name as page title" causes the page title to be displayed ''above'' the ''main'' element. This is not good HTML or DOM structure, not good for accessibility, etc.

The third problem is that the preference option "Display the page name inside the page content" doesn't actually cause the page name to be displayed inside div class="content". It's not clear to me why this div was added when there was already an article element and a div id="page-data" (or why the "content" class wasn't added to the div id="page-data"), but IMO the preference name and HTML should be consistent. (Usually there's no visible difference, but a theme might give the page content a different style than the rest of the page, so in this case it's a significant distinction.) The h1 heading tag and link icon that has no text, described in the first paragraph, is actually located correctly, inside div class="content", IMO.

Comparing to versions 27 and 28, it looks like to me that the admin handling of the wiki page title display hasn't been good for a while now so I can understand the motivation to make some changes but there appears to be more work to do.

{syntax type="tiki" editor="plain"}
In case we have "Wiki page edit buttons location" set (Preference name: wiki_actions_bar) to "Both" (shows buttons on top and bottom) the bottom "Cancel edit" is not working.

{syntax type="tiki" editor="plain"}
When you click "Start Changes Wizard" button on tiki-wizard_admin.php?stepNr=0&url=index.php it shows "New in Tiki 26" in big letters and that is the latest (newest) version that wizard page was updated for (except it just shows "URL Fragment format" as a new preference; otherwise it is just empty). When you click "Save and Continue" it shows "New in Tiki 25", etc. (at least there is a bit more features to set up).

__We should update that wizard to include some major new stuff from Tiki 30 at least before we release!__

{syntax type="tiki" editor="plain"}
When you monitor a page and do some changes then save, your user should not receive a notification.
This work, your user don't receives notifications on own changes.

But the success message is misleading, for exemple my user "me@blabla.com" edited a page and the feedback says:

 Success
Page 00Bernardplayground2 saved (version 88).
To review the changes you have just made compare the versions in history of this page.

 Notification sent to:
me@blabla.com, riki@blabla.com

Feedback is wrong, I won't be notified.

{syntax type="tiki" editor="plain"}
On tiki-admin_modules.php, the "Add module" button should link to the first tab "Edit module", not "Custom modules", because in most cases an existing module will be assigned, not a new custom one created. (The Edit module tab content contains the heading "Assign new module", which reflects that process.)
* So the "Add module" button link should be tiki-admin_modules.php?edit_assign=0&cookietab=1, not tiki-admin_modules.php?edit_assign=0&cookietab=2.
* Thinking about it more, it seems like the first tab label should be "Configure new module", not "Edit module", to better reflect the content of the tab. Modules are edited after being assigned, from their actions link, not in this tab, or else are edited as custom modules, but again not here.
* The "Assign new module" heading in the first tab content can then be removed, as it would be redundant.
I believe the button link issue is a regression but I don't know when it happened offhand.

Another thing, after selecting the module to assign, the page refreshes to an "Edit module" tab and there's a heading "Edit this assigned module: login_box". This is a smaller issue, maybe, but this heading is incorrect because the module is not yet assigned, which might confuse new users. To be accurate, it should be "Edit module: login_box".

{syntax type="tiki" editor="plain"}
I installed a Tiki 30 from git using an existing DB to be upgraded.

On DB validation I had a white screen and this is the error log:

{CODE()}
[23-May-2026 06:17:12 UTC] PHP Warning: Undefined array key "feature_fixed_width" in /blabla.bsfez.com_tiki30/installer/schema/20260312_change_fixed_width_default_tiki.php on line 18
[23-May-2026 06:17:12 UTC] PHP Fatal error: Uncaught Exception: Found 1 unsupported mail queue entries (serialized in old Laminas/Zend format). These entries cannot be processed. WARNING: These entries will be DELETED if you proceed with --auto-register, and queued email data will be lost. To delete them and continue, rerun:<info> php console.php database:update --auto-register</info> in /blabla.bsfez.com_tiki30/installer/schema/20260430_remove_unsupported_mail_queue_entries_tiki.php:42
Stack trace:
#0 /blabla.bsfez.com_tiki30/installer/Installer.php(192): upgrade_20260430_remove_unsupported_mail_queue_entries_tiki(Object(Tiki\Installer\Installer))
#1 /blabla.bsfez.com_tiki30/installer/Installer.php(143): Tiki\Installer\Installer->installPatch('20260430_remove...')
#2 /blabla.bsfez.com_tiki30/installer/tiki-installer.php(562): Tiki\Installer\Installer->update()
#3 /blabla.bsfez.com_tiki30/tiki-install.php(132): include_once('/Users/bernards...')
#4 {main}
thrown in /blabla.bsfez.com_tiki30/installer/schema/20260430_remove_unsupported_mail_queue_entries_tiki.php on line 42
xxxxx htdocs %
{CODE}

{syntax type="tiki" editor="plain"}
To test RTL support in Tiki currently, I turned on the necessary i18n preferences and specified a right-to-left language, Urdu, and created a page written in Urdu. But the page continued to display left-to-right. According to [https://getbootstrap.com/docs/5.3/getting-started/rtl/#required-html], -+ dir="rtl" +- needs to be set on the -+ html +- element. So even after turning on all the i18n settings that seem to be necessary and even specifying an RTL language (Urdu) as the site default, the HTML element still didn't get the -+ dir +- attribute.

When I add -+ dir="rtl" +- to the -+ html +- element manually with the browser's dev tools editor, then the page displays correctly for the RTL language (text goes right to left, left column goes to right side, etc.)

I see code at the top of each -+ layout_view.tpl +- file to add the -+ dir="rtl" +- but there must be a bug preventing it from not functioning here.

I think once this HTML attribute issue is fixed, then we can document the recommended Bootstrap method to implement LTR and this feature will work well for interested users.

{syntax type="tiki" editor="plain"}
I'm on Tiki Wiki 29 I enabled the Tiki Tags feature.
I'm using some tags on wiki page and I have set some tags.
But the keyword tags are not displayed in the head.

I went at tiki-admin.php?page=metatags (admin metatags).
I checked that "Include tags" is enabled. But I have also noticed I no Keywords set in the field Keywords.

As result I have no keyword on the page.
If I add just one keyword in the field, on the page i see this keyword but also all other missing keywords.

The condition for the elseif branch only triggers if either metatag_keywords or metatag_local_keywords is non-empty.

NOTE: I don't use forum so I didn't touch anything related to the way the forum fill its keywords. It may worth to have a look at it.

{syntax type="tiki" editor="plain"}
Under certain condition the img plugin add image quality information that is breaking image transparency when using .png file.

On a Tiki 30 i have the following:
{img fileId="3254" thumb="box"}

A weird background is visible.

The plugins:
-+{img type="fileId" featured="y" class="img-fluid text-center"}+-

The HTML:
{CODE()}
<img src="dl571?display&amp;format=png&amp;quality=75" class="img-fluid text-center regImage pluginImg571 img-fluid featured " alt="Image">
{CODE}

If I remove "format=png" the image is displayed with the correct transparency.

It seems to come from here: lib/wiki-plugins/wikiplugin_img.php

{CODE()}
if (isset($imgdata['quality'])) {
$src .= '&format=' . str_replace('image/', '', $imgdata['file']->filetype) . '&quality=' . $imgdata['quality'];
}
{CODE}


Note a brand new Tiki by default (like demo.tiki.30.t.o) doesn't show the issue.
Could be file quality encoded data (on the file) or something that changed in the code.

---

I used the parameter "An image anywhere on the internet" and pointed to my file to fix the issue:
{CODE()}
{img type="src" src="display571" alt="Sovereign Offsite Backup Service" responsive="y" class="img-fluid text-center"}
{CODE}

Test on dev.t.o

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

{syntax type="tiki" editor="plain"}
When you look at tiki-admin.php?page=textarea with basic pref. filter the Markdown section is not visible.

With the Advanced pref filter the section title is visible but no options are available.

This doesn't look right.
Or we show it with options to use or not. Seeing the title...

{syntax type="tiki" editor="plain"}
At tiki-admin.php?page=login admin can set "CAPTCHA questions and answers".

A question with a single answer.
-+What is the capital of France:Paris+-

However this is fine for ===unique=== language Tikis.
If you use French+English+German you should be able to ask the question and have an answer depending on the language displayed.

{syntax type="tiki" editor="plain"}
A user with the right perms access to the Wiki list pages (tiki-listpages) and there can "copy" a page to a new page. (it should be called "duplicate" IMO)

The same user should be able to do it from a page itself with an item in the "More" or the "wiki actions bar" dropdown.

{syntax type="tiki" editor="plain"}
As the title says, it should be possible to use the Tiki console (console.php) to empty any tiki logs.
That would ease and even allow automatisation of maintenance operations.

{syntax type="tiki" editor="plain"}
You can't see or edit the left or right column modules on tiki-admin_modules.php any more (without clicking show hidden modules, and when you save anything they get hidden again).

Critical regression, release blocker!

{syntax type="tiki" editor="plain"}
This feature arrived in {mr id=5960} but wan't made optional sadly, i might get round to it one day, so this is just a reminder really

{syntax type="tiki" editor="plain"}
Menu dropdowns (with Smartmenus turned on) are opening upward when there is no need to, such as in the default system menu in the left column, when there is plenty of space to open in the normal downward position. This is caused by the class "dropdown-menu-bottom" in the menu code. Could this class just be removed?

In my experience (Windows 11, Edge and Firefox browsers), Smartmenus dropdowns will open upward when the parent item is near the bottom viewport edge and there isn't enough room for them to open downward. I thought this problem was resolved a few months ago but it's back in master currently.

{syntax type="tiki" editor="plain"}
I have a menu with a third-level dropdown, followed by another link in the second level, as shown in the attached screenshot. The menu is saved, including the last option, "One more link", but the menu doesn't show the item "One more link" in the second-level dropdown, or anywhere. Another master instance here on my localhost also has the same problem. The second-level dropdown items just get truncated after the link with the dropdown. This obviously doesn't happen with first-level links, but is happening with second-level links (and probably with third-level, etc. links).

This is a regression maybe linked to the change in Smartmenus versions.