Category: 29.x
Show subcategories objects| Name | Type |
|---|---|
| Enable Image Compression on Upload to Improve Wiki Page Load Times | tracker item |
|
Error on https://dev.tiki.org/Wishlist: Oops trackerId parameter must be present
{syntax type="tiki" editor="plain"} When you go to https://dev.tiki.org/Wishlist and first remove the "Open" status from the "Status:" field and then click to sort the results column by "Modified" you get an error 403 and feedback in a remarksbox: {CODE()}Oops trackerId parameter must be present <!--//--><![CDATA[//><!-- // js 0 window.elementPlus = {"select":{"enabled":true,"clearable":true,"collapseTags":true,"maxCollapseTags":3,"filterable":true,"allowCreate":false,"ordering":true},"autocomplete":true}; //--><!]]>{CODE} {img src="display3244" thumb="box"} |
tracker item |
|
Extend the URL that the anonymous user is redirected to when a page is not found to all users
{syntax type="tiki" editor="plain"} At : tiki-admin.php?page=general#contentadmin_general-3 We have an option : The URL that the anonymous user is redirected to when a page is not found The work fine. When an anonymous it a 404 he see the page. But that doesn't work with registered. Why not extend to anyone when a page is not found ? That would be very useful. |
tracker item |
|
Grouping metatags and SEO related fields on a wiki page properties
{syntax type="tiki" editor="plain"} We have now a new option to set the "Content of the tag title" on the properties of a Wiki page. We had a previous metatags field, "Page Description (used for metatags)" that can be enabled at tiki-admin.php?page=metatags Enabling it add a field "Description (used for metatags)" to the properties of a Wiki page. We have also "Will be added to the sitemap". While these fields are related they are not grouped in the wiki page properties and all options seems mixed without any consideration as you can see in this example. {img fileId="3139" thumb="box"} Note: This is just an example other option, preferences and parameters based on admin settings should checked. Anyway, these should be grouped in a more logical way having in mind the user experience. |
tracker item |
|
HTML element is missing dir attribute for RTL support
{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. |
tracker item |
|
If you don't have one keywords set on the admin, metatags no Tiki Tags is set as keyword even if they exist
{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. |
tracker item |
|
Image alternative text in article has become mandatory and it prevent saving older article unless it has a value (error is hiden)
{syntax type="tiki" editor="plain"} On an upgraded Tiki to version 29.1 I have articles using their own image and no "Image alternative text" was set as this is not mandatory. However if I try to modify the content an old article on save the page reload no save and I don't see an error. Only when I go to the "Image" tab of the edit article interface I can see an error message. Add a value for the field "Image alternative text" solve the issue. If a value is mandatory NOW, a red asterisk or something on the field should show it is mandatory. If a user edit an article that was created BEFORE the change then the issue should be pointed inside or outside the tab Image so the user see what is the problem. |
tracker item |
|
Img plugin Thumb=box parameter is broken on Tiki29
{syntax type="tiki" editor="plain"} The parameter thumb="box" is not applied anymore. The sample below should be a thumbnail not a full screen image. {img fileId="1215" thumb="box"} |
tracker item |
|
Impossible to add an existing page to a structure in tiki documentation
{syntax type="tiki" editor="plain"} It's impossible to add an existing page to a structure. Here I was trying to add the Nginx page https://doc.tiki.org/Nginx to Structure: Tiki Installation Guide / Advanced Settings Doesn't work on https://copydoc.tiki.org/ either Problems: 1- The procedure is super hard to find, buried in the second paragraph of (couter-intuitively) the new page section: https://doc.tiki.org/Structure-User#Adding_a_new_page 2- The officially documented procedure doesn't work a) There is no drop target feedback when you try to move the page from the search at the bottom of https://copydoc.tiki.org/tiki-edit_structure.php?page_ref_id=3571&find_objects=nginx&search_objects=Filter&categId= to a part of the structure. b) Mouse wheel scrolling is inhibited while scrooling, so it's impossible to reach many elements of the structure. That's a bug. If it's also a misfeature, the search area should not scrool with the structure. c) The drop doesn't work. Nothing seems to happen no matter what part of the structure element I drop the page on. d) Even if it did work, the save button referred to in the doc would appear off screen at the top. 3- The intuive procedure (the places a normal use would look) isn't there. a) From the https://copydoc.tiki.org/Advanced-Settings page, I presume I am supposed to use the "Type to search ... | Add Page | [] Child" interface on the right of the structure navigation. But: I. There is no hover help II. If I type and select the Nginx page and click Add Page, it takes me to the edit page of the right page. But if I save the page, it's not added to the structure. III. The "Child" Button has no effect on the above. Even if it were a new page, I don'T understand what it's for. I am already on a a structure page, where else than as a child would I want to add the page (new or existing). But maybe it's for something else, once again there is now hover help. b) From the page itself https://copydoc.tiki.org/Nginx I. For a site using structure, if I have access to edit the pages I would expect an interface to add the page to a structure for a site using structures. But I guess some people may only want structures on part of the site. II. From the edit interface (https://copydoc.tiki.org/tiki-editpage.php?page=Nginx), I have a Categories tab. I would expect a similar "Structures" tab. Failing that The interface clearly implies that clicking on Properties / Structures would allow me to place it, but it does not pre-fill the page in search (It should at the very least point to https://copydoc.tiki.org/tiki-edit_structure.php?page_ref_id=3571&find_objects=nginx&search_objects=Filter) , and it should work (so back to problem 2) |
tracker item |
|
In Tiki 29.0-beta new install, configuration wizards show error message
{syntax type="tiki" editor="plain"} Testing the new Tiki 29.0 beta, on configuration wizard pages (tiki-wizard_admin.php), an error message is displayed at the top of the page: {QUOTE()}Too late to modify headers. Headers already sent by output_headers() called at [C:\laragon\www\Other\tiki-29.0.beta\temp\templates_c\en_admin^f9b63c6bdf795e3e08f52a05c45794fe0e5bd8d4_0.file_header.tpl.php:155]){QUOTE} I don't know if functionality is affected but in any case this doesn't look good on intial setup screens. |
tracker item |
|
Inline style attribute stripped in DIV plugin and others in Tiki29.x
{syntax type="tiki" editor="plain"} The style= attribute passed to {DIV} and other wiki plugins is silently dropped. I believe (I'm not pro understanding git) it comes from here: https://gitlab.com/tikiwiki/tiki/-/commit/7b9d81b6f30c7532bee770079ddeead22838a3f1 In lib/wiki-plugins/wikiplugin_div.php, the function wikiplugin_div() initializes $style = '' before calling extract($params, EXTR_SKIP). Because EXTR_SKIP skips extraction when a variable already exists, the style parameter from $params never overwrites the empty $style variable. At lib/wiki-plugins/wikiplugin_div.php I changed : {CODE()} function wikiplugin_div($content, $params) { $style = ''; extract($params, EXTR_SKIP); {CODE} For {CODE()} function wikiplugin_div($content, $params) { extract($params, EXTR_SKIP); $style = $style ?? ''; {CODE} refreshed the cache en the issue was fixed. |
tracker item |
|
Issue with hreflang tag in the page header
{syntax type="tiki" editor="plain"} We have now, when we use multilingual, an hreflang tag that is added to display alternates pages. This is it should work; Every page in a multilingual set should: * List itself with its own hreflang. * List all other language/region versions. Ensure all those other pages return the favor. But in Tiki, it create ONLY the code for the alternative pages. IE: I have 3 page for en, fr and de. There should 3 alternate rel link, one for each language. However, when I'm on the de (German language) page, I see only: <li <li This leads to error on website checkers. {img fileId="3141"} |
tracker item |
|
Issues with chunkSizeWarningLimit value that is unset at vite.config.mjs and is set by default to 500 (on my osx setup)
{syntax type="tiki" editor="plain"} When I compile a Tiki27 or 28 or 29 from git I have a warning about the "chunkSizeWarningLimit" that is limited to 500. To fix it I edited src/js/vite.config.mjs and added; {CODE(caption="line 159, after: target: "es2022")} chunkSizeWarningLimit: 2500, {CODE} {CODE(caption="line 197, after: //preserveModulesRoot: 'src/js/',)} manualChunks(id) { if (id.includes("node_modules")) { if (id.includes("jspdf") || id.includes("html2canvas")) { return "vendor-pdf"; } if (id.includes("element-plus")) { return "vendor-element-plus"; } return "vendor"; } }, {CODE} May be this could be of some help ? |
tracker item |
|
It is not possible for a registered user to assign himself to a group with userChoice enabled
{syntax type="tiki" editor="plain"} Currently, users cannot join groups even when the `userChoice` option (“User can assign himself or herself to the group”) is enabled, unless they also have additional group-related permissions. This change allows self-assignment when `userChoice` is enabled, without requiring extra permissions. The `userChoice` option is intended to allow users to join groups themselves, not to grant permission to add other users. Requiring `group_add_member` contradicts this purpose. The `group_add_member` permission remains enforced when adding other users. This aligns the behavior with the expected purpose of `userChoice` groups. |
tracker item |
|
It is not possible to delete a menu option anymore on Tiki29
{syntax type="tiki" editor="plain"} It is not possible to delete a menu option anymore on Tiki29. (among other errors) Videoshot: https://streamable.com/ykmbu7 |
tracker item |
|
It should be possible to duplicate a wiki page from the "More" button or the wiki actions bar
{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. |
tracker item |
|
It should be possible to flush any Tiki logs or syslogs from console commands
{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. |
tracker item |
|
Module go to a 500 related to theme_navbar_fixed_topbar_offset (multiple errors in fact)
{syntax type="tiki" editor="plain"} On a Tiki29 (updated from Tiki27) I had a 500 error trying to access different admin areas. I could track the issue on the admin module panel. {CODE()} thrown in /home/opensourcesolutions/public_html/tiki-admin_modules.php on line 638 #0 {main} Stack trace: [20-Oct-2025 13:14:47 UTC] PHP Fatal error: Uncaught TypeError: Unsupported operand types: string + int in /home/opensourcesolutions/public_html/tiki-admin_modules.php:638 thrown in /home/opensourcesolutions/public_html/tiki-admin_modules.php on line 638 {CODE} Tracking the error lead me to understand that, in this Tiki the "theme_navbar_fixed_topbar_offset" was empty. And this caused a problem. After reseting to the default 90px i could access to the module. This shouldn't happen. ;-) |
tracker item |
|
Module title "Git detail" should be improved
{syntax type="tiki" editor="plain"} The module title "Git detail" is not normal English. Usually as a title or heading, the plural form "details" would be used, and especially so in this case since there are two details, the git commit hash and the date and time. So at minimum I strongly recommend changing "detail" to "details". But "Git detail(s)" in the module header and "Git information" in the module body have essentially the same meaning, so there's some redundancy here; so I suggest changing the module title to "Git information" and then changing "Git information" to "Branch" or "Commit" or "Branch and commit" (whatever would be better) in the module body. Also, a small thing, but there needs to be a space after the colon following "master". |
tracker item |
|
Monitor Tiki Performance is firing multiple times per page, on every page load - Admin should be warned
{syntax type="tiki" editor="plain"} Enabling the Monitor Tiki Performance (tiki_monitor_performance) is adding a lot to the logs and consuming resource. It is to be used for some time and not be enable 24/7. Admin may enable this without real knowledge of this cost. Even if it is part of the advanced preferences, a warning should be added next to the checkbox. |
tracker item |
|
Newsletter unsubscribe link always fails — inputConfiguration filters hash as 'bool'
{syntax type="tiki" editor="plain"} Clicking the unsubscribe link in a newsletter email always results in the error "Your request to unsubscribe failed", even though the subscription record and code exist in the database. The subscription is never removed. Tiki 29.x (confirmed). Likely affects all versions where the $inputConfiguration array is present with this filter. !!Steps to Reproduce #Enable the Newsletters feature #Create a newsletter and add a subscriber (email-based, non-user) #Send a newsletter edition #Open the received email and click the unsubscribe link, e.g.: #https://example.com/tiki-newsletters.php?unsubscribe=bfaea1b540a27940684c99854449549c #The page displays: "Your request to unsubscribe failed" #The subscription record remains in tiki_newsletter_subscriptions — nothing was deleted In tiki-newsletters.php, the $inputConfiguration array declares the unsubscribe parameter with a 'bool' filter: {CODE()} $inputConfiguration = [ [ 'staticKeyFilters' => [ 'unsubscribe' => 'bool', //post // ... ], ], ]; {CODE} There is a legal concern with so I will commit a fix right away. Non-functional unsubscribe links may violate anti-spam regulations (CAN-SPAM, GDPR) |
tracker item |
|
No title or filename or text for new attachment on Tiki29.x trackers
{syntax type="tiki" editor="plain"} When you attach a file to a a tracker item using the attachment tracker feature, the file is uploaded and stored (where?) but it has no title or filename. Also remove and edit icons look out of their places. {img fileId="3238" thumb="box"} |
tracker item |
|
Not possible to change the recategorization event of a field Category when the category uses non-latin leters
{syntax type="tiki" editor="plain"} I have a Tiki29 in hebrew. I use trackers and I have a field "Categorize tracker item". If I change the option "recategorization event" (from save to indexing) Tiki feedback show a red error with "name is required". The modal close and nothing is saved. I don;t know since when it is broken, but it used to work... {img fileId="3215" thumb="box"} |
tracker item |
|
Not possible to upload a file at dev.t.o
{syntax type="tiki" editor="plain"} It is not possible to upload a file when filling a ticket. #I create a bug report #I select the icon uploap in the text area description #I navigate to the correct folder I want to drop a screenshot (liste galleries -> bug report -> bsfez) #I drop the image on the upload area (I wait to be sure no timeout in the background) #I click on insert The upload fails: {CODE()} FileGalUploader.vue:23 POST https://dev.tiki.org/tiki-ajax_services.php?controller=file&action=upload 413 (Content Too Large) FileGalUploader.vue:23 UploadAjaxError: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>413 Request Entity Too Large</title> </head><body> <h1>Request Entity Too Large</h1> The requested resource does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit. </body></html> at $e (ajax.mjs:24:10) at XMLHttpRequest.<anonymous> (ajax.mjs:64:29) at XMLHttpRequest.i (helpers.js:74:23) {CODE} |
tracker item |
__Problem__:
When inserting large (e.g., 5 MB) images from the gallery into wiki pages, they load slowly, affecting user experience.
Users often forget or don’t know how to compress images before uploading.
''There's currently no way to reduce image size from within Tiki''.
__Feature Suggestion__:
Add an option during image upload to compress the image, either by:
A compression quality slider (e.g., 0–100%)
Predefined levels (High Quality / Balanced / Compressed)
The system should compress the image before saving it to the gallery. Optionally, admins could allow saving the original uncompressed file separately.