Loading...
 
Skip to main content

Category: Bug

Tickets reporting bugs. Some bugs reports can be categorized in more specific categories such as "Bug::Security" and do not *have* to be directly categorized in this category, but it is never an error to categorize a bug report in this category.
Bug
Show subcategories objects

Name Type
Looking at "events" in products tracker yields exception
My tiki contains a products tracker from the shop profile. I do not know why, but it's wrench symbol carries a "view events". When clicked, it yields this exception:
{CODE(Colors="Tiki")}
undefined extension class 'Smarty_Internal_Runtime_CheckPlugins'
{CODE}
I don't need events in this tracker, and I do not want that my users click on it, being confronted with the exception...
tracker item
Loosing Header Numbering when editing text
I'm reporting this for version 25 but I have experienced this issue since tiki was a teenager.
If you create a numbered heading with {CODE(caption="sample" wrap="0" colors="tiki" theme="default")}!!#Next Step
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum{CODE}
And later your either edit the whole wiki page with the drop down edit items from the top right of the wiki page or you do a section edit by clicking the little edit icon next to the header, it looses the # symbol every time and needs to be inserted again. Its quite annoying .
{img fileId="8302"}
tracker item
Loss of Categories going to v24.2
I just upgraded from 21.2 to 24.2 on my Tiki Wiki at: https://firehallsagas.com/tiki-index.php.

When I did so, my subcategories disappeared. Rather, the pages show they're part of the category structure still (you can see in the pictures below). The individual pages are still listed as objects in their subcategories.

However, I don't see them in the Admin Category section. They're no longer showing in the module. I can't assign new pages to these subcategories. The module to display Categories no longer gives me the option with the red triangle to show subcategories.

{img fileId="1928" thumb="box"}
Here's the default look which shows no objects under each. The previous default was to show all the objects in the category.

{img fileId="1929" thumb="box"}
Here it is again, with no objects to show.

{img fileId="1930" thumb="box"}
This is what it shows if you set the "show subcategories objects." Note the variety of categories to the right of the listing. These subcategories still exist.

{img fileId="1931" thumb="box"}
However, as you can see here, I cannot move items in the organizer except between the root categories.

{img fileId="1937" thumb="box"}
As you can see, the only categories I can see when I am editing a file are the root files.

{img fileId="1932" thumb="box"}
{img fileId="1933" thumb="box"}
{img fileId="1934" thumb="box"}
{img fileId="1935" thumb="box"}
{img fileId="1936" thumb="box"}
If I go to add a new category, you can see that the subcategories still exist when I click Parent.

{img fileId="1938" thumb="box"}
As you can see from the screenshot from Wednesday, which I was lucky to have, that the Categories module on the right shows all the subcategories. You'll note that on all the previous pictures, the current category module has no way to show the subcategories.

All of this changed immediately upon the upgrade. I went through all the settings I could find in Category. I even got rid of the Category PlugIn and re-installed it. It kept the subcategories, which is nice, but didn't fix the problem, which is not.

What am I doing wrong?

tracker item
Lost wiki attachment functionality on upgrade from 24.2 to 25.0
It seemed to happen in 24.2 all of a sudden, so I upgraded to 25.0 to see if it would fix the issue but no, I can no longer attach an image to a wikipage using either the button at the bottom of the page or the button in the file galleries section. So I figure tiki is confused in a database setting.

All files are stored in a directory that has worked just fine previously
tracker item
Five plugins cannot be activated
Five of the plugins in 18.7 cannot be activated. Simply, because there is NO checkbox for "activate"! How come? Have they been withdrawn? If so, why wasn't their heading removed? Headings are there, hints also, but no "activate".

The non-activateable are

- footnotearea (cf note: footnote is there!)
- paymentlist
- pdfbookmark
- pdfpage
- pdfpagebreak
tracker item
Lots of wrongly escaped quotes in /lib/prefs/feature.php
/lib/prefs/feature.php contains 11 instances of quote characters that are wrongly escaped. To my understanding of PHP they shouldn't be escaped with a backslash if they are in single quote strings, which they are.

Example:
{CODE(Colors="Tiki")}
'feature_jquery_zoom' => [
'name' => tra('jQuery zoom'),
'description' => tra('Enables zoom in images on mouseover or click. Used in Plugin Img with the parameter \"thumb=zoombox\"'),
'type' => 'flag',
'help' => 'PluginImg#Zoombox',
'default' => 'n',
],
{CODE}

The description string is enclosed in single quotes, yet the double quotes that are part of the string were escaped with backslashes. And the strings are fed into tra().

This leads to the backslashes being visible to the user in English language, and making translating really hard: The only way that tra() will catch these with a content from custom.php is double escaping like this:

{CODE(Colors="Tiki")}
"Enables zoom in images on mouseover or click. Used in Plugin Img with the parameter \\\"thumb=zoombox\\\"" => "Emöglicht, in Bilder hineinzuzoomen bei Mouseover oder Klick. Im Img-Plugin mit dem Parameter \"thumb=zoombox\" verwendet",
{CODE}

I'm not sure if many writers of other translations out there know about this implication...

Not all strings in feature.php have been escaped like this, actually there are 11 instances of \" in there. Some, actually many, strings were written the right way like this example:

{CODE(Colors="Tiki")}
'feature_jquery_reflection' => [
'name' => tra('Reflection'),
'description' => tra('Creates a reflection under an image. Used in Plugin Img with the parameter "class=reflect"'),
'type' => 'flag',
'help' => 'JQuery#Reflection',
'default' => 'n', // reflection effects on images
],
{CODE}

The 11 instances are on lines 1526 (2), 1841 (2), 2084 (2), 2191 (2), 2928 (2). Line 2496 uses \" for something else.
tracker item
Make 26.x work on show2.tiki.org
As Tiki 26+ needs PHP 8.1 of greater we need to add this to show2.tiki.org please.

I created a test instance here [http://bsfez-11581-8531.show2.tiki.org] but i\m not expecting to to complete the install yet...

Thanks (:mrgreen:)
tracker item
maketoc generates "super Table of Contents" with too many headings in Multiprint
__The message below was edited.__ {sign user="Chealer9" datetime="2018-06-08T15:57:21+00:00"}

We are running into an issue of maketoc appending onto itself if more than one maketoc appear per page. for starters, our server is TikiWiki 3.2, Windows Server 2003, apache 2.2.13, mysql 5.1.39, php 5.3.0, Multiwiki setup.

We are seeing this in ((doc:Multiprint)). What I am seeing is that if I have Tikipage A with a ~np~{maketoc}~/np~ at the VERY top and headings 1, 2, 3 and Tikipage B with a ~np~{maketoc}~/np~ at the VERY top and headings 4, 5. When I Multiprint using the Pages selector (both Tikipage A and B) there will be 2 TOCs displayed in the resulting print page. The first TOC will show 1,2,3 and further down the page will be 1,2,3,4,5 (when I expected only 4,5). We are trying to Mulitprint hundreds of pages (and most have their own maketoc) so the very last TOC takes up 15 pages itself (after accumulating TOCS over 100s of wiki pages). Big problem for us as our nurses need to have a hardcopy/offline copy on hand in case our systems go down.



So it is the parsing of the maketoc that is causing the appending of subsequent TOCs. I found a bug by "larryg" where he tries to fix a similar issue (cf {wish id=2781} and [http://tikiwiki.org/tiki-view_forum_thread.php?topics_offset=1&forumId=2&comments_parentId=34791]) but his fix did not work for me. I think that he is on the right track. Does anyone know of a fix? Has anyone experienced this? Is it fixed in 4.x?

Thanks in advance,

Tim
tracker item
Markdown in Tiki 27 depends on external source for the WYSIWYG markdown editor
{syntax type="tiki" editor="plain"}
Hi. I've installed Tiki 27.0 and turned on markdown (which is marked as experimental). When I try to create a wiki page, the editor is just missing. Nothing can be entered. This is due to my javacript blocker. It's called Noscript and is a Firefox extension.

According to Noscript, there is a dependency on toast.com, for some javascript code. It looks like the editor component is loaded from that external source. When I allow for javascript code to be loaded from toast.com, then the editor appears and it works.

It's a security problem, in my eyes. I don't want to have to trust some external source, like toast.com. The markdown editor should be included in Tiki, like all the many other libraries and components.

(Aside: There isn't any accurate choice for the mandatory "Category" field, so I've chosen "Bug". Maybe there should be added an "Other" category).
tracker item
Markdown plugin does not parse quoted text properly
Hello,

While trying to convert some blog posts to Tiki by using Markdown plugin I noticed several problems...First one is that when using quoted text, Tiki does not parse it properly.

Here is the text snippet:

-+Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
tempor incididunt ut labore et dolore magna aliqua. Mauris pharetra et
ultrices neque. Id consectetur purus ut faucibus pulvinar elementum
integer enim. Sed euismod nisi porta lorem mollis. Dui nunc mattis enim
ut tellus elementum sagittis vitae et. Porttitor eget dolor morbi non
arcu risus quis. Aliquam purus sit amet luctus venenatis lectus magna.
Ipsum suspendisse ultrices gravida dictum. In mollis nunc sed id semper
risus in. Arcu risus quis varius quam.

> Mattis rhoncus urna neque viverra justo nec. Aliquet nec ullamcorper
> sit amet. Sit amet venenatis urna cursus eget nunc. Maecenas accumsan
> lacus vel facilisis volutpat est. Consequat ac felis donec et. Aliquam
> vestibulum morbi blandit cursus risus at.

> A diam maecenas sed enim ut sem viverra. Consequat nisl vel pretium
> lectus. Ultricies integer quis auctor elit sed vulputate. Scelerisque
> in dictum non consectetur. Scelerisque eleifend donec pretium
> vulputate sapien nec sagittis aliquam.

A diam maecenas sed enim ut sem viverra. Consequat nisl vel pretium
lectus. Ultricies integer quis auctor elit sed vulputate. Scelerisque in
dictum non consectetur.+-


Here {img fileId="1295" thumb="box"} you can see how does it look like.

tracker item
markdown rendering issues
{syntax type="tiki" editor="plain"}
Rendering of mixed un-numbered and numbered lists has issues in tiki wiki pages, e.g.,

```markdown
* unnumbered level 1
* unnumbered level 2
1. numbered level 3
* unnumbered level 4
2. numbered level 3
```

should be rendered like

```markdown
* unnumbered level 1
* unnumbered level 2
1. numbered level 3
* unnumbered level 4
2. numbered level 3
```

but tiki actually renders it to

```markdown
* unnumbered level 1
* unnumbered level 2
1. numbered level 3
2. unnumbered level 4
3. numbered level 3
```

Apart from "unnumbered level 4" item getting numbered (I get unintended numberings of list items quite a lot in tiki),
the actual spaces before each bullet point/number seems to not follow any common convention but appears to be basically random.

To best of my knowledge, two blanks before the first numbered item below an unnumbered item should be used
to make it align properly under the text of the unnumbered item above.
But tiki renders the above with an unintended huge indention for the "unnumbered level 4" item.

commonmark renders this just fine, see

https://spec.commonmark.org/dingus/?text=*%20unnumbered%20level%201%0A%09*%20unnumbered%20level%202%0A%20%20%20%20%20%201.%20numbered%20level%203%20%0A%20%20%20%20%20%20%20%20%20%20*%20unnumbered%20level%204%20%0A%20%20%20%20%20%202.%20numbered%20level%203%20%0A%60

There seems to be no way to properly include code blocks here. I will try show2.tiki.org...
...does not work either "Lost Tiki database connection".

Please check the source of this post to better understand the issue.
Thanks.

tracker item
Mass replace in wiki pages fails
I go to page tiki-search_replace.php

I try to replace
-+ [https://wiki.inesss.qc.ca/ +-
with
-+ [ +-
in all wiki pages

I see a section of pages.
I select all of them.
I click on the "Replace" button at the bottom

Nothing was replaced. No error message either.

Replacing -+ https://wiki.inesss.qc.ca/ +- with nothing failed in the exact same way

More info :
If I don't actually « select all of them », all works well for small values, like "10".

If I select all of them, Tiki fails silently while the error log shows :
[17-Feb-2020 15:44:26 America/New_York] PHP Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in Unknown on line 0

tracker item
Mathematical Calculation Field, "Less-Than" function has Logical Error
Create a tracker with a Numeric and a Mathematical Calculation Field.
I want to append a zero to numbers less than 10 to patch a tracker sort order listing issue
(if (less-than testingtrackerNum 10)
(concat 0 testingtrackerNum) testingtrackerNum
)

The above function adds a zero to any number less than 11. Even though the upper test limit is 10.
So the test (less-than 10 10) will be true, which is not the case in reality .
Look at the attached screen grab too
tracker item
Mathematical Calculation on Item List cannot concat the items
on tiki 25.3
The following will work
(count
(for-each
(list parent)
(formula (coalesce childrenNames))
)
)
it outputs e.g. 10

But if you want to see the actual childrenNames you just see Array as the answer
(for-each
(list Parent)
(formula (concat childrenNames))
)

Output=Array
As seen in attachment
tracker item
media-alchemist package installation errors
I can't install media-alchemist due to several problems.. When attempted in 21.x through packages web control panel, this output is shown:
{CODE()}
Problem 1
- Conclusion: don't install media-alchemyst/media-alchemyst 0.5.5
- Conclusion: remove monolog/monolog 2.0.2
- Conclusion: don't install monolog/monolog 2.0.2
- Installation request for media-alchemyst/media-alchemyst ^0.5.4 -> satisfiable by media-alchemyst/media-alchemyst[0.5.4, 0.5.5].
- Conclusion: don't install monolog/monolog 2.0.2
- media-alchemyst/media-alchemyst 0.5.4 requires monolog/monolog ~1.0 -> satisfiable by monolog/monolog[1.0.0, 1.1.0, 1.10.0, 1.11.0, 1.12.0, 1.13.0, 1.13.1, 1.14.0, 1.15.0, 1.16.0, 1.17.0, 1.17.1, 1.17.2, 1.18.0, 1.18.1, 1.18.2, 1.19.0, 1.20.0, 1.21.0, 1.22.0, 1.22.1, 1.23.0, 1.24.0, 1.25.0, 1.25.1, 1.25.2, 1.25.3, 1.4.0, 1.4.1, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.9.1, 1.0.1, 1.0.2, 1.2.0, 1.2.1, 1.3.0, 1.3.1].
- Can only install one of: monolog/monolog[1.17.0, 2.0.2].
- Can only install one of: monolog/monolog[1.17.1, 2.0.2].
- Can only install one of: monolog/monolog[1.17.2, 2.0.2].
- Can only install one of: monolog/monolog[1.18.0, 2.0.2].
- Can only install one of: monolog/monolog[1.18.1, 2.0.2].
- Can only install one of: monolog/monolog[1.18.2, 2.0.2].
- Can only install one of: monolog/monolog[1.19.0, 2.0.2].
- Can only install one of: monolog/monolog[1.20.0, 2.0.2].
- Can only install one of: monolog/monolog[1.21.0, 2.0.2].
- Can only install one of: monolog/monolog[1.22.0, 2.0.2].
- Can only install one of: monolog/monolog[1.22.1, 2.0.2].
- Can only install one of: monolog/monolog[1.23.0, 2.0.2].
- Can only install one of: monolog/monolog[1.24.0, 2.0.2].
- Can only install one of: monolog/monolog[1.25.0, 2.0.2].
- Can only install one of: monolog/monolog[1.25.1, 2.0.2].
- Can only install one of: monolog/monolog[1.25.2, 2.0.2].
- Can only install one of: monolog/monolog[1.25.3, 2.0.2].
- Can only install one of: monolog/monolog[2.0.2, 1.17.0].
- Can only install one of: monolog/monolog[2.0.2, 1.17.1].
- Can only install one of: monolog/monolog[2.0.2, 1.17.2].
- Can only install one of: monolog/monolog[2.0.2, 1.18.0].
- Can only install one of: monolog/monolog[2.0.2, 1.18.1].
- Can only install one of: monolog/monolog[2.0.2, 1.18.2].
- Can only install one of: monolog/monolog[2.0.2, 1.19.0].
- Can only install one of: monolog/monolog[2.0.2, 1.20.0].
- Can only install one of: monolog/monolog[2.0.2, 1.21.0].
- Can only install one of: monolog/monolog[2.0.2, 1.22.0].
- Can only install one of: monolog/monolog[2.0.2, 1.22.1].
- Can only install one of: monolog/monolog[2.0.2, 1.23.0].
- Can only install one of: monolog/monolog[2.0.2, 1.24.0].
- Can only install one of: monolog/monolog[2.0.2, 1.25.0].
- Can only install one of: monolog/monolog[2.0.2, 1.25.1].
- Can only install one of: monolog/monolog[2.0.2, 1.25.2].
- Can only install one of: monolog/monolog[2.0.2, 1.25.3].
- Can only install one of: monolog/monolog[1.0.0, 2.0.2].
- Can only install one of: monolog/monolog[1.0.1, 2.0.2].
- Can only install one of: monolog/monolog[1.0.2, 2.0.2].
- Can only install one of: monolog/monolog[1.1.0, 2.0.2].
- Can only install one of: monolog/monolog[1.10.0, 2.0.2].
- Can only install one of: monolog/monolog[1.11.0, 2.0.2].
- Can only install one of: monolog/monolog[1.12.0, 2.0.2].
- Can only install one of: monolog/monolog[1.13.0, 2.0.2].
- Can only install one of: monolog/monolog[1.13.1, 2.0.2].
- Can only install one of: monolog/monolog[1.14.0, 2.0.2].
- Can only install one of: monolog/monolog[1.15.0, 2.0.2].
- Can only install one of: monolog/monolog[1.16.0, 2.0.2].
- Can only install one of: monolog/monolog[1.2.0, 2.0.2].
- Can only install one of: monolog/monolog[1.2.1, 2.0.2].
- Can only install one of: monolog/monolog[1.3.0, 2.0.2].
- Can only install one of: monolog/monolog[1.3.1, 2.0.2].
- Can only install one of: monolog/monolog[1.4.0, 2.0.2].
- Can only install one of: monolog/monolog[1.4.1, 2.0.2].
- Can only install one of: monolog/monolog[1.5.0, 2.0.2].
- Can only install one of: monolog/monolog[1.6.0, 2.0.2].
- Can only install one of: monolog/monolog[1.7.0, 2.0.2].
- Can only install one of: monolog/monolog[1.8.0, 2.0.2].
- Can only install one of: monolog/monolog[1.9.0, 2.0.2].
- Can only install one of: monolog/monolog[1.9.1, 2.0.2].
- Can only install one of: monolog/monolog[2.0.2, 1.0.0].
- Can only install one of: monolog/monolog[2.0.2, 1.1.0].
- Can only install one of: monolog/monolog[2.0.2, 1.10.0].
- Can only install one of: monolog/monolog[2.0.2, 1.11.0].
- Can only install one of: monolog/monolog[2.0.2, 1.12.0].
- Can only install one of: monolog/monolog[2.0.2, 1.13.0].
- Can only install one of: monolog/monolog[2.0.2, 1.13.1].
- Can only install one of: monolog/monolog[2.0.2, 1.14.0].
- Can only install one of: monolog/monolog[2.0.2, 1.15.0].
- Can only install one of: monolog/monolog[2.0.2, 1.16.0].
- Can only install one of: monolog/monolog[2.0.2, 1.4.0].
- Can only install one of: monolog/monolog[2.0.2, 1.4.1].
- Can only install one of: monolog/monolog[2.0.2, 1.5.0].
- Can only install one of: monolog/monolog[2.0.2, 1.6.0].
- Can only install one of: monolog/monolog[2.0.2, 1.7.0].
- Can only install one of: monolog/monolog[2.0.2, 1.8.0].
- Can only install one of: monolog/monolog[2.0.2, 1.9.0].
- Can only install one of: monolog/monolog[2.0.2, 1.9.1].
- Installation request for monolog/monolog (locked at 2.0.2) -> satisfiable by monolog/monolog[2.0.2].
{CODE}

When attempted through the command line with this command,
{CODE()}
php temp/composer.phar require --update-no-dev --prefer-dist media-alchemyst/media-alchemyst:^0.5.4
{CODE}

This is then the error message shown:
{CODE()}
root@computer: /var/www/html/21.x# php temp/composer.phar require --update-no-dev --prefer-dist media-alchemyst/media-alchemyst:^0.5.4
Do not run Composer as root/super user! See https://getcomposer.org/root for details
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Conclusion: don't install media-alchemyst/media-alchemyst 0.5.5
- Conclusion: remove monolog/monolog 2.0.2
- Conclusion: don't install monolog/monolog 2.0.2
- Installation request for media-alchemyst/media-alchemyst ^0.5.4 -> satisfiable by media-alchemyst/media-alchemyst[0.5.4, 0.5.5].
- Conclusion: don't install monolog/monolog 2.0.2
- media-alchemyst/media-alchemyst 0.5.4 requires monolog/monolog ~1.0 -> satisfiable by monolog/monolog[1.0.0, 1.1.0, 1.10.0, 1.11.0, 1.12.0, 1.13.0, 1.13.1, 1.14.0, 1.15.0, 1.16.0, 1.17.0, 1.17.1, 1.17.2, 1.18.0, 1.18.1, 1.18.2, 1.19.0, 1.20.0, 1.21.0, 1.22.0, 1.22.1, 1.23.0, 1.24.0, 1.25.0, 1.25.1, 1.25.2, 1.25.3, 1.4.0, 1.4.1, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.9.1, 1.0.1, 1.0.2, 1.2.0, 1.2.1, 1.3.0, 1.3.1].
- Can only install one of: monolog/monolog[1.17.0, 2.0.2].
- Can only install one of: monolog/monolog[1.17.1, 2.0.2].
- Can only install one of: monolog/monolog[1.17.2, 2.0.2].
- Can only install one of: monolog/monolog[1.18.0, 2.0.2].
- Can only install one of: monolog/monolog[1.18.1, 2.0.2].
- Can only install one of: monolog/monolog[1.18.2, 2.0.2].
- Can only install one of: monolog/monolog[1.19.0, 2.0.2].
- Can only install one of: monolog/monolog[1.20.0, 2.0.2].
- Can only install one of: monolog/monolog[1.21.0, 2.0.2].
- Can only install one of: monolog/monolog[1.22.0, 2.0.2].
- Can only install one of: monolog/monolog[1.22.1, 2.0.2].
- Can only install one of: monolog/monolog[1.23.0, 2.0.2].
- Can only install one of: monolog/monolog[1.24.0, 2.0.2].
- Can only install one of: monolog/monolog[1.25.0, 2.0.2].
- Can only install one of: monolog/monolog[1.25.1, 2.0.2].
- Can only install one of: monolog/monolog[1.25.2, 2.0.2].
- Can only install one of: monolog/monolog[1.25.3, 2.0.2].
- Can only install one of: monolog/monolog[2.0.2, 1.17.0].
- Can only install one of: monolog/monolog[2.0.2, 1.17.1].
- Can only install one of: monolog/monolog[2.0.2, 1.17.2].
- Can only install one of: monolog/monolog[2.0.2, 1.18.0].
- Can only install one of: monolog/monolog[2.0.2, 1.18.1].
- Can only install one of: monolog/monolog[2.0.2, 1.18.2].
- Can only install one of: monolog/monolog[2.0.2, 1.19.0].
- Can only install one of: monolog/monolog[2.0.2, 1.20.0].
- Can only install one of: monolog/monolog[2.0.2, 1.21.0].
- Can only install one of: monolog/monolog[2.0.2, 1.22.0].
- Can only install one of: monolog/monolog[2.0.2, 1.22.1].
- Can only install one of: monolog/monolog[2.0.2, 1.23.0].
- Can only install one of: monolog/monolog[2.0.2, 1.24.0].
- Can only install one of: monolog/monolog[2.0.2, 1.25.0].
- Can only install one of: monolog/monolog[2.0.2, 1.25.1].
- Can only install one of: monolog/monolog[2.0.2, 1.25.2].
- Can only install one of: monolog/monolog[2.0.2, 1.25.3].
- Can only install one of: monolog/monolog[1.0.0, 2.0.2].
- Can only install one of: monolog/monolog[1.0.1, 2.0.2].
- Can only install one of: monolog/monolog[1.0.2, 2.0.2].
- Can only install one of: monolog/monolog[1.1.0, 2.0.2].
- Can only install one of: monolog/monolog[1.10.0, 2.0.2].
- Can only install one of: monolog/monolog[1.11.0, 2.0.2].
- Can only install one of: monolog/monolog[1.12.0, 2.0.2].
- Can only install one of: monolog/monolog[1.13.0, 2.0.2].
- Can only install one of: monolog/monolog[1.13.1, 2.0.2].
- Can only install one of: monolog/monolog[1.14.0, 2.0.2].
- Can only install one of: monolog/monolog[1.15.0, 2.0.2].
- Can only install one of: monolog/monolog[1.16.0, 2.0.2].
- Can only install one of: monolog/monolog[1.2.0, 2.0.2].
- Can only install one of: monolog/monolog[1.2.1, 2.0.2].
- Can only install one of: monolog/monolog[1.3.0, 2.0.2].
- Can only install one of: monolog/monolog[1.3.1, 2.0.2].
- Can only install one of: monolog/monolog[1.4.0, 2.0.2].
- Can only install one of: monolog/monolog[1.4.1, 2.0.2].
- Can only install one of: monolog/monolog[1.5.0, 2.0.2].
- Can only install one of: monolog/monolog[1.6.0, 2.0.2].
- Can only install one of: monolog/monolog[1.7.0, 2.0.2].
- Can only install one of: monolog/monolog[1.8.0, 2.0.2].
- Can only install one of: monolog/monolog[1.9.0, 2.0.2].
- Can only install one of: monolog/monolog[1.9.1, 2.0.2].
- Can only install one of: monolog/monolog[2.0.2, 1.0.0].
- Can only install one of: monolog/monolog[2.0.2, 1.1.0].
- Can only install one of: monolog/monolog[2.0.2, 1.10.0].
- Can only install one of: monolog/monolog[2.0.2, 1.11.0].
- Can only install one of: monolog/monolog[2.0.2, 1.12.0].
- Can only install one of: monolog/monolog[2.0.2, 1.13.0].
- Can only install one of: monolog/monolog[2.0.2, 1.13.1].
- Can only install one of: monolog/monolog[2.0.2, 1.14.0].
- Can only install one of: monolog/monolog[2.0.2, 1.15.0].
- Can only install one of: monolog/monolog[2.0.2, 1.16.0].
- Can only install one of: monolog/monolog[2.0.2, 1.4.0].
- Can only install one of: monolog/monolog[2.0.2, 1.4.1].
- Can only install one of: monolog/monolog[2.0.2, 1.5.0].
- Can only install one of: monolog/monolog[2.0.2, 1.6.0].
- Can only install one of: monolog/monolog[2.0.2, 1.7.0].
- Can only install one of: monolog/monolog[2.0.2, 1.8.0].
- Can only install one of: monolog/monolog[2.0.2, 1.9.0].
- Can only install one of: monolog/monolog[2.0.2, 1.9.1].
- Installation request for monolog/monolog (locked at 2.0.2) -> satisfiable by monolog/monolog[2.0.2].

Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.

Installation failed, reverting ./composer.json to its original content.
root@computer:/var/www/html/21.x# php temp/composer.phar require --update-no-dev --prefer-dist monolog/monolog:^1.0.0
Do not run Composer as root/super user! See https://getcomposer.org/root
{CODE}
I could solve by means of downgrading the monolog/monolog package to 1.x, and then reinstalling through command line worked.
{CODE()}
root@computer:/var/www/html/21.x# php temp/composer.phar require --update-no-dev --prefer-dist monolog/monolog:^1.0.0
Do not run Composer as root/super user! See https://getcomposer.org/root for details
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies
Package operations: 22 installs, 1 update, 0 removals
- Installing symfony/polyfill-ctype (v1.14.0): Loading from cache
- Installing symfony/filesystem (v3.4.38): Downloading (100%)
- Installing symfony/polyfill-mbstring (v1.14.0): Loading from cache
- Installing symfony/debug (v4.4.5): Downloading (100%)
- Installing symfony/console (v3.4.38): Downloading (100%)
- Installing pimple/pimple (v1.0.2): Downloading (100%)
- Downgrading monolog/monolog (2.0.2 => 1.25.3): Downloading (100%)
- Installing evenement/evenement (v1.1.0): Downloading (100%)
- Installing alchemy/binary-driver (1.6.0): Downloading (100%)
- Installing swftools/swftools (0.3.2): Downloading (100%)
- Installing php-unoconv/php-unoconv (0.3.1): Downloading (100%)
- Installing php-mp4box/php-mp4box (0.3.0): Downloading (100%)
- Installing neutron/temporary-filesystem (2.4): Downloading (100%)
- Installing doctrine/cache (1.10.0): Downloading (100%)
- Installing php-ffmpeg/php-ffmpeg (0.5.1): Downloading (100%)
- Installing imagine/imagine (v0.6.3): Downloading (100%)
- Installing symfony/http-foundation (v2.5.4): Downloading (100%)
- Installing doctrine/collections (1.6.4): Downloading (100%)
- Installing phpexiftool/exiftool (10.10): Downloading (100%)
- Installing alchemy/phpexiftool (0.7.2): Downloading (100%)
- Installing alchemy/mediavorus (0.4.10): Downloading (100%)
- Installing alchemy/ghostscript (0.4.0): Downloading (100%)
- Installing media-alchemyst/media-alchemyst (0.5.5): Downloading (100%)
Package robloach/component-installer is abandoned, you should avoid using it. Use oomphinc/composer-installers-extender instead.
Writing lock file
Generating autoload files
> ComponentInstaller\Installer::postAutoloadDump
Compiling component files
root@computer:/var/www/html/21.x# php temp/composer.phar require --update-no-dev --prefer-dist media-alchemyst/media-alchemyst:^0.5.4
Do not run Composer as root/super user! See https://getcomposer.org/root for details
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies
Nothing to install or update
Package robloach/component-installer is abandoned, you should avoid using it. Use oomphinc/composer-installers-extender instead.
Generating autoload files
> ComponentInstaller\Installer::postAutoloadDump
Compiling component files
root@computer:/var/www/html/21.x#
{CODE}
tracker item
Migrate wiki attachement failed when upgrading a Tiki25 to Tiki26
{syntax type="tiki" editor="plain"}
I upgraded a Tiki25 to Tiki26.
When login as admin I had a warning that console command attachments:migrate has not been executed.

On execution I had the following error.


{CODE()}
/public_html$ php console.php attachments:migrate
Processing page mydomain Website Pages, attachment 15 apagename.html...
Undefined variable $galleryId on line 58 of /home/mydomain/public_html/lib/core/Tiki/FileGallery/Manipulator/Validator.php
PDOStatement::execute(): SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'comment' at row 1 on line 114 of /home/mydomain/public_html/lib/core/TikiDb/Pdo.php
A error was encountered while running a command
Data too long for column 'comment' at row 1 on line 17 of /home/mydomain/public_html/lib/core/TikiDb/Exception.php
{CODE}
tracker item
Migrating 18.8 to 21.4 fails utterly, breaks layout
I have test-upgraded my test site (which is a copy of the productive site with slightly less content, but duplicate files, layout, CSS) and upgrading failed. Miserably.

First, there was one (1) SQL error:
{CODE(Colors="Tiki")}
UPDATE `users_objectpermissions` SET `permName` = 'tiki_p_read_article' WHERE `permName` = 'tiki_p_topic_read' AND `objectType` = 'topic'
Duplicate entry '4dadd7eebd7a5fc8790114f9f5aaa8b6-topic-Anonymous-tiki_p_read_art' for key 'PRIMARY'
{CODE}

For the moment, I checked the checkmark in order to proceed (it's not the productive site anyway, and I have a backup of both the files and the DB).

After logging in, I was flabbergasted. I thought my layout (originally done by Gary to imitate a standard layout of 12.14 that was dropped with later updates: Geo) was kind of conservative, absolutely nothing fancy. Standard, classic Tiki layout with 3 containers, a header, a left module zone, a center wiki content and a right module zone.

There is one horizontal menu which was VERY hard to create on 18.8 (because creating menus from scratch is simply not possible (at all) on 18.8., due to an unfixed bug. I made it possible with a trick, I created a second standard menu, exported it, modified it as needed, and re-imported.

Since at that time I did not want to indulge in the depths of the CSS, I created style directives in the context of the menu, which worked satisfactorily. Most of the site is classic Wiki content. Some articles for news, a calendar (which was horribly bug-ridden and thus dysfunctional on 18.8) and a small shop (CART).

So nothing fancy at all. No categories (besides what CART brought with it), no perspectives, etc.

And now the catastrophe: The left module zone is now sitting on the right, and the right module zone went to far-right. Yes, both left and right module zone now sit on the right-hand side.

The menu is a mess with wrong fonts, wrong sizing, wrong spacing etc.

When I call the control panels, they come up as one column (!) in a seemingly endless page, hardly usable at all.

This is the worst upgrade I have ever witnessed. And I thought 12.14 -> 18.2 was a bad. Little did I know...

I checked the look & feel setting, found nothing special in there, it is still on "classic Tiki 3 container". The admin setting was off, to "1 container", but setting that to "Classic Tiki 3 container" to match the site's default changed nothing...

If Tiki keeps breaking my layouts, I am seriously considering to let go. If it weren't for more than one decade of content, I would be gone already. Enough is enough.
tracker item
Migration of image gallery doesn't migrate
Hi,

when you have an image gallery (from days with prior Tiki Wiki versions) you are encouraged to migrate it to file galleries. There is also a feature named "migrate".

I now had some spare time and wanted to do this, which I have long evaded. I clicked on migrate.

But it does not migrate... I only copies the contents of the image gallery to file galleries. Btw, the folder that gets created in that process should have its name piped through tra() in order to translate it.

On the positive side, I saw that all folders and all image really made it into the file galleries.
On the negative: There was no migration. On Wiki pages, all images are still taken from the image gallery and not from the file galleries...

So either this should be changed so that all calls for migrated images are transscribed into calls from the file galleries OR this process should be renamed "copy to file galleries".

Copy is okay, it does make things a little easier, but to my understanding of the word "migration", a migration would be to transscribe all image calls on all Wiki pages, something that still is tremendous work if you have many pages to convert...

Thanks
hman
tracker item
Missing 'save' button when editing a structure
When changing a wiki structure with drag and drop in tiki-edit_structure.php, the 'save' button doesn't appear as it does in Tiki 18/19.
It's keeps being hidden by css with display:none, beside that it also doesn't work; it will not save the changes.

Please see as showed here, it's possible to drag a new page in to the structure but there is no save button.
http://wobow-11900-7179.show2.tikiwiki.org/tiki-edit_structure.php?page_ref_id=1
tracker item
Missing "array_merge" when the custom.php file is created by Tiki (admin, I18n)
When you use the I18n admin control panel for the first time to create a custom translation (/tiki-language-manage_custom_translations) , it create the custom.php file.

However translation are not performed as it miss at the end of the file (like in the sample file we distribute : custom.php_example)
~pp~$lang = array_merge($lang, $lang_custom);~/pp~

Once you paste it custom translation are working.

Update: Even if you paste it in the file it is removed each time a translation is saved.
tracker item
Modifying permissions
{syntax type="tiki" editor="plain"}
When trying to apply changes to the permission - nothing happens. In other words, I tried to set permissions for admins by selecting several permissions and hitting the apply button. Nothing happens and permissions are not granted.

It looks as if the apply button does not get actionned at all.
tracker item
Module "New User Registration" cannot be added anywhere
There is a module named "New User Registration" with the explanation "Permit anonymous visitors to create an account on the site". But as soon as you try to add this module anywhere (being admin, of course) you are immediately thrown onto the home page with an error message "You are logged in".
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 loadstats doesn't work when positioned bottom
For some time, I have wondered why I did not see the module loadstats contents, just it's headline. At first I thought it might be a localization problem (I use the localized German version of 18.3 at the moment) and looked up the module's real name and localized name, and added it again.

Funny thing: At first I had two module loadstats at the bottom. One worked, and the other did not. So I removed what I thought was the first, but then the only remaining reverted to not show it's contents. So I removed that one, too. And added the module once again, but by mistake in position top. There it worked as it should.

So I just wanted to move to position bottom, so that was the only thing I changed: From top to bottom. And it stopped working. Moving it back up to top cured this, so this behaviour is reproducible.

Thanks
hman
tracker item
Module login_box does not use localization
The module login_box to ask for user credentials and to log out does not make use of the localization, therefore is always in English and does not respond to custom.php, even when the missing array_merge is added to custom.php.
tracker item
Show PHP error messages