Loading...
 
Skip to main content

Category: Database MySQL (MyISAM)

What is related to the MySQL database.
Database MySQL (MyISAM)
Show subcategories objects

Name Type
Saving a page results in MySQL Error (tikiwiki/PHP/Apache/MySQL)
Install:

tikiwiki 1.9.3.2
PHP 5.1.4 (Build 2600)
Apache 2.2.2
MySQL 5.0

Whwn adding the following text to a page (text between but not including the "$" symbols) it will preview fine, but the Save operation causes an error with MySQL which shows up in the Apache logs as:

[Thu Jun 22 17:04:50 2006] [notice] Parent: child process exited with status 3221225477 -- Restarting.
[Thu Jun 22 17:04:50 2006] [notice] Apache/2.2.2 (Win32) PHP/5.1.4 configured -- resuming normal operations
[Thu Jun 22 17:04:50 2006] [notice] Server built: Apr 29 2006 18:32:31
[Thu Jun 22 17:04:50 2006] [notice] Parent: Created child process 672
[Thu Jun 22 17:04:51 2006] [notice] Child 672: Child process is running
[Thu Jun 22 17:04:51 2006] [notice] Child 672: Acquired the start mutex.
[Thu Jun 22 17:04:51 2006] [notice] Child 672: Starting 250 worker threads.
[Thu Jun 22 17:04:51 2006] [notice] Child 672: Starting thread to listen on port 80.


Here is the text you can try:


$

))Cohen-Steiner(( “Restricted delauney triangulations and normal

cycles”. are estimates of

the principle curvature directions at the vertex. Once we have computed principle curvatures for every isosurface

vertex, we can use the jack triangle floodfiller to flood-follow lines of curvature. The complexity here is how to

sample the curvature fields to produce curves.

*)

$

tracker item
Score feature got system error using MySQL 5.6.16
Installed and Setup Tiki 12.0 with MySQL 5.6.16.
Enabled Score feature.
Then posting to forum, I got System error. Error messages is ...
{CODE(caption="Tiki logs" wrap="1")}Field 'tstamp' doesn't have a default value - INSERT INTO...{CODE}

I think it would be relate to MySQL version.
Is it not certified with 5.6?
tracker item
Scoring feature causes intermittent blog access error in v1.9.8.3
Two users received the following error when trying to access a blog for which they have permissions in TW v1.9.8.3:
---
__An error occurred in a database query!__
Context:
File tiki-view_blog.php
Url tiki-view_blog.php?blogId=2
Query:
insert into 'tiki_users_score' ('user','event_id','expire') values (?,?,?)
Values:
0 [redacted username of blog creator]
1 blog_is_read_[redacted username of bug victim]:2
2 1200929940
Message:
Error Message Duplicate entry '[redacted blog creator]-blog_is_read_[redacted bug victim]' for key 1
---

No other users (~60) reported this error. The two affected users reported that other blogs were accessible.

~~#FF0000:__When Scoring was turned off, this error did not repeat until Scoring was turned back on.__~~
tracker item
Search modules - Problem with results and highlight
Using both search modules search_box and search_new my Tiki returns different results.

The results are identical if the search string has only English characters (standard ASCII).

Search_box returns more results than Search_new if the search string contains Greek characters (upper ASCII).

Search_new also highlights only "English" search strings.

I wish seaching Greek tokens and getting all possible results and highlighted too.
tracker item
SEF URL Search Engine Friendly URL
__A CMS without SEF URL means it is a Bug : Usability__

it's a by setup checkable standart in a high quality CMS
simple weblogs like http://www.s9y.org/ have such a feature

why :
google likes */this_is_a_very_god_page.html
and normaly google didn't index
*/mybugy.php?bestpage=my&t1=page&t2=is&t3=the&t4=best&indexed_by_SE=normalnever

i think the best webpage is nothing if SEFURL isn't working


the half way is done with the htaccess - ok
the next half way was a mod from http://www.coofercat.com/wiki/TikiURLtInstall

It's working in a root env with 1.9.x and 1.10cvs
that means only if /tmp is writable for the webserver - this is the bug

but online on a vserver this shit happens to me

Warning: mkdir(): open_basedir restriction in effect. File(/tmp/71) is not within the allowed path(s): (/srv/nww/webx/:/srv/nww/htdocs/phpMyAdmin/:/srv/nww/htdocs/confixx/html/gesperrt/) in /srv/nww/webx/html/wiki/lib/adodb/adodb.inc.php on line 1551

Warning: fopen(): open_basedir restriction in effect. File(/tmp/71/adodb_716f2422695ca15b221f4ce6f146321c.cache) is not within the allowed path(s): (/srv/nww/webx/:/srv/nww/htdocs/phpMyAdmin/:/srv/nww/htdocs/confixx/html/gesperrt/) in /srv/nww/webx/html/wiki/lib/adodb/adodb-csvlib.inc.php on line 298
......this msg repeats about 1000 times
did you know what's going on

I started to debug this problem
but it seams to get bigger and bigger

saved data titles must be renamed
becorce
http://localhost/HEAD/page-page%202.html
didn't result in
page 2
and so on
tracker item
Shared User tasks
I have encountered many problems with this feature when activating on dev.tikiwiki.org

A- The site becomes very slow...

B- ((TaskModuleTest)) page is almost totally blank.

C- Should there not be a feature setting for all of this?
tracker item
Some DB tables are not created on MySQL 5.5 and above during install
I created a test environment with the following components:
Apache 2.2.10
PHP 5.2.8
MySQL 6.0.8 alpha

I was not able to get MySQL 5.1 working on my machine,
but I was abe to get 6.0.8alpha runnning smooth.

I checked out the latest code in TRUNK 15953
pointed Apache to the files.

I ran tiki-install.php without problems except the following 3 SQL problems
which I suppose is due to MySQL version 6.0.8alpha

As my SQL skills are not up to date...
Are there any solutions for these bug?

Do not propose, that version 6 of MySQL is not supported :-)

