Category: Regression

Some wysiwyg wiki pages lose content on edit-save.

Just editing the page, not changing anything and saving changes the page display.

Example with a ~np~<br style="clear: left;">~/np~ which is changed into ~np~<p> </p>~/np~

The result is loss of confidence into the wysiwyg edition from users, since parts of the page they did not edit are visually messed up.

------
!Issue

If you look at [http://jyhem-9952-5164.show.tikiwiki.org/tiki-index.php?page=JML+test+03] and view the source of revision 1, it contains
{CODE(wrap="1")}<table align="left" border="1" cellpadding="0" cellspacing="0" style="width:50%;">
<tbody>
<tr>
<td style="text-align:left;">
<div class="more" style="text-align:left;margin-left:36px;">
<p><strong>Contents</strong></p>
</div>

<p>bla bla bla</p>
</td>
</tr>
</tbody>
</table>

<br style="clear: left;">
<h2>Distribution</h2>

<p>Although the disease probably originated in southeast Asia, the first recording of the disease was made in 1874 in Australia, where it was observed at Eagle Farm near Brisbane</p>{CODE}

And visually, the Title __Distribution__ is ''below'' the table because of a ~np~<br style="clear: left;">~/np~

If this is not what you can see in [http://jyhem-9952-5164.show.tikiwiki.org/tiki-index.php?page=JML+test+03], just rollback to version 1

Then you can edit the page, and it does not show correctly. If you save it without touching anything, the code is now:
{CODE(wrap="1")}<table align="left" border="1" cellpadding="0" cellspacing="0" style="width:50%;"><tbody><tr><td style="text-align:left;">
<div class="more" style="text-align:left;margin-left:36px;">
<p><strong>Contents</strong></p>
</div>

<p>bla bla bla</p>
</td>
</tr></tbody></table><p> </p>

<h2>Distribution</h2>

<p> </p>

<p>Although the disease probably originated in southeast Asia, the first recording of the disease was made in 1874 in Australia, where it was observed at Eagle Farm near Brisbane</p>{CODE}

This should not happen (change the page content when no change is actually done). On big pages, it is impossible to go edit a little part of the page and then check that nothing else anywhere else was changed :-(
This has 2 main visual problems after edit-save:
* The title __Distribution__ is not ''below'' the table, it wraps on the right side.
* There is an extra line below the title __Distribution__ due to the newly appeared ~np~<p> </p>~/np~

On Tiki 21.
To reproduce, go at : https://next.tiki.org/tracker22
Edit an item from the actions (wrench) menu on the right of the table.

The design is broken.

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

Tested on one of my Tikis from a plugin list, on save it also goes to the page "undefined" instead of staying on the page (refresh ?) (I tried updating a value and without updating a value)
https://share.vidyard.com/watch/XivK6CHsiD5MKVxLdnFX76?

Works on Tiki 20 with the same database and it works as previously:
https://secure.vidyard.com/organizations/230727/players/4Xs7Tyhok7peWDZUFLB8uv

Same if I want to delete an item from the wiki pages (tiki-listpages.php):
{img fileId="1367" thumb="box"}

But erasing it from the page itself work.

{syntax type="tiki" editor="plain"}
After upgrade to 27.5 (I have not observer this in 27.2), edits made to Wiki Plugins on any given Wiki Page cause PHP errors related to missing language definition.
# Assigned language of the Wiki Page is removed (causing a PHP error, and "No language assigned" message)
# Page Description is removed
The above can be reverted using History, but it's practically impossible to edit Plugins without causing data loss (description).
User is forced to manually re-assign language (which fixes PHP errors), and insert new Page Description.
Tested on fresh install of 27.5

PHP errors shown on affected page are related to translated-lang.tpl (missing language)
^<?php echo $_smarty_tpl->getSmarty()->getModifierCallback('escape')($_smarty_tpl->getValue('trads')[0]['langName']);?>
(<?php echo $_smarty_tpl->getSmarty()->getModifierCallback('escape')($_smarty_tpl->getValue('trads')[0]['lang']);?>^

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

It seems some internal code in tiki to use elastic search needs to be updated to work with ElasticSearch 5.x:

Installed a blank new tiki, changed unified search engine to ElasticSearch (using v5.0.2 in Ubuntu 16.04 with their elasticsearch repository to have updated packages), and I applied Collaborative_Community_12 profile. I saw these errors just above the instructions page:

{CODE()}
Error(s)

Indexing failed while processing "HomePage" (type wiki page) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Instructions" (type wiki page) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Community" (type wiki page) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Wiki Help" (type wiki page) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "1" (type forum) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "1" (type tracker) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "1" (type trackerfield) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "2" (type trackerfield) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "3" (type trackerfield) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "4" (type trackerfield) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "5" (type trackerfield) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "6" (type trackerfield) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "1" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "2" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "3" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "4" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "5" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "6" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "7" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "8" (type trackeritem) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Community Members HomePage" (type wiki page) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Anonymous" (type group) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Registered" (type group) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Editors" (type group) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "SubAdmins" (type group) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
Indexing failed while processing "Admins" (type group) with the error "The [string] type is removed in 5.0 and automatic upgrade failed because parameters [term_vector] are not supported for automatic upgrades. You should now use either a [text] or [keyword] field instead for field [title]"
{CODE}

And when I reindex, I get these other error messages:
{CODE()}
Error

all shards failed
×
Error

Indexing failed while processing "Community" (type wiki page) with the error "no such index"
×
Error

Indexing failed while processing "1" (type forum) with the error "no such index"
×
Error

Indexing failed while processing "1" (type file gallery) with the error "no such index"
×
Error

Indexing failed while processing "1" (type trackeritem) with the error "no such index"
×
Error

Indexing failed while processing "1" (type tracker) with the error "no such index"
×
Error

Indexing failed while processing "1" (type trackerfield) with the error "no such index"
×
Error

Indexing failed while processing "admin" (type user) with the error "no such index"
×
Error

Indexing failed while processing "Admins" (type group) with the error "no such index"
Rebuild Index
Your index was last fully rebuilt on Wednesday November 30, 2016 09:55:03 UTC.
×
Indexed

wiki page: 5
forum post: 0
forum: 1
file: 0
file gallery: 3
trackeritem: 8
tracker: 1
trackerfield: 6
comment: 0
user: 1
group: 5
{CODE}

See: https://doc.tiki.org/tiki-syslog.php

{img fileId="658"}

{syntax type="tiki" editor="plain"}
When I click the emoji icon on the toolbar in master, nothing happens.

The syntax:

-+ ~np~{filter field="tracker_field_permName" content="NOT "}~/np~+-

No longer works in plugin list in 23.x (and possibly 22.x) with elasticsearch.

It still works fine with the mysql engine, but it definitely fails (and finds everything, empty or not) in es7, 6 and 5.

More... finally confirmed the last version it worked in was 18.x, 21.x is broken too (also that i could only get 18.x to work properly with es5, 6 and 7 refused to index successfully) {sign user="jonnybradley" datetime="2021-08-09T17:41:43+00:00"}

{syntax type="tiki" editor="plain"}
Empty slides are added on the Wiki page slideshow

Visible here : https://doc.tiki.org/slideshow

[Edit, 2 April 2016, Torsten]
The bug seems to be fixed by rjsmelo r58016 - ( thx Nelson for emailing me).
Before I close, I want to do a more in-depth test later to night or so, but it really seems to work (did resend out a wikisyntax-wysiwyg html+ txt version newsletter, that previously caused false encoding when received and today it was sent and received smoothly and intact).

Before I describe in detail, I`ll setup a show instance.

Strings from the main app menu in the side column in 24.x from git today, or tiki24beta(.tar.gz) show wrong encoding.
Reproduced with Catalan, Spanish and French,

Using all defaults. In Ubuntu 18.04 and 20.04 computers, with mysql Innodb (all default options at installation time)

{img fileId="1734" thumb="box" width=1000}

---
Attempting to create a show2.t.o instance, I get this error (could it be related?)
{CODE()}
Fatal error: Uncaught Error: Undefined constant 'TIKI_PATH' in /var/www/xavi-9794-8089/lib/core/Tiki/TikiInit.php:51 Stack trace: #0 /var/www/xavi-9794-8089/lib/tikilib.php(63): Tiki\TikiInit::getContainer() #1 /var/www/xavi-9794-8089/lib/init/tra.php(106): TikiLib::lib() #2 /var/www/xavi-9794-8089/lib/init/tra.php(58): init_language() #3 /var/www/xavi-9794-8089/lib/init/tra.php(27): tra() #4 /var/www/xavi-9794-8089/tiki-install.php(122): tr() #5 {main} thrown in /var/www/xavi-9794-8089/lib/core/Tiki/TikiInit.php on line 51
{CODE}

{syntax type="tiki" editor="plain"}
Hello,

This concerns the [http://dev.tikiwiki.org/Search+Bugs] and [http://dev.tikiwiki.org/tiki-index.php?page=Search+Bugs]

I have yet reported this bug, but because of three crossed bugs 3104 and the "not found ones" this had been yet reported but not reachable.

__The three bugs are (were for the first) :__

!! 1- Report with no author
The registering of a "report a bug" was not always getting the author name. So, the report was, till ten days ago (diagnostic by chat and it seems repaired), treated as a not registered user (or logged in user ) writing.

!!!The consequences are :
# No way to access them (no ticket displayed) and no access if found for the real author. Nota : if you have the ticket number (got from chat when submitted ) you can access it reacting the http query for this ticket.

# no way to manage them by the registered author

I have between ten and twenty report lost by this way.
And because of the second bug I can't find them back (just those submitted while I was chatting because the ticked is displayed on the chat.

!! 2- Filter crash :
the reason is the use of the "IN()" SQL clause which is not accepted by MYSQL
It is impossible to check the list in a right manner

!!3- Crash on sort list
(click on column headers) for the same reason : use of "IN() clause into the SQL request

!Problems and solutions

!!Repair the request generation - all

!!Getback the management of his ticket to the real author

It is a lot of job and not fair to rewrite all the reports lost (generates doubletons).

The lonely solution seems to be that the author could submit to the manager (webmaster...) the list of the concerned reports (ticket number or title).

This needs to get a successful search (filter), implies that the 2d and 3td bug should be solved (I could not display an available list to find mines - I have sometimes made a local copy, so I have some dates, but at this dates or around I can't find my report, the list is always just a part of the full one)

!!Display the ticket number even the author is not known should be usefull

!!The mean of "any" in properties of report and display
Even this data means "any not defined" when you say "any" you mean actually : "only the marked - any - reports". So it is impossible without clicking individually all the checks "anyone" of this criteria.
The solution can be either :
*on the filter a button : select all
*a data for filter names "anyone"
*both

- "select all" allow to unselect someones after
- "anyone" makes a more simple query allowing to forgot the criteria


__Without these solutions it is either awful or impossible to manage his "reports a bug"
__

Trebly - 04/28/2010 - 3h.07 Paris

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

On Tiki22 the page won’t save (Error 500) if you enter more than 200 characters (white space included).

That wasn’t the case previously (19, 20... 21) can’t tell for sure but I use a lot Description of Wiki page as Meta Tags for SEO so I never seen it before.

Related to https://dev.tiki.org/item276-Multilingual-Meta-Keywords-and-Meta-Description-and-increase-255-characters-limit

After applying a profile in 20.x, plenty of ugly error message notices are shown, regarding inability to create plenty of cache files:

Things like:
{QUOTE()} Error
Cache file temp/cache/module8756ab3c25fd45a0a55957e6d7bb1f16 is not writable
{QUOTE}

Very bad image for any one testing a brand new tiki site, and clicking for instance at any of the featured profiles.

When trying to Upload Translations using a Custom Translations file I got the following (tested on Mac and Windows).

Error
Invalid file type (expected file type: php)

when attempting to see this url ( [https://doc.tiki.org/tiki-index_p.php?page=Tiki26]), either through the "whats new wizard" ([http://localhost/tiki26/tiki-wizard_admin.php?&stepNr=7&url=tiki-index.php%3Fpage%3DHomePage&use-changes-wizard=1]) or directly in a new browser tab, I got this message:

{CODE()}
Too late to modify headers. Headers already sent by output_headers() called at [/home/tiki-doc/public_html/temp/templates_c/en_social^ea0943f75a262d8be544059ae17e04e9602d1469_0.file.header.tpl.php:482])
{CODE}

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

A few minutes later, reloading the page, displayed the page properly.
Weird (I had never seen such a thing in all previous tiki versions).

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).

{syntax type="tiki" editor="plain"}
When there is an error, such as trying to go to a non-existent page, e.g. tiki-index.php?page=sadjklfjadklfjlkds

the error page has the header appearing below the error.

You need search to be turned on (problem does not occur in mysql search though).

With feature_search enabled errors produced from error.tpl etc end up with the header, modules etc being repeated inside the page under the error message.

This can be seen here: [http://demo.tiki.org/12x/made+up+page] {sign user="jonnybradley" datetime="2013-10-13T16:13:38+00:00"}

This is a side-effect of the change to using Smarty Inheritance in the tempting system and due to tiki-searchindex.tpl now using "{extends 'layout_view.tpl'}".


Should also happen with feature_search_fulltext but the logic's borked currently... will fix that once this is fixed.

When you save a page on Tiki.org it just reload the previous content.

After a few attempts (copy/paste edited content) it accept to save.

Update 2021-07-07:
Happened again editing was almost lost ! ?

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

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

When using a mathematical field I created several times in the past a field to calculate the age of someone using:
{CODE()}(round (div (sub (date) childrenBirthDate) 31536000 ) 1){CODE}

In Tiki 20.1 (from Git; no revision number found) it thrown an error:
~pp~Divide by zero on "0"~/pp~

{CODE()}(sub (date) childrenBirthDate){CODE}
is not throwing the error.

The error is coming from a test at "lib/core/Math/Formula/Function/Div.php".

Updated 04/04/2020 {sign user="Bsfez" datetime="2020-03-04T19:59:04+00:00"}
After upgrading to Tiki21 the workaround is not useable anymore.
It forbid the index rebuilt operation to complete and therefore the Tiki is broken.
See: https://dev.tiki.org/item7304-Change-in-condition-inside-a-calculation-field-breaks-rebuilt-index-operation-and-calculation

---
Update 20/05/2020 {sign user="Bsfez" datetime="2020-05-20T09:07:12+00:00"}
Found the culprit ! (and it is not directly related to calculation ?)
I have in this tracker an item list field that get info from another tracker so I need to use trackerrender to display the original value and not the value of the dropdown item.
__It is not used for any calculation, it is the employee ID__
To display it I use:
{CODE()}
{FORMAT(name="id")}{display name="tracker_field_timeworkEmployeeId" format="trackerrender" default=""}{FORMAT}
{CODE}
Used that way I got the error:
~pp~Divide by zero on "0" ~/pp~

If I change the format for:
{CODE()}
{FORMAT(name="id")}{display name="tracker_field_timeworkEmployeeId_text" default=""}{FORMAT}
{CODE}

The error is gone.

I have errors trying to access a file in a subfolder on dev.t.o on the file galleries.

Using the main link to open the folder Bug Report Image => bsfez I have errors.
Using the Tiki Explorer for the file galleries it worked.

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

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

---

Not the same issue but may be related, I couldn't set a plugin img after uploading and setting the plugin following the process using the dialog modal from the Help plugin. I also tested on Safari and Chrome.

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

I tested on Tiki19 using nextdev.
nextdev is using elfinder and it worked better but still I had to retry several times to get over an error after the upload (may be due to nextdev setup ?):
^Potential cross-site request forgery (CSRF) detected. Operation blocked. Reloading the page may help.^

https://nextdev.tiki.org/item6831-test-file-gallery
Not sure I can add 19.x to this ticket... In doubt I didn't.

Check the image which is supposed to be to the left of "Upgrade fix" on step7 of the installer

See https://www.evernote.com/shard/s37/sh/62198085-ac08-48a9-afb4-74752eeef887/43a9e4c3a493246765820b7836aa1070

How come I cannot disable the right module? I tried the same for left column and it also does not work

Please first check if problem exist on new tiki 13 and then on nextdoc as it could be due to some customization? or not?