Category: Error
error message, broken, etc
A bug is something which doesn't work like it should. It is an obvious error.
This category was probably used as a fallback for bugs which did not fit other Bug subcategories before the general Bug category was created.
Show subcategories objects
A bug is something which doesn't work like it should. It is an obvious error.
This category was probably used as a fallback for bugs which did not fit other Bug subcategories before the general Bug category was created.
| Name | Type |
|---|---|
| Plugins broken in Blog in 1.9.2 | tracker item |
|
Plugins broken in Blog inn 1.9.2
When putting a plugin onto a blog post which requires parameters, the parameters are not passed in or are passed in as an &. This happens when the => syntax is used, or quotes are used around the parameter. These are otherwise fine when in a wiki page. Most plugins appear to be affected on my installation - which was an upgrade from 1.8.4 to 1.9.2. They render okay when viewing individual posts, or previewing, which leads me to beleive it is in tiki-blog_view.php somewhere. After diffing the files, the largest visible change was the addition of categories into the blog, this is however not affected by turning off the feature in admin. I am putting this high on my own priority list as I cannot upgrade my live site to 1.9.2 (although it has had some secuirty fixes put on it) until this is solved as I do not want to break my history of blog posts using plugins. Perhaps it is worth a shot on this site or tikiwiki.org to see if plugins are affected here as well with that. |
tracker item |
|
pluginSharethis breaks maps
When pluginSharethis is used on a page, the following maps are blank 1) map displayed using pluginMap 2) map displayed using showMap option with pluginTrackerlist or pluginTrackerfilter 3) location fields displayed with pluginTrackerlist or pluginTrackerfilter This has been demonstrated on a show.tiki instance |
tracker item |
|
PluginSplit: uses % instead of px width
Split plugin is not working when we try to set fixed pixel width for columns. They are percentages instead, as you can see here: http://themes.tikiwiki.org/tiki-index.php?page=TestPluginSplit Also, there is some info here & a patch: http://tikiwiki.org/PluginSplit |
tracker item |
|
PluginTogether fails due to warning of edition conflict
Wasn't that fixed already in 15.x+? |
tracker item |
|
pluginTracker url parameter does not work
Say I use the plugin in on the page "Edit Publisher&itemId=1159". {CODE()}{tracker trackerId="18" url="Publishers" wiki="Edit Publisher Template"}{CODE} I asked it to go to the page "Publishers" after being submitted. Instead it goes to tiki-index.php?page=Edit+Publisher&itemId=1159&ok=y&iTRACKER=1#wikiplugin_tracker1 ----------------------- In the tiki show instance, I have created a tracker for colors and pages for displaying and editing the items. # Go to http://hrsms-11204-5079.show.tikiwiki.org/tiki-index.php?page=Colors #Click on "bleu". You will be taken to Edit+Color&itemId=2 #View the source. Note the url parameter is set to "Colors" #Change the spelling to "blue" and hit save. You will be directed to Edit+Color&itemId=2&ok=y&iTRACKER=1#wikiplugin_tracker1. The edit fields will no longer be displayed. #Click on the button provided (my workaround) to go back to the "Colors" page, where you will see the change did take effect. |
tracker item |
|
PluginWantedPages displays stray non-breaking space HTML entities in header
The ((doc:PluginWantedPages|WANTEDPAGES)) plugin will display literal ~amp~nbsp; HTML entities in the header of the display table. |
tracker item |
|
WYSIWYG plugin fails to open if no parameter for page (regression from version 17)
The WYSIWYG plugin no longer works starting from Tiki 17 if there is no page URL parameter, for example on the homepage. I wrote in the wiki page the usual way to have the plugin to show up: {CODE()} {WYSIWYG()} {WYSIWYG} {CODE} I save the wiki page. When one clicks the "Edit" button at the bottom right corner of the plugin, a JavaScript error occurs: {QUOTE()}Uncaught TypeError: Cannot read property 'type' of null at HTMLButtonElement.<anonymous> (tiki-ckeditor.js:188) at HTMLButtonElement.dispatch (jquery.js:5206) at HTMLButtonElement.elemData.handle (jquery.js:5014){QUOTE} jqueryTiki.current_object is null. If the homepage is accessed using relative URL tiki-index.php, the issue occurs. If the homepage is accessed using relative URL tiki-index.php?page=HomePage, the issue does not occur. Tiki 16 does not have this issue. |
tracker item |
|
Poll, even with permission anonymous can't vote
Even if poll global permissions says anonymous can vote, they are not allowed to vote. tested on next.tiki.org |
tracker item |
|
Polls can be seen by anonymous even though they are not allowed to vote.
Anonymous users can see can view polls even though they don't have tiki_p_vote_poll These files need to be checked: tiki-old_polls.php tiki-poll_results.php tiki-poll_form.php Setting that anon can vote in polls needs to be cheked too. tiki-admin.php?page=polls Sorry not to have a clearer bug report. Short version is that permissions for polls don't work as expected in 1.9.0 Please also see tracker #278 |
tracker item |
|
Polls: handling of users that have already voted
1- If you have voted, it should show you results instead of offering to vote. Even if the system doesn't record your second vote, it still offers the voting interface. 2- tiki-admin.php?page=polls If "Allow Anonymous Poll Voting:" (feature_poll_anonymous) is checked and tiki_p_vote_poll is given to anonymous (not sure if this matters), anonymous voters can vote multiple times, without having to clear their cookies. |
tracker item |
|
pop port appears hardcoded to 110
i'm still tracking this down and i hope someone might have a ready answer since i'm new to tikiwiki. i created a mail-in account to use Google's Gmail for POP since our IT department does not support POP from Exchange. the Gmail account uses port 995 for POP connections rather than the standard port 110. the account data was stored correctly in mySQL database but when tikiwiki attempts to read mail it fails citing a timeout on the gmail IP and port 110 as shown below: PHP (5.2.3) ERROR (E_WARNING): File: Socket.php Line: 136 Type: fsockopen() [function.fsockopen]: unable to connect to 209.85.133.109:110 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ) i have not yet found where the call to lib\pear\Net\Socket.php is made and will hopefully update this later with the information. |
tracker item |
|
Possible bug at creating base Tiki DB tables
The basic Tiki DB initalization IMHO contains an error. Maybe this is due to a change introduced later that made the INSERT incompatible to the CREATE. /db/tiki.sql contains this at lines 2867-2878: {CODE(Colors="Tiki")} DROP TABLE IF EXISTS `users_usergroups`; CREATE TABLE `users_usergroups` ( `userId` int(8) NOT NULL default '0', `groupName` varchar(255) NOT NULL default '', `created` int(14) default NULL, `expire` int(14) default NULL, PRIMARY KEY (`userId`,`groupName`(225)) ) ENGINE=MyISAM; INSERT INTO users_groups (`groupName`,`groupDesc`) VALUES ('Anonymous','Public users not logged'); INSERT INTO users_groups (`groupName`,`groupDesc`) VALUES ('Registered','Users logged into the system'); INSERT INTO users_groups (`groupName`,`groupDesc`) VALUES ('Admins','Administrator and accounts managers.'); {CODE} This should not work. Maybe the resulting error is just ignored? Values are entered into the non-existent column "groupDesc"... |
tracker item |
|
Possibly wrong help text for facets
(or, alternatively, wrong user input method) The admin UI for the facet feature describes, that the user shall enter a comma-separated list of categories, yet a multiselection window is presented. Interestingly, in /lib/prefs/category, where this help string comes from, is text input specified ?! If that would be presented, the text would be right, but somehow it is not... {CODE(Colors="Tiki")} 'category_custom_facets' => [ 'name' => tr('Generate custom facets from categories'), 'description' => tr('Comma-separated list of category IDs.'), 'type' => 'text', 'size' => 15, 'filter' => 'int', 'separator' => ',', 'default' => '', 'profile_reference' => 'category', ], {CODE} cf. screenshot (attachment) |
tracker item |
|
Post to forum via pop3 mail does not decode encoded subject
Mail answers to forum posts do not get sorted to the correct thread when the mail subject is encoded due to non-ascii characters. There is a new thread started. Original subject in forum: HIPP Biopute mit Möhrchen Subject in mail sent from tikiwiki: =?utf-8?q?HIPP_Biopute_mit_M=C3=B6hrchen?= Subject in mail sent to tikiwiki: Re: =?utf-8?q?HIPP_Biopute_mit_M=C3=B6hrchen?= Subject in forum after mail retrieval: =?utf-8?q?HIPP_Biopute_mit_M=C3=B6hrchen?= Tikiwiki does not decode the encoded mail subject. I see the same behaviour, when the mail subject is encoded in iso885-15 insted of utf8. |
tracker item |
|
PostGres errors on attempted post/insert of long emails to forums with email-to-forum enabled
Postgres returns row length error to tiki-view_forum.php upon attempt to write data from long e-mail to a forum with email-to-forum functionality enabled. |
tracker item |
|
postgres7 error: operator does not exist
Hi all! I am building a tiki in italian, english, german, french and spanish (not published yet). My development environment: - XAMPP 2.5 for Windows - Apache/2.2.8 (Win32) DAV/2 mod_ssl/2.2.8 OpenSSL/0.9.8g mod_autoindex_color PHP/5.2.5 - PHP Version 5.2.5 - DBMS Postgres 8.3.1 (running remotely on an Ubuntu box) tikiwiki version: 1.9.10.1 I'm having a problem using the i18n feature: if I activate "Multilingual" and I select "Italiano (it)", and then I try to update my homepage, I get the following error message: --- Warning: postgres7 error: ERROR: operator does not exist: bigint = character varying LINE 1: ...cts" as t2 LEFT JOIN "tiki_pages" p ON p."page_id"=t2."objId... ^ HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts. in query: select t2."objId", t2."lang", p."pageName"as "objName" from "tiki_translated_objects" as t1, "tiki_translated_objects" as t2 LEFT JOIN "tiki_pages" p ON p."page_id"=t2."objId" where t1."traId"=t2."traId" and t2."objId"!= t1."objId" and t1."type"=? and t1."objId"=? in C:\xampp\htdocs\tikiwiki\lib\tikidblib.php on line 134 Context: File tiki-index.php Url tiki-index.php Query: select t2."objId", t2."lang", p."pageName"as "objName" from "tiki_translated_objects" as t1, "tiki_translated_objects" as t2 LEFT JOIN "tiki_pages" p ON p."page_id"=t2."objId" where t1."traId"=t2."traId" and t2."objId"!= t1."objId" and t1."type"=? and t1."objId"=? Values: 0 wiki page 1 2 Message: Error Message ERROR: operator does not exist: bigint = character varying LINE 1: ...cts" as t2 LEFT JOIN "tiki_pages" p ON p."page_id"=t2."objId... ^ HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts. --- The some operation, running on a MySql5 based installation, doesn't happen. Which is my fault ? What another thing I must check and where ? Thanks in advance ! Giuseppe |
tracker item |
|
PostgreSQL - cannot present user files
When user files area is empty it causes error displaying the content. My tikiwiki is 1.9.1 with php5 and Postgresql 8.x For more details see --> https://sourceforge.net/tracker/index.php?func=detail&aid=1283628&group_id=64258&atid=506846 |
tracker item |
|
PostgreSQL - cannot upload user avatar
when downloading image/jpeg type of user avatar it fails due to problem in execution of SQL query. It seems that binary uploads that for sure contains special characters destroys the SQL statament to be queries. My TikiWiki is 1.9.1 configured with Postgersql 8.x For more info see --> https://sourceforge.net/tracker/index.php?func=detail&aid=1283624&group_id=64258&atid=506846 |
tracker item |
|
Potential cross-site request forgery (CSRF) detected. Operation blocked. Required headers are missing.
Hello everyone. I'm encountering the following issue. I found some tickets regarding this message but nothing seems to be related to this specific issue. Is this a bug or something from my side? Any clues? When I'm trying to access the page `/tiki-syslog.php` I'm getting this error message __Error message: __ -+Potential cross-site request forgery (CSRF) detected. Operation blocked. Required headers are missing.+- __Log output:__ -+Request to /tiki-syslog.php failed CSRF check. Requesting site could not be identified because HTTP_ORIGIN and HTTP_REFERER were empty.+- __Server Info__ * Release: Debian GNU/Linux 10 (buster) * Database Version: 10.3.23-MariaDB-0+deb10u1 * PHP version: 7.3.19-1 Thank you very much. |
tracker item |
|
Pref. Force users to fill tracker information brakes Tiki (seen in 16)
The preference "Force users to fill tracker information" in the tiki admin secton "login" broke a newly installed Tiki 16 (from svn) shortly after installation, at the moment of activation. I just have had started the configuration. Trackers was not yet active, so not User Tracker aswell. I will activate Trackers and User Tracker prior to activate the preference in the show instance. This is the error message I had after activation, representing a full WSOD for logged in admin (Please mind: the anonymous user still could see the website): {CODE()} Fatal error: Call to a member function getUserField() on boolean in /www/htdocs/.../tiki/.../currentroot/lib/setup/tracker_force_fill.php on line 18 {CODE} __Update:__ When I first setup Tacker and User Tracker in the show instance, the "Force users to fill tracker information" continuously forces users to again and again create a new tracker item, even when multiple exist. Try now with autouser field. __Update2:__ User field with auto assign helped, but Tracker is creating multiple items, when updating info. Obviously I forgot to set "only one tem per user"! ... __Update3:__ It is NOT working correctly. When updating user data (in tracker) from the 'my Account' -> 'my info' -> 'Additional Information' tab, multiple Tracker items are created. |
tracker item |
|
Preference metatag_imagetitle is not defined error on admin meta-tags
On a Tiki23 when checking tiki-admin.php?page=metatags I see the following error: "Preference metatag_imagetitle is not defined" and "Error" in the value field. Visible also on dev: https://dev.tiki.org/tiki-admin.php?page=metatags |
tracker item |
|
Prefix doubled when tracker item saved and wiki-page-tracker-field uses custom namespace
Prefix doubled when tracker item saved and wiki-page-tracker-field uses custom namespace --- human error, not tiki error. The field to get the page name from was a mathematical calculation field, and I had written there the prefix aswell, not only in the params of the wiki-page tracker field. |
tracker item |
|
preg_quote(): Argument #1 ($str) must be of type string, Math_Formula_Element given
I just filed this bug report: https://dev.tiki.org/item8492-Error-on-tiki-index_p-php-Too-late-to-modify-headers-error-shown-in-wizard-for-tiki-admins-in-new-installs as user "xavi", thorugh ((File a bug)) wiki page. After hitting save, I saw this error message (below) where the wiki page should have provided feedback to the user (plugin tracker feedback). {CODE()} preg_quote(): Argument #1 ($str) must be of type string, Math_Formula_Element given {CODE} {img fileId="2116" thumb="box"} I did set the importance to 9 because it's very discouraging to new devs or users to attempt to report bugs at the bug tracker and have the sensation that their time and report might be lost (it triggers the sensation the tiki can be unreliable - dangerous effect to our comunity) |
tracker item |
|
pretty tracker demo cannot be applied
Pretty_Tracker_Demo cannot be applied any more wihtin the admin's profiles. Instead of loading the profile, a new pages opens with the link "jdoe@company.commsmith@company.com" and the pages keeps loading. Perhaps it is due to the new release 5.2. |
tracker item |
Most plugins appear to be affected on my installation - which was an upgrade from 1.8.4 to 1.9.2.
They render okay when viewing individual posts, or previewing, which leads me to beleive it is in tiki-blog_view.php somewhere.
After diffing the files, the largest visible change was the addition of categories into the blog, this is however not affected by turning off the feature in admin.
I am putting this high on my own priority list as I cannot upgrade my live site to 1.9.2 (although it has had some secuirty fixes put on it) until this is solved as I do not want to break my history of blog posts using plugins.
Perhaps it is worth a shot on this site or tikiwiki.org to see if plugins are affected here as well with that.