~np~CREATE TABLE tiki_banning (
banId int(12) NOT NULL auto_increment,
mode enum('user','ip') default NULL,
title varchar(200) default NULL,
ip1 char(3) default NULL,
ip2 char(3) default NULL,
ip3 char(3) default NULL,
ip4 char(3) default NULL,
user varchar(200) default '',
date_from timestamp(14) NOT NULL,
date_to timestamp(14) NOT NULL,
use_dates char(1) default NULL,
created int(14) default NULL,
message text,
PRIMARY KEY (banId)
) ENGINE=MyISAM AUTO_INCREMENT=1~/np~
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(14) NOT NULL,
date_to timestamp(14) NOT NULL,
use_dates char(1) default NUL' at line 10

~np~CREATE TABLE tiki_friendship_requests (
userFrom varchar(200) NOT NULL default '',
userTo varchar(200) NOT NULL default '',
tstamp timestamp(14) NOT NULL,
PRIMARY KEY (userFrom(120),userTo(120))
) ENGINE=MyISAM~/np~
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(14) NOT NULL,
PRIMARY KEY (userFrom(120),userTo(120))
) ENGINE=MyISAM' at line 4

~np~CREATE TABLE tiki_users_score (
user char(200) NOT NULL default '',
event_id char(200) NOT NULL default '',
expire int(14) NOT NULL default '0',
tstamp timestamp(14) NOT NULL,
PRIMARY KEY (user(110),event_id(110)),
KEY user (user(110),event_id(110),expire)
) ENGINE=MyISAM~/np~
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(14) NOT NULL,
PRIMARY KEY (user(110),event_id(110)),
KEY user (user(110),ev' at line 5
tracker item
change the table definitions to support the new utf8mb4 character
I was creating a wiki page entry and encounter a bug. When a special character is used in the text, text is deleted at the instance of the first special character and below. I just upgraded from 10.2 to 11.1 hoping to fix this problem. Both version delete text using special characters inserted using the character feature of the editor. mu, epsilon, pi, kappa, h bar were used. epsilon is the first special character and was the start of the deleted text.

-----

This is now converted into a Feature Request for tiki 13, See comment thread for reasons why {sign user="pascalstjean" datetime="2013-11-27T16:09:44+00:00"}
tracker item
Specific edit perm causes global view perm to fail.
Even though global perms allow viewing wiki pages (to Anonymous, for example), assigning an edit perm to another group for a specific wiki page overrides the view perm and Anonymous can't see it anymore unless a specific tiki_p_view perm is assigned to the page for Anonymous.

this is a feature - it is how it works . As soon as you hjave a special perms, you need to redefine all the perm for the page
tracker item
Spellcheck dictionary should be install via mods, in many languages.
This is a perfect use for mods.

words_en.sql weighs 7.5 Megs. This is not super easy to upload via phpmyadmin.
tracker item
spellcheck feature not working properly (yet), specially with latin characters in text
Hi:

I just tried spellcheck, with the provided english dictionary at sf.net (words_en.sql, etc.). And also added another one as a trial (words_ca.sql, with 15 catalan words, etc.), coded words with utf-8.

Enabled feature, Created a new page with some words:
^
abaconarà
Abaconarà
abaconará
Abaconarà
Abaconara
abaconara
perquè així però vinyals calçador
howto
howtee
yeouhooo
spellchek
^

The only one shown in red at preview state is "~~red:vinyals~~", having interface either in English or Catalan.
There must be something wrong in the feature.

The only word included in words_ca.sql is abaconarà (non of the others is)

And in words_en.sql, non of the catalan words are, and I guess yeouhooo is not either...
tracker item
Spellcheck: database data check and friendly error message
As of today (pre 1.9.8), if I activate the Spellcheck, I get:

{img src=images/code.png}%%% {CODE()}
An error occured in a database query!

Context:
File php.cgi
Url tiki-editpage.php
Query:
select `word` from `babl_words_fr` where `word`=? or `word`=?
Values:
0 test
1 test
Message:
Error Message
{CODE}


I need to know from:
http://doc.tikiwiki.org/Spellcheck

That I need to install the word dictionary database separately from the rest of Tiki.


Tiki should check that the table exists and return a nicer error message.


And why is Tiki searching for "babl_words_fr"? My browser and Tiki are in English...
tracker item
SQL error when using wikiplugin_contributionsdashboard
When using the profile https://profiles.tiki.org/Test_All_Features to test a clean Tiki 20.0 installation, I get the following error when accessing the tiki page "Test_All_Plugins":

{CODE()}
Expression #2 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'tiki-test-20-0.tiki_actionlog.lastModif' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by

The query was:

SELECT COUNT(actionId) AS count, DATE_FORMAT(FROM_UNIXTIME(lastModif), '%m/%d/%Y') as date FROM tiki_actionlog WHERE objectType = ? AND lastModif > ? AND lastModif < ? GROUP BY DATE_FORMAT(FROM_UNIXTIME(lastModif), '%Y%m%d') ORDER BY lastModif DESC
{CODE}

And the stack trace was:
{CODE()}
* /vagrant/test/tiki-20.0/tiki-index.php : 0 -> {main}(array ( ))
* /vagrant/test/tiki-20.0/tiki-index.php : 681 -> __toString(array ( ))
* /vagrant/test/tiki-20.0/lib/core/Tiki/Render/Lazy.php : 22 -> {closure:/vagrant/test/tiki-20.0/lib/wiki/renderlib.php:347-357}(array ( ))
* /vagrant/test/tiki-20.0/lib/wiki/renderlib.php : 350 -> get_parse(array ( 'page' => '???', 'canBeRefreshed' => '???', 'suppress_icons' => '???', ))
* /vagrant/test/tiki-20.0/lib/wiki/wikilib.php : 802 -> __construct(array ( 'info' => '???', 'originalValue' => '???', 'options' => '???', 2 => '???', ))
* /vagrant/test/tiki-20.0/lib/wiki/wikilib.php : 2118 -> parse_data(array ( 'data' => '???', 'option' => '???', ))
* /vagrant/test/tiki-20.0/lib/parser/parserlib.php : 1369 -> parse(array ( 'options' => '???', ))
* /vagrant/test/tiki-20.0/lib/core/WikiParser/Parsable.php : 252 -> parse_first(array ( 'data' => '???', 'preparsed' => '???', 'noparsed' => '???', 'real_start_diff' => '???', ))
* /vagrant/test/tiki-20.0/lib/core/WikiParser/Parsable.php : 103 -> plugin_execute(array ( 'name' => '???', 'data' => '???', 'args' => '???', 'offset' => '???', 'validationPerformed' => '???', 'option' => '???', ))
* /vagrant/test/tiki-20.0/lib/core/WikiParser/Parsable.php : 472 -> wikiplugin_contributionsdashboard(array ( 'data' => '???', 'params' => '???', 1 => '???', 2 => '???', ))
* /vagrant/test/tiki-20.0/lib/wiki-plugins/wikiplugin_contributionsdashboard.php : 125 -> countByDateFilterId(array ( 'ids' => '???', ))
* /vagrant/test/tiki-20.0/lib/logs/logsquerylib.php : 206 -> countByDate(array ( ))
* /vagrant/test/tiki-20.0/lib/logs/logsquerylib.php : 181 -> fetchAll(array ( ))
* /vagrant/test/tiki-20.0/lib/logs/logsquerylib.php : 325 -> fetchAll(array ( 'query' => '???', 'values' => '???', 'numrows' => '???', 'offset' => '???', 'reporterrors' => '???', ))
* /vagrant/test/tiki-20.0/lib/core/TikiDb/Bridge.php : 32 -> fetchAll(array ( 'query' => '???', 'values' => '???', 'numrows' => '???', 'offset' => '???', 'reporterrors' => '???', ))
* /vagrant/test/tiki-20.0/lib/core/TikiDb/Pdo.php : 135 -> handleQueryError(array ( 'query' => '???', 'values' => '???', 'result' => '???', 'mode' => '???', ))
* /vagrant/test/tiki-20.0/lib/core/TikiDb.php : 174 -> handle(array ( 'db' => '???', 'query' => '???', 'values' => '???', 'result' => '???', ))
{CODE}
tracker item
SQL plugin won't work with empty passwords
strtok does not return empty tokens. If the password is empty in the DSN the parser comes out of order.
tracker item
Standard permissions for features per groups
Every time a new object gets created (wiki page, blog entry etc) the item recieves only global permissions.

It would help a lot if the admin could define 'standard permissions' for each group for specific features.
(needs to be integrated with improvements to "permissions by category" introduced in 1.9 - which provides a coherent approach for "object" based permissions to compliment user based perms.)

To keep wiki pages inside the group, the admin would assign the read right only to that group, and a member of that group posting a new item would not have to worry about security as much.

Am not sure what to do when user is member of multiple groups... maybe she can select in a drop-down which is the one that wins, or maybe the admin determins that when creating the user?

Reccomendation: Inherit permissions. (particularly for wiki)
The default behavior for a new object should be to inherit permissions from the page it was created from (global if none). Particularly in a wiki, this would facilitate the use of "private areas" - key feature for tikiwiki as groupware so committees. groups, etc. can operate in privacy, if so desired. Whoever create the page should be able to disable this inheriting, but it should be on by default. Admins can then create private wiki spaces by customizing perms on one page (the group home page).
tracker item
support media casting (e.g. podcasting) from blogs
Support inclusion of media in blogs to provide podcasting, vodcasting, etc.

- Attachment of media files to blog posts
- Association of URLs to other media files on Tiki or elsewhere to blog posts
- Automatic recognition of relevant data from media files using getid3
- Creation of fields in database to store relevant media data
- Creation of enclosure and media XML tags in RSS feed
- Display of media controls in blog entries
- Test using iTunes and iPod, iPodder, Thunderbird, among others

This should be an optional feature, admin through the Blogs Admin panel
Should allow choice of db or file storage, but probably file storage will normally be used, as media files tend to be quite large.

Existing image attachment functionality in blogs will need substantial improvement to support this.
tracker item
Test if the db upgrade script has been run and put a note in tiki-admin.php
This would avoid this type of issue:
http://tikiwiki.org/tiki-view_forum_thread.php?topics_offset=1&forumId=6&comments_parentId=21274

Maybe at each release, we could add one test of the DB to see if the most recent sql additions were done.


phplist does this well. Once click and your DB is in the right format.
tracker item
The possible text-length for fortune cookies should be longer
Subject says it all.

Some great men(women) said great things - and I can't enter their name in addition to their quote!! ;(

Give credit, where credit's due! And I take that very seriously!
tracker item
tiki_preferences.name should be longer than 40 characters
The field "name" in the tiki_preferences is currently limited to 40 characters.

This may be appropriate for English speakers, as soon as you start developing german-language Wiki Plugins, it becomes awfully little. For Example:

You are trying to write a plugin named

__ inventarisierung_details (this string has 24 characters).

As soon as you try to configure this, it becomes

__ wikiplugininline_inventarisierung_details (this one has 41 characters)

and fails horribly.
tracker item
tikiwiki calls non-existent pear library without checking that library is installed
I have configured "tiki and pear::auth" in the login section of tikiwiki on a server which did not have the pear php libraries installed.
Next time I try to login with a user (not admin), I see a blank page.

This happens because on line 756 of file lib/userslib.php
$a = new Auth("LDAP", $options, "", false, $user, $pass);
just dies without any error message.
tracker item
TikiWiki without AdoDB lacks the capability of writing correct UTF-8 data to MySQL
I have just migrated a Tiki from one server to another and ran into
UTF-8 Problems. The browser showed Umlauts as the dreaded diamonds with
question marks in them.

Both servers are fully utf-8 compliant as described in
http://tikiwiki.org/UTF-8

The big problem is that on the new server PDO is available while it
isn't on the old one. According to the mailing list PDO is not default,
but as far as I can see in the code PDO will be default, if available
and not set otherwise. Setting

$api_tiki='adodb';

in db/local.php fixes the special character problem.

The issue seems to be that PDO gives a silent fuc# about encodings and
just pumps everything to the database and back as you hand it to it.
Additionally PHP/PDO doesn't read your my.cnf and therefore doesn't know
which encoding to use.
A quick fix is telling PDO which encoding to use - line 39 in
db/tiki-db-pdo.php :

$dbTiki = new PDO("$db_tiki:$db_hoststring;dbname=$dbs_tiki",
$user_tiki, $pass_tiki,array(PDO::MYSQL_ATTR_INIT_COMMAND => "SET NAMES
utf8"));

But I think that this is not safe to commit...
e.g. someone started with Tiki on MySQL 4.0 which used latin1 as
default, so all her tables are latin1. She upgrades MySQL to 5.1, but
doesn't change the Tiki database to default to utf-8 and hasn't
converted the database. Then the PDO-fix above will most probably
produce the same problem, just the other way around...

No idea, what to do actually, but wanting to raise awareness here!

This is a dangerous issue as people with utf-8 databases upgrading their
system or Tiki and switching automagically over to PDO will end up with
mixed stuff in their database: clean UTF-8 and double-byte
ansi-control-characters which MySQL converted to their right unicode
codepoints (freaky, hm? ;) ).

I hope, I was capable of describing the problem in a way that's
understandable....
tracker item
Tracker Plugin fails with trackers with mirror tables
{maketoc}

Using 1.9.cvs

!! 1st trial
!!! Using a tracker plugin code within this page content:
{CODE()}
{MAKETOCBOX(float=>none)}{MAKETOCBOX}
!! Ofertes de recursos o serveis

!!! Oferiments de transports
{TRACKERLIST(trackerId=>2,fields=>5:6:7:17:8:11, showtitle=>n, showlinks=>y, showdesc=>n, showinitials=>y, showstatus=>y, status=>opc, sort_mode=>asc, max=>20, filterfield=>6, filtervalue=>Transport, exactvalue=>Transport, goIfOne=>n)}Com????{TRACKERLIST}

!!! Oferiments de recursos (materials)
{TRACKERLIST(trackerId=>2,fields=>5:6:7:17:8:11, showtitle=>n, showlinks=>y, showdesc=>n, showinitials=>y, showstatus=>y, status=>opc, sort_mode=>asc, max=>20, filterfield=>6, filtervalue=>Recurs, exactvalue=>Recurs, goIfOne=>n)}Com????{TRACKERLIST}

!!! Oferiments de serveis (immaterials)
{TRACKERLIST(trackerId=>2,fields=>5:6:7:17:8:11, showtitle=>n, showlinks=>y, showdesc=>n, showinitials=>y, showstatus=>y, status=>opc, sort_mode=>asc, max=>20, filterfield=>6, filtervalue=>Servei, exactvalue=>Servei, goIfOne=>n)}Com????{TRACKERLIST}

!!! Oferiments d'altres coses
{TRACKERLIST(trackerId=>2,fields=>5:6:7:17:8:11, showtitle=>n, showlinks=>y, showdesc=>n, showinitials=>y, showstatus=>y, status=>opc, sort_mode=>asc, max=>20, filterfield=>6, filtervalue=>Altres, exactvalue=>Altres, goIfOne=>n)}Com????{TRACKERLIST}

!! Insereix nous oferiments a la base de dades
{TRACKER(trackerId=>2, fields=>5:6:7:17:8:16:11, action=>Envia les dades del teu oferiment, showtitle=>n, showdesc=>n, showmandatory=>y, embedded=>y)}Oferiment enviat amb èxit! Pots continuar navegant per la web amb normalitat. {TRACKER}
{CODE}

!!!- Tracker 2 is this one:
{CODE()}
[TRACKER]
trackerId = 2
name = Ofertes
description = Ofertes de recursos i serveis de persones de la Vall del Corb i afins
useExplicitNames = n
showStatus = y
defaultStatus = o
showStatusAdminOnly = n
outboundEmail =
simpleEmail = n
newItemStatus = o
modItemStatus =
writerCanModify = y
writerGroupCanModify = n
showCreated = y
showLastModif = y
defaultOrderKey = -1
defaultOrderDir = asc
useComments = y
showComments = n
useAttachments = y
showAttachments = n
attachmentsconf = 0,1,3,0,2,0,0,0
useRatings = n
ratingOptions =
categories = 3
{CODE}

!!!- And its fields are these:
{CODE()}
[FIELD5]
fieldId = 5
name = Què ofereixes?
position = 10
type = t
options =
isMain = y
isTblVisible = y
isSearchable = y
isPublic = y
isHidden = n
isMandatory = y
[FIELD6]
fieldId = 6
name = Tipus d'oferta
position = 20
type = d
options = Recurs,Servei,Transport,Altres
isMain = n
isTblVisible = y
isSearchable = y
isPublic = y
isHidden = n
isMandatory = y
[FIELD7]
fieldId = 7
name = Descripció
position = 30
type = a
options = 1
isMain = n
isTblVisible = n
isSearchable = y
isPublic = y
isHidden = n
isMandatory = n
[FIELD17]
fieldId = 17
name = Foto
position = 35
type = i
options = 50,50,400,400,400
isMain = n
isTblVisible = n
isSearchable = n
isPublic = y
isHidden = n
isMandatory = n
[FIELD8]
fieldId = 8
name = Persones interessades
position = 40
type = l
options = 3,15,5,14,1
isMain = n
isTblVisible = y
isSearchable = y
isPublic = y
isHidden = n
isMandatory = n
[FIELD16]
fieldId = 16
name = Demanda relacionada
position = 45
type = r
options = 3,9,1
isMain = n
isTblVisible = y
isSearchable = n
isPublic = y
isHidden = n
isMandatory = n
[FIELD11]
fieldId = 11
name = Persona que ho ofereix
position = 50
type = u
options = 1
isMain = y
isTblVisible = y
isSearchable = y
isPublic = y
isHidden = p
isMandatory = n
{CODE}

!!! I inserted this information:

||Què ofereixes? *: | Manual d'administració de Webs com aquesta
Tipus d'oferta *: |Recurs
Descripció: | En pdf..., i en català . tot i que la versió en anglès és més complerta.
Foto: |
Demanda relacionada: |
Persona que ho ofereix | admin
| submit button ||
''(At this page: [http://www.moviments.net/valldelcorb/Ofertes] )''

!!! I get this message after attempting to insert a new record:
^
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '='Ofertes' where `itemId`='13'' at line 1
^

!! 2nd trial
I made another trial in another page just having the tracker plugin ([http://moviments.net/valldelcorb/prova]), with just this content in the page:
{CODE()}
{TRACKER(trackerId=>2, fields=>5:6:7:17:8:16:11, action=>Envia les dades del teu oferiment, showtitle=>n, showdesc=>n, showmandatory=>y, embedded=>y)}Oferiment enviat amb èxit! Pots continuar navegant per la web amb normalitat. {TRACKER}
{CODE}

I got this message:
^
Warning: mysql error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '='prova' where `itemId`='14'' at line 1 in query:

update tiki_trk_2 set =? where `itemId`=?


in /home/httpd/tiki19/lib/tikidblib.php on line 134
^
tracker item
Tracker should have possibility to be marked as duplicate
{syntax type=tiki}
{syntax type="tiki" editor="plain"}
This is the ((Tracking system for Tiki issues)).
If this is your first time, please read: ((How to Submit a new item on the Wishlist))
tracker item
unable to connect to DB after upgrade to 4.0
Tikiwiki 2.3 was upgraded to 4.0. Upgrade went well, DB connection was found, DB was upgraded, installer locked. TW4.0 is unable to connect to the MySQL5 DB it was able to upgrade seconds before. See: http://tikiwiki.org/tiki-view_forum_thread.php?topics_offset=1&forumId=6&comments_parentId=35478
tracker item
Undefined index: showAttachments in tiki-view_tracker.php
A simple tracker view (such as: http://uniwiki.ourproject.org/tiki-view_tracker.php?trackerId=4) produces a warning like:
^
Notice: Undefined index: showAttachments in /var/lib/gforge/chroot/home/groups/uniwiki/htdocs/tiki-view_tracker.php on line 625

Warning: Cannot modify header information - headers already sent by (output started at /var/lib/gforge/chroot/home/groups/uniwiki/htdocs/tiki-view_tracker.php:625) in /var/lib/gforge/chroot/home/groups/uniwiki/htdocs/tiki-view_tracker.php on line 675
^
tracker item
Show PHP error messages