The directory feature isn't maintained much because web directories are mostly a thing of the past, but as long as it's still in Tiki, probably its pages shouldn't have broken layout. The page is tiki-directory_browse.php and the file is tiki-directory_browse.tpl. Mostly it's the "find" form layout that needs updating to be similar to other find forms in Tiki.
Other details could be improved. For example the breadcrumbs element doesn't seem to use the breadcrumbs preference for link divider. And in general the page layout could be nicer.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
The code looks like this (right, it's also missing ARIA attributes):
{tr}{$forumOrder|escape}{/tr}
but only the label displays. There's no forum order information. Apparently this page is related: tiki-admin.php?page=forums&cookietab=2&highlight=forums_ordering so maybe something set here should show up as forum order on the forum's main admin tab, but I don't really know. Anyway, either the data should display or the label should be removed.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
alt=""
but it's empty because there's no form input when editing the article to specify it.To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
After checking out in-page navigation outside of Tiki and doing some searching for best practices, I'd like to make a few suggestions for improvement.
First of all, about the current situation of autotoc in master (to be Tiki 27), I came across these bugs, that I think are known already, plus some recommendations:
• Autotoc feature itself (suggestions for improvement):
.** If the autotoc is longer than the viewport height, then either make dropdowns for lower-level links like a vertical menu, so there are visual cues (dropdown arrows) that they are there, or put the whole nav in a div with overflow-y:scroll. But actually I think the whole thing should display, and the reader can scroll the page if the toc extends down out of sight.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
I couldn't use Webcron in 26.2 on Debian 11.9 with PHP 8.2.12, my cronjobs didn't run which caused some problems. After calling the cron-URL I got an error.
I call:curl -6 -k https://tiki.exmaple.com/cron.php?token=cb64a63643d1500bb978e612597f5ae8
Fatal error: Uncaught TypeError: Unsupported operand types: string + int in /var/www/html/cron.php:53 Stack trace: #0 {main} thrown in /var/www/html/cron.php on line 53
I can fix this by editing cron.php by changing
if ($last_cron_run + $cron_interval >= $start_time) {
if (strtotime($last_cron_run) + $cron_interval >= $start_time) {
After that the cronjobs were working again, calling the Webcron-URL resulted in a blank page.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
On a wiki page when you create a wiki link from the toolbar on the page field there is an autocomplete/search system that allow you to insert existing pages.
This is not working anymore and the field (page selector) is not populated.
It has been tested at doc.t.o the bug is also visible on dev.t.o and other Tikis.
This is basic Wiki Page and it is important it is fixed rapidly.
Note: If I insert manually the wiki link, "Tiki Newsletter February 2024" is ok while "Tiki-Newsletter-February-2024" is not ok. Somehow I remember it should work the same with the dash.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
Under Menu > Navigation in the admin settings, attempting to edit the menu's Details/Options (via the dialog accessed using the edit/pencil button) results in the following error:
This means that no options can be updated for menus. Name, group restrictions, et al. Menus can still be re-ordered and re-arranged, but no settings, labels, or other features are saving.
This is a brand-new, fresh install, and I am not seeing any errors when updating any other content or items.
Steps to reproduce:
Faulty consequence:
Expected behavior:
Workaround:
Use menus without permissions or customization. This means that menu items that should not appear for, say, anonymous users will still appear, and take the visitor to an error/access denied message. Menu link, title and position are the only things that can be changed, as they can be adjusted through the menu options list.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
The Smarty template usage indicator isn't naming the template. The page source just shows
TPL:
/TPL:
(HTML comment tags removed here so the content will show.) This is in master.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.