Category: 12.x

Search index rebuild fails. I've tracked it down to the file and it fails at php:s function rename. Where the code tries to rename the index-new folders content to the current index. This used to work in version 11. Possible issue with file-permission systems, php is not allowed to access the folders. The file in question is searchlib-unified.php and rows close to 250. rename($index_location, $swapName)) this fails.
I'm not sure if this is a problem on Linux servers.

Settings:
Windows server 2008 R2 Standard
MySQL server 5.6
PHP 5.4.19

Workarounds:
1: Comment out the rename and delete lines from code.
2:
Build a batch file to do your file transfer.
OR
Move the files manually if you don't have to build indexes very often
OR
build indexes with previous versions and move the files
OR
Fix the code by making a recursive loop that moves the files from the folder to another folder.

We have this for wiki pages. Maybe add to tiki-admin_notifications.php?

When entering tiki-login_scr.php, only the login box can be seen. There is no "Login box", typically located in the top right corner

1) Try a login with an invalid user
The error is shown "inline" with the login box.
The "Login box" also appears at the top, which it shouldn't

2) Try a login with an invalid password
The error is show in the error screen,which is a completely new screen.

Should be, for all errors
1) Errors are reported "inline" with the log-in dialog
2) The "Login box" should not be shown on the log-in screen.

---
r50668 fixes #1. All errors are now display "inline" with the login dialog on tiki-login.php

#2 is still pending.

Before Composer (until Tiki10), if you try to run Tiki with a too old version of PHP, you get a clear warning. Now, with Composer, it's not so clear (you get the version warning of Composer instead of Tiki)

Note that the command line version of PHP may be different than the web version.
Command-Line PHP version: PHP 5.3 is needed Composer.
Web version of PHP: Tiki12 needs 5.3, Tiki13 will need 5.5

So perhaps for Tiki 13, it will be OK to have PHP 5.3 requirement on CLI, but 5.5 in web?

So for now, let's add a PHP CLI version check on sh setup.sh before running Composer.

Please see:
http://tiki.org/tiki-view_forum_thread.php?comments_parentId=48901

There are issues at: ((Unified Index with MySQL Full Text Search))

Also, there should be warnings when site hits limitations of MySQL, that the admin needs to change to Zend_Lucene or ElasticSearch. Ideally, these warnings would come before hitting the limitations but this may not be easy to do.

Nelson (note to self): To make this bug actionable: these are the following actions. Many other things like excluding plugins by default are already done.

1) Make the logging use a different log file when triggered from the console vs the web (this will avoid any file perm problem).

2) Provide remarks box about including plugins in the admin panel.

3) Provide remarks box explaining that MySQL Full text search will only search first x characters of content (might affect large files in the file gallery for e.g.) - this is handled in item4641 already

The maketoc plugin displays multiple TOC's (one from each Language displayed) on the left hand side when the international "all languages" feature is used.

{img fileId="752"}

http://dev.tiki.org/tiki-searchindex.php?find=maketoc


{flash type="url" movie="display522" width="846" height="711"}

On a wiki page, the "translate" and "manage translation" links under the little globe appear if 1. The person has permission to edit that page, but at the same time have no permissions to create new pages or edit other pages.

The links do not appear if the person does not have write access to the wiki page.


What should happen:

The "translate" and "manage translations" buttons should only appear if the user has permissions to create a translation, rather than edit the specific page they are on.

The issue I have come across is that the nav buttons are appearing when the page can not be edited, but the opposite problem is also likely (although I have not tested it) that a translation could be desired, on a page thats write permissions have been suspended.

This issue has also caused several translation & error pages to become crawled by bots and indexed in search engines. I will be proposing some new robots.txt rules to help prevent this in another ticket (to keep it all together with other suggestions)

Hope this is of interest for someone to tackle.

{flash type="url" movie="display662" width="657" height="508"}

The feeds:

Blogs, File Galleries & Forums do not create SEF URL's, when the option is enabled.

After successfully trying many-to-many relationships in trackers using these instructions: https://doc.tiki.org/Relations+Tracker+Field I tried the same in 12.x and it does not work.

It is impossible to select a related object from another tracker because the select box remains empty even though the other tracker holds items.

I am not sure whether this is due to a regression or simply outdated documentation.

Let me know if I can be helpful in any way.

Thanks!

Maps are displayed in front of the Draw editor, making it difficult to use.

{flash type="url" movie="display637" width="645" height="787"}

__Looks like this only happens for menus that have got the "Wiki parse" option set__

When a menu is exported the resultant CSV file contains html (and other end of line characters?) for the Name field

Particular difficulties occur when the option to wiki parse the label is set 'on' ie the Name field may have something like:

~np~Home {img src="img/icons/home.gif" height="12" width="12" alt="Image"}~/np~

so that a small icon is included - but when this is exported it appears as:

~np~Home <img src="img/icons/home.gif" height="12" width="12" alt="Image" class="regImage pluginImg" />~/np~

with additional spurious end of line characters that do not show up in the Excel spreadsheet

Similar end of line characters appear on all simple text entries in the Name field.

The difficulty arises when you want to reimport previously exported data and this then causes corruption

It looks like the parsed output of the Name field may be being exported instead of the simple stored value ?

Menu Wiki 'List Pages' and 'Create a Wiki Page' are two tabs on one page.

After visiting 'Create a Wiki Page' the focus stays on this tab when visiting 'List Pages'. Average expectation is assumed to refocus to the new tab.

We are getting a lot spam on current space and sooner or later, we need to move.

Also, the auto-responders are stuck on tikiwiki.org instead of tiki.org When we migrate, we can address this.

The old server is being shut down shortly.

See: ((tw:Community Mail Server))

When uploading files in the file gallery (XXX.JPG) with uppercase filenames they will be detected as application/octet-stream (XAMPP on Windows 7).
Instead they should be recognized as jpeg.

Proposed patch (i.e. convert extension to lower case before testing for mime type).
~pp~
--- mimelib-ori.php 2013-12-07 13:07:10.000000000 +0100
+++ mimelib.php 2013-12-07 13:08:07.000000000 +0100
@@ -101,7 +101,7 @@
global $mimetypes; include_once('lib/mime/mimetypes.php');

if (isset($mimetypes)) {
- $ext = $this->get_extension($filename);
+ $ext = strtolower($this->get_extension($filename));
$mimetype = isset($mimetypes[$ext]) ? $mimetypes[$ext] : '';

if (!empty($mimetype)) {
~/pp~

current mindmap module is very old and doesn't support other double byte languages.
does anyone have alternative to replace this module or enhance this module and include it into future Tiki release?

while building a website, mindmap or detail sitemap is an important tools to track all the pages.

Missing (12.x) or wrong (13.x) feedback to comment poster when Comments Moderation is on and post is not shown

However, in the show.t.o instance for 12.x, I couldn't get the same behavior I saw a few weeks in a 12.x in localhost.

Current issues reproduced in the show.t.o 12.x instance:
Adding a comment as anon to the homepage (with comments moderation enabled):
http://xavi-9794-5310.show.tikiwiki.org/tiki-index.php

{CODE()}
Notice: Array to string conversion in /var/www/xavi-9794-5310/vendor/bombayworks/zendframework1/library/Zend/Filter/Alnum.php on line 144
{CODE}

{CODE()}
Your comment was posted.

No object information provided.
{CODE}

In 13.x I saw the same output (without the initial array notice):
{CODE()}
Your comment was posted.

No object information provided.
{CODE}

This seems to be an error message:
{QUOTE()}
__No object information provided__
{QUOTE}

And "Your comment was posted." is a missleading information, since the comment is not visible yet (until moderation happens). So a better message could be shown in this case, something like:

"__Your comment was posted but is pending moderation, and until approval, it will not be shown__"

When viewing the page again, it says:
"There are no comments at this time."

when you would expect to see something like:

"__There are some comments hidden pending moderation__"
---
^ __And last, as registered users, there is no feedback of what happens in that tiki site that their comments are gone after clicking at "post".__ ^

There seem to be some issue with MySQL 5.7 and Tiki.

For instance, mysql table tiki_payment_requests is not created due to issue with date with __no null__ but with a missing default value):

{CODE(colors="sql")}
DROP TABLE IF EXISTS `tiki_payment_requests`;
CREATE TABLE `tiki_payment_requests` (
`paymentRequestId` INT NOT NULL AUTO_INCREMENT,
`amount` DECIMAL(7,2) NOT NULL,
`amount_paid` DECIMAL(7,2) NOT NULL DEFAULT 0.0,
`currency` CHAR(3) NOT NULL,
`request_date` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
`due_date` TIMESTAMP NOT NULL,
`authorized_until` TIMESTAMP NULL,
`cancel_date` TIMESTAMP NULL,
`description` VARCHAR(100) NOT NULL,
`actions` TEXT,
`detail` TEXT,
`userId` int(8),
PRIMARY KEY( `paymentRequestId` )
) ENGINE=MyISAM;
{CODE}

{CODE(colors="sql")}
#1067 - Invalid default value for 'due_date'
{CODE}

One could think in migrating to mariadb, but it seems that mariadb and mysql started to diverge before mysql 5.7.
Taken from: https://seravo.fi/2015/10-reasons-to-migrate-to-mariadb-if-still-using-mysql
{QUOTE()}
Migration might become difficult after 2015
In versions MariaDB 10.0 and MySQL 5.6 the forks have already started to diverge somewhat but most likely users can still just upgrade from 5.6 to 10.0 without problems. The compatibility between 5.7 and 10.1 in the future is unknown, so the ideal time to migrate is now while it is still hassle-free. If binary incompatibilities arise in the future, database admins can always still migrate their data by dumping it and importing it in the new database.

With the above in mind, MariaDB is clearly our preferred option.

One of our customers once expressed their interest in migrating from MySQL to MariaDB and wanted us to confirm whether MariaDB is bug-free. Tragically we had to disappoint them with a negative answer. However we did assure them that the most important things are done correctly in MariaDB making it certainly worth migrating to.
{QUOTE}

File /templates/tiki-upload_file.tpl
row 284

{CODE(wrap="0" colors="smarty")}<label for="filetype">File Type:</label>{CODE}

Translation tag is missing. Should be:

{CODE(wrap="0" colors="smarty")}<label for="filetype">{tr}File Type:{/tr}</label>{CODE}

Mobile display is broken in trunk. Example:
https://nextdev.tiki.org/elFinder

{syntax type="tiki" editor="plain"}
Using mobile mode, from a PC with Chrome (on GNU/Linux, in case it matters).

I clicked on "Switch to mobile site" in nextdev.tiki.org, and then when you go to "Admin home > Look & Feel", the theme style shown there is "abse" and not fivealive, so that if you save any setting there in L&F, you are switching the theme for the non-mobile mode (and you will not notice since you as admin are still in mobile mode).

current Slideshow feature doesn't really support mobile browser, there is a workaround to set mobile browser to request desktop contents, but the navigation and screen layout not really fit to mobile nature.

slideshow is nice feature in desktop, but more people is using mobile to show the contents, to get the feature work in mobile would be helpful.

can we have a enhanced version of slideshow to support mobile?

For example I have specified a prefix for all of my pages so I can have structures like
STR1_pageName alias pageName
-STR1_Another alias Another
STR2_pageName alias pageName
-STR2_Another alias Another

The issue comes when I want to have consistent naming for my left navigation and on breadcrumbs module. Structures are displayed correctly on the left navigation every single item has that alias. But on the breadcrumbs module the current page you are on is displayed by pages realname. For example pageName >> STR1_Another
I've received complaints from clients that this behaviour is confusing , and I've yet to find the solution to this issue. This may somewhat be related to ((https://dev.tiki.org/item4891|this)) issue. If someone has ideas how to overcome this issue I could try to fix it.

Module months_links is expected to show links to the months in the last year where posts occurred, but also display a link to the previous years, so that the user can click to the previous year to list the months that hold posts, etc.

The user expected to be able to list all months where there were posts, from the previous years, but it only display posts from the last 12 months.

The rows param by default gets the value 10 (like month october, our current month by the time of this writing)
Increasing the value shows more links (from previous years). However, it seems that Value max="-1" (show all posts, with no max limit) doesn't fetch them all.