Name | Type |
---|---|
"Source" button in wiki page should have its own permission - not depend on tiki_p_view_history | tracker item |
1.9.x: mysql error: tikilog iattempts to nsert new actions in tiki_logs as logId=0, on mysql 4.0.x
Using 1.9.7 or 1.9.cvs from mid july 2007, and mysql 4.0.x When clearing cache through "Admin > System Admin", for instance (tiki-admin_system.php?do=templates_c), I hit a warning mysql error: {CODE(wrap=>1)} Warning: mysql error: Duplicate entry '0' for key 1 in query: insert into `tiki_logs` (`logtype`,`logmessage`,`loguser`,`logip`,`logclient`,`logtime`) values (?,?,?,?,?,?) in /home/virtual/site21/fst/var/www/html/tikiwiki/lib/tikidblib.php on line 134 {CODE} Looking at tikilog table in tiki db, I see: ^0 system erased templates_c content Xavi 161.116.71.36 Mozilla/5.0 (Windows; U; Windows NT 5.0; ca; rv:1.... 1186492878^ When I delete this record from the db, then Tiki can delete templates once (through "Admin > System Admin"), but if I attempt to do it a second time, I get the same mysql error message. It looks as if those actions are not saved with the right logId number, but to logId=0 This happens to one of the tikis I admin at: http://precarios.org/tikiwiki/ |
tracker item |
Koichi
Contributors |
tracker item |
database queries counter: remove until it is fixed
In the bottom bar of Tiki sites if activated there is some "debug" information. Notably: {img src=images/code.png}%%% {CODE()} [ xx database queries used ] {CODE} The SQL counter report is incorrect and reports higher number. Since this is making Tiki look bad for no good reason I am removing until it's fixed. Please see: http://sourceforge.net/mailarchive/message.php?msg_id=469E4D13.8010609%40gmail.com |
tracker item |
jonnybradley
Contributors |
tracker item |
2 unused filelds for Tiki articles
+ALTER TABLE `tiki_articles` ADD `bibliographical_references` TEXT DEFAULT NULL AFTER `created` , ADD `resume` TEXT DEFAULT NULL AFTER `bibliographical_references`; +ALTER TABLE `tiki_submissions` ADD `bibliographical_references` TEXT DEFAULT NULL AFTER `created` , ADD `resume` TEXT DEFAULT NULL AFTER `bibliographical_references`; fhcorrea added them and confirmed that won't be used. |
tracker item |
Multilingual Meta Keywords and Meta Description (and increase 255 characters limit)
Please increase the limit and make it multilingual |
tracker item |
changi67
Contributors |
tracker item |
DB update SQL statement
When upgrade from version 2.2 to 3.9, I received one database error. The error is related to this statement: INSERT INTO `tiki_menu_options` (`optionId`, `menuId`, `type`, `name`, `ur The SQL statement failed to complete because the optionId 197 already exist. |
tracker item |
Search within a category
Categories are amazing for a large site. It makes it easier to manage. Next step is to add an option in search which can be filtered by category. |
tracker item |
database charset issue
we're having a charset issue when displaying tikiwiki pages. The pages themselves are correctly sent as UTF-8: data coming from the localization files is fine. However, data coming from the tikiwiki database is latin1, and those characters are shown as ? in a lozenge. The database is encoded as UTF-8, but the default encoding for MySQL, set at build-time, is Latin1. So it appears that there is an implicit conversion done when getting/putting data to and from the DB. Data received is converted from UTF-8 to Latin1, and data sent is considered to be Latin1 (though it is UTF-8), and converted again: the end result in the database is corrupted again. It seems that this happens because tikiwiki uses the default charset encoding from the MySQL engine. On another system, with the same MySQL version, but built to use UTF-8 as default (--with-charset=utf-8), there is no problem. It should probably use the "SET NAMES utf8" command to set the charset encoding, as described there: http://dev.mysql.com/doc/refman/5.0/en/set-option.html Software used is: Solaris 9 Apache 2.2.3 PHP 4.4.4 MySQL 5.0.24a |
tracker item |
add automatic sequential id to tracker
add automatic sequential id to tracker or get read access to internal id |
tracker item |
Add SQL/DB Link Tracker field type | tracker item |
add trackers-quicktags to SQL-scripts
Textarea in Trackers checks for quicktags from the "tracker"-category - those are not yet in the db. |
tracker item |
Admin User gets many php warnings
If admin user get lots of php warnings. Eventually page will build. Other warnings depending on various DB requests. Not a cookie problem - deleted cookies. Not browser specific. Typical warnings encountered. Most everything: Notice: Only variable references should be returned by reference in lib/adodb/adodb.inc.php on line 2797 Notice: Only variable references should be returned by reference in lib/adodb/adodb.inc.php on line 2802 Admin Menu: Warning: usort(): Invalid comparison function. in lib/tikilib.php on line 1714 Notice: Only variable references should be returned by reference in /home/vamasono/public_html/cms/lib/pear/PEAR.php on line 425 Admin Groups: Warning: Cannot modify header information - headers already sent by (output started at lib/adodb/adodb.inc.php:2797) in tiki-admingroups.php on line 254 Installed full v1.9.1 to a DB with 1.9.0. Ran 1.9.0->1.9.1. |
tracker item |
Adodb script errors on a new installation when working with groups
On a new installation of TikiWiki 1.9.4 (installed via Fantastico on a LAMP server), I get the following error: Notice: Only variable references should be returned by reference in /home/hocho/public_html/wiki/tikiwiki/lib/adodb/adodb.inc.php on line 834 Warning: Cannot modify header information - headers already sent by (output started at /home/hocho/public_html/wiki/tikiwiki/lib/adodb/adodb.inc.php:834) in /home/hocho/public_html/wiki/tikiwiki/tiki-adminusers.php on line 414 All I did was create a new group and try to assign the group to a new user. I also don't know why it is using ADOdb when I am using MySQL. All other functionality of TikiWiki seems fine. |
tracker item |
After upgrade 4.1->5.0 - Errors : 01 - Users maangement table :.tiki_trk_1 missing
Hello, As I told about, after upgrading from 4.2 (I am testing from 4.3) many errors occurs. This theated in a glabal way in id4377. After connecting as administrator if you submit "Users management" and try to modify a user preférences you will reach a __fatal error__ : Table "<your database>.tiki_trk_1" missing You will find joined the htm saved from "page source code" |
tracker item |
Call to ADONewConnection failing in plugins
I noticed that all the calls to the SQL plugin were killing my intranet website when going to version 4.x. Digging deeper I've narrowed it down to the ADONewConnection call of the wikiplugin_sql.php file. On that line of code PHP dies and I am left with a white page. I have tried playing with the call itself and even going to PDO which worked well enough to complete the page without dying, however I don't know enough about the PDO paradigm to actually retrieve data and rewriting the entire data retrieval strategy seems a bit extreme. Upon learning of dbreport, the only other plugin I know of to also use ADONewConnection plugin, is also failing I've decided this might be an issue in the plugin engine itself which is beyond me to resolve. One black box at a time is my general approach to things and this now relates to ADO and the plugin engine. I will continue to look at this issue, however assistance from bigger brains for PHP than my own would be a good thing. |
tracker item |
Categories feature enabled breaks database
3.0 Beta 2: After enabling the Categories feature through Admin -> Features, the following error occurs when adding or editing pages, articles, file galleries, and everything that needs to alter the database. (Names are arbitrary) An error occured in a database query! Context: File tiki-editpage.php Url tiki-editpage.php Query: insert into `tiki_objects`(`type`,`itemId`,`description`,`name`,`href`,`created`,`hits`,`comments_locked`) values(?,?,?,?,?,?,?,?) Values: 0 wiki page 1 sdf 2 sadfsa 3 sdf 4 tiki-index.php?page=sdf 5 1239375431 6 0 7 n Message: Unknown column 'comments_locked' in 'field list' Built query was probably: insert into `tiki_objects`(`type`,`itemId`,`description`,`name`,`href`,`created`,`hits`,`comments_locked`) values('wiki page','sdf','sadfsa','sdf','tiki-index.php'1239375431'page=sdf','0','n',?) |
tracker item |
Check if tiki.sql and tiki_xtoy.sql give the same results
This occured to me, while looking at the homework-perms remove issue... ... could be, that there is still something left... not sure though - reminder! |
tracker item |
check_feature fields missing from tables when upgrading fom 2.1 to 5
When running the upgrade using tiki-install.php to upgrade from 2.1 to 5 33 database errors are reported. Several of these are "Unknown column 'feature_check' in 'field list'" errors. During an upgrade, it is normal to have SQL failures resulting with Table already exists messages. 20091105_auth_tokens_tiki -- 2009-11-05 lphuberdeau CREATE TABLE `tiki_auth_tokens` ( `tokenId` INT NOT NULL AUTO_INCREMENT, `creation` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP, `timeout` INT NOT NULL DEFAULT 0, `token` CHAR(32), `entry` VARCHAR(50), `parameters` VARCHAR(255), `groups` VARCHAR(255), PRIMARY KEY( `tokenId` ), KEY `tiki_auth_tokens_token` (`token`) ) Table 'tiki_auth_tokens' already exists 20091123_dns_permission_tiki INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_dsn_query', 'Can execute arbitrary queries on a given DSN', 'admin', 'dsn', NULL, NULL) Unknown column 'feature_check' in 'field list' 20091124_fgal_backlink_tiki CREATE TABLE `tiki_file_backlinks` ( `fileId` int(14) NOT NULL, `objectId` int(12) NOT NULL, KEY `objectId` (`objectId`), KEY `fileId` (`fileId`) ); Table 'tiki_file_backlinks' already exists 20091204_tiki_p_view_newsletter_tiki INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_view_newsletter', 'Can view the archive of a newsletters', 'basic', 'newsletters', NULL, 'feature_newsletters') Unknown column 'feature_check' in 'field list' 20091214_perspective_management_tiki INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_perspective_edit', 'Can edit the perspective', 'admin', 'perspective', NULL, 'feature_perspective') Unknown column 'feature_check' in 'field list' INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_perspective_create', 'Can create a perspective', 'admin', 'perspective', NULL, 'feature_perspective') Unknown column 'feature_check' in 'field list' INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_perspective_admin', 'Can admin perspectives', 'admin', 'perspective', 'y', 'feature_perspective') Unknown column 'feature_check' in 'field list' 20100107_payment_tiki 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, `cancel_date` TIMESTAMP NULL, `description` VARCHAR(100) NOT NULL, `actions` TEXT, PRIMARY KEY( `paymentRequestId` ) ) Table 'tiki_payment_requests' already exists CREATE TABLE `tiki_payment_received` ( `paymentReceivedId` INT NOT NULL AUTO_INCREMENT, `paymentRequestId` INT NOT NULL, `payment_date` TIMESTAMP DEFAULT CURRENT_TIMESTAMP, `amount` DECIMAL(7,2), `type` VARCHAR(15), `details` TEXT, PRIMARY KEY(`paymentReceivedId`), KEY `payment_request_ix` (`paymentRequestId`) ) Table 'tiki_payment_received' already exists INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_payment_admin', 'Can administer payments', 'admin', 'payment', 'y', 'payment_feature') Unknown column 'feature_check' in 'field list' INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_payment_view', 'Can view payment requests and details', 'admin', 'payment', NULL, 'payment_feature') Unknown column 'feature_check' in 'field list' INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_payment_manual', 'Can enter manual payments', 'admin', 'payment', NULL, 'payment_feature') Unknown column 'feature_check' in 'field list' INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_payment_request', 'Can request a payment', 'admin', 'payment', NULL, 'payment_feature') Unknown column 'feature_check' in 'field list' 20100115_tiki_p_admin_modules_tiki INSERT INTO users_permissions (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES ('tiki_p_admin_modules', 'User can Administer Modules', 'registered', 'tiki', NULL, NULL) Unknown column 'feature_check' in 'field list' 20100128_tiki_p_blog_view_ref_tiki INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_blog_post_view_ref', 'Can view in module and feed the blog posts', 'basic', 'blogs', NULL, 'feature_blogs') Unknown column 'feature_check' in 'field list' INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_blog_view_ref', 'Can view in module and feed the blog', 'basic', 'blogs', NULL, 'feature_blogs') Unknown column 'feature_check' in 'field list' 20100203_payment_detail_tiki ALTER TABLE tiki_payment_requests ADD COLUMN detail TEXT Duplicate column name 'detail' 20100205_tiki_p_wiki_view_ref_tiki INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_wiki_view_ref', 'Can view in module and feed the wiki pages reference', 'basic', 'wiki', NULL, 'feature_wiki') Unknown column 'feature_check' in 'field list' 20100211_rss_items_tiki CREATE TABLE `tiki_rss_items` ( `rssItemId` INT NOT NULL AUTO_INCREMENT PRIMARY KEY, `rssId` INT NOT NULL, `guid` VARCHAR(255) NOT NULL, `ur 20100215_create_tiki_user_login_cookies_tiki CREATE TABLE `tiki_user_login_cookies` ( `userId` INT NOT NULL, `secret` CHAR(64) NOT NULL, `expiration` TIMESTAMP NOT NULL, PRIMARY KEY (`userId`, `secret`) ) ENGINE=MyISAM AUTO_INCREMENT=1 Table 'tiki_user_login_cookies' already exists 20100215_rating_permissions_tiki INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_rate_article', 'Can rate articles', 'basic', 'cms', NULL, 'feature_articles') Unknown column 'feature_check' in 'field list' 20100216_attributes_tiki CREATE TABLE `tiki_object_attributes` ( `attributeId` INT PRIMARY KEY AUTO_INCREMENT, `type` varchar(50) NOT NULL, `itemId` varchar(255) NOT NULL, `attribute` varchar(25) NOT NULL, `value` varchar(100), UNIQUE `item_attribute_uq` ( `type`, `itemId`, `attribute` ), KEY `attribute_lookup_ix` (`attribute`, `value`) ) Table 'tiki_object_attributes' already exists 20100217_rating_config_tiki CREATE TABLE `tiki_rating_configs` ( `ratingConfigId` INT PRIMARY KEY AUTO_INCREMENT, `name` VARCHAR(50) NOT NULL, `expiry` INT NOT NULL DEFAULT 3600, `formula` TEXT NOT NULL, `callbacks` TEXT ) Table 'tiki_rating_configs' already exists CREATE TABLE `tiki_rating_obtained` ( `ratingId` INT PRIMARY KEY AUTO_INCREMENT, `ratingConfigId` INT NOT NULL, `type` VARCHAR(50) NOT NULL, `object` INT NOT NULL, `expire` INT NOT NULL, `value` FLOAT NOT NULL, UNIQUE `tiki_obtained_rating_uq` (`type`, `object`, `ratingConfigId`) ) Table 'tiki_rating_obtained' already exists 20100218_auth_token_reuse_tiki ALTER TABLE `tiki_auth_tokens` ADD COLUMN `hits` INT NOT NULL DEFAULT 1 AFTER `timeout` Duplicate column name 'hits' 20100224_object_relations_tiki CREATE TABLE `tiki_object_relations` ( `relationId` INT PRIMARY KEY AUTO_INCREMENT, `relation` varchar(25) NOT NULL, `source_type` varchar(50) NOT NULL, `source_itemId` varchar(255) NOT NULL, `target_type` varchar(50) NOT NULL, `target_itemId` varchar(255) NOT NULL, KEY `relation_source_ix` (`source_type`, `source_itemId`), KEY `relation_target_ix` (`target_type`, `target_itemId`) ) Table 'tiki_object_relations' already exists 20100226_tracker_dump_perm_tiki INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_tracker_dump', 'Can save a CSV backup of entire trackers', 'admin', 'trackers', NULL, 'feature_trackers') Unknown column 'feature_check' in 'field list' 20100419_bigbluebutton_tiki INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_bigbluebutton_join', 'Can join a meeting', 'basic', 'bigbluebutton', NULL, 'bigbluebutton_feature') Unknown column 'feature_check' in 'field list' INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_bigbluebutton_moderate', 'Can moderate a meeting', 'admin', 'bigbluebutton', NULL, 'bigbluebutton_feature') Unknown column 'feature_check' in 'field list' INSERT INTO `users_permissions` (`permName`, `permDesc`, `level`, `type`, `admin`, `feature_check`) VALUES('tiki_p_bigbluebutton_create', 'Can create a meeting', 'admin', 'bigbluebutton', NULL, 'bigbluebutton_feature') Unknown column 'feature_check' in 'field list' If you think that the errors of a patch can be ignored, please check the checkbox associated to it before clicking on continue. |
tracker item |
Comments to Image Galleries cause failure in mod-since_last_visit_new.php causing site crash
When any user creates a comment for an image gallery all users with the since_last_visit_new module active will not be able to access the site. Instead they will receive this error message: Notice: Undefined index: list in /hsphere/local/home/stdiddl/breakingpaint.com/BP2/modules/mod-since_last_visit_new.php on line 87 {CODE(caption=Excerpt_from_line_86)} if (!isset($perm) || $userlib->user_has_perm_on_object($user,$res['object'], $res['objectType'], $perm)) { if ($ret["items"]["comments"]["list"][$count]["href"]) $ret["items"]["comments"]["list"][$count]["href"] .= '&comments_show=y#threadId'.$res['threadId']; $ret["items"]["comments"]["list"][$count]["title"] = $tikilib->get_short_datetime($res["commentDate"]) ." ". tra("by") ." ". $res["userName"]; $ret["items"]["comments"]["list"][$count]["label"] = $res["title"]; $count++;{CODE} Recreating the problem: #Enable comments for image galleries in Admin>general #Enable the module since_last_visit_new #Create an image gallery if one does not already exist #view an image gallery and post a comment |
tracker item |
Crash on a replication of site from Unix to Windows - and windows installation
Hello, ~~#0c6:HELP, I spent 120 hours on the problem, and I am completely stopped in my Work because I can't install Tikiwiki on the development tool on windows. I could not find a way to understand why 4.1 installation seam's impossible on windows. A failure, that I could not find till know, on windows is not detected by the product.~~ Sorry for the length. I try to install on windows to make test and developments an installation of tikiwiki 4.1 that is on a unix system (OVH provider with shared servers). So I can't have xdebug and many other facilities. This local replication is needed to begin my participation to the dev.tikiwiki.org. For this I have : 1- Changed the way to hold .htaccess (patch) For my apache I use the définition AccessFileName access.htaccess My various application are accessed via virtualhosts this since six years. 2- Enable all needed extension for php : the lonely problem is that it not exists an adodb.dll for php 5.3.0 on windows (not found) After I tried a manual installation : - create mysql db with data 4.1 - create local.php This crash on (see screen xdebug copy) the instruction in tikisession-pdo.php TikiDb::get()->setAttribute(PDO::ATTR_ERRMODE,PDO::ERRMODE_EXCEPTION); But when I made the searches (this is the opportunity to go inside the product) __I could not find the way how the instance of the class TikiDb inherit of the setAttribute method from probably Zend_Db_Statement_Pdo__ in lib\core\lib\Zend\Db\Statement\Pdo.php:411: If the link exists I am interested in the fact to understand the structure. If this come from the lack of the adodb.dll extension (functions and constants) this should be detected and I could not reach this execution point. Generally may be a detection of php extension features could in the future avoid my "exploration". I will redact when I will have solved all the problems a document about detail of a good implementation on windows. Thank's for an answer, because I am locked till 15 days on this problem. Trebly : ''__Nota1: __''I try new clean installation which don't functions, it crashes, after everything seems to be ended well installed the data are empty and a loop of to forms is without issue : # because the data base is not populated # because at the end we go back to the screen for validation of user and pass (second time) which calls the language form ad vitam. The analyze shows that the POST('user') and POST('pass') are not got back into tiki-install.php and the failed installer is not run again. Finally if I populate the data base with the data's (SQL) coming from one of the to implementations I reach the same as described upon. ''__Nota2:__'' The data's are well accessed by phpmyadmin and the parameters OK. '' __Nota3:__'' I run Mysql with mysqli extension. 256Mo of memory for php * Version du serveur: 5.1.37-community-log * Version du protocole: 10 * Utilisateur: root@localhost * Jeu de caractères pour MySQL: UTF-8 Unicode (utf8) Serveur web * Apache/2.2.13 (Win32) DAV/2 mod_ssl/2.2.13 OpenSSL/0.9.8k SVN/1.6.6 PHP/5.3.0 * Version du client MySQL: mysqlnd 5.0.5-dev - 081106 - $Revision: 1.3.2.27 $ * Extension PHP: mysqli phpMyAdmin * Version: 3.2.1 May be there are other reasons that I have not found after 100hours of work... |
tracker item |
Creator text box missing when creating blog in tiki-edit_blog.php
When a user attempts to create a blog, the Creator text box is missing and the creator value is not stored when the record is committed. |
tracker item |
Database engine is inconsistent on hosts with non-MyISAM default engines.
When installing Tiki 6.1 on a system with an engine other than MyISAM as the MySQL default, it creates a random mix of MyISAM tables and the default type tables. This gives the user all the drawbacks of using MyISAM without any of the benefits of using MyISAM, since the management features specific to each engine cannot be used uniformly. Ideally, Tiki should honor the MySQL default, but even forcing MyISAM consistently would be an improvement. Tiki 6.1 PHP 5.1.6 MySQL 5.0.77 |
tracker item |
1. add feature_print and checks
2. add tiki_p_print and checks
---
The above problem-description makes no sense... please look at tw#74 for that
---
Problem rephrased:
The "Source" button is currently dependant on tiki_p_view_history - it should have a perm of its own.