Loading...
 
Architecture / Installation

Architecture / Installation


Need help with older Tiki 1.9.8.3 and image gallery problem (long)

posts: 166 Germany

Hi,

I have a seemingly weird problem with the image gallery on my old Tiki 1.9.8.3. I am aware that I need to update this to a current level (and shift from image to file galleries), but I think it would be a good idea to ask for some advice from friendly users/admins/developers to find the right strategy:

a) Fix the DB problem and perform the upgrade
b) Upgrade first
c) Which path to upgrade:
c1) Upgrade directly to the current LTS or
c2) Upgrade in steps, and if so: Which versions?
c3) Migrate images from image gallery to file galery when?

Since I only admin this Tiki as a hobby, but am otherwise quite experienced in other IT areas, I would be very grateful for help from more experienced Tiki users/admins/developers. First, let me describe the problem (long!).

I started this Tiki with Polaris, upgraded to Sirius, and the last upgrade I installed was 1.9.8.3. With that upgrade, the image upload behaviour changed. Sometimes large images would not upload correctly. Back then I thought this would be due to the CPU time limitation that my ISP has on using PHP and MySQL, and that the new version would simply consume more CPU.

Now after running the Tiki for a couple of years I have to find that also some older images that had successfully uploaded became corrupted. There are entries in the image gallery that have no thumbnail and no image, and some do have a thumbnail, but no image behind that. The Tiki is set to store images in the DB.

When calling on a broken image, there is no error message, just the image (or the thumbnail) are missing in action. When calling the image by entering the URL I get a 500 Internal Server Error followed by a 404 for a missing error handler page. This happens both with calling by ID and with calling by image name.

A 500 is also thrown when hitting the edit image property link (tiki-edit_image.php).

When uploading images, there is a difference depending on whether I use the solitary entry field for uploading from disk, or one of the six that are grouped together. In the first case I get

Warning: preg_match() function.preg-match: Compilation failed: nothing to repeat at offset 0 in account data deleted/htdocs/tiki/tiki-upload_image.php on line 135

In the second case I get a bogus success message, with no image in it, and an entry in the gallery with no thumbnail and no image.

When I navigate to the System Gallery and use the "All images" dialog, I get an unformatted text page with a drop down list. Selecting a gallery and hitting View results in

Warning: imagettftext() function.imagettftext: Could not find/open font in account data deleted/htdocs/tiki/tiki-show_all_images.php on line 80

Warning: Cannot modify header information - headers already sent by (output started at account data deleted/htdocs/tiki/tiki-show_all_images.php:80) in account data deleted/htdocs/tiki/tiki-show_all_images.php on line 109

Warning: Cannot modify header information - headers already sent by (output started at account data deleted/htdocs/tiki/tiki-show_all_images.php:80) in account data deleted/htdocs/tiki/tiki-show_all_images.php on line 110

followed by pure binary data which might be the image, it contains the string JFIF...

Some gallerys however show something different with View. The show a formatted page that is prepended by a PHP error

Warning: imagettftext() function.imagettftext: Could not find/open font in account data deleted/htdocs/tiki/tiki-show_all_images.php on line 80

Warning: mysql error: Duplicate entry '0-80-80-t' for key 1 in query:

insert into `tiki_images_data`(`imageId`,`xsize`,`ysize`,
`type`,`filesize`,`filetype`,`filename`,`data`)
values (?,?,?,?,?,?,?,?)

in account data deleted/htdocs/tiki/lib/tikidblib.php on line 134

followed by a small table and another error message, this time by Tiki:

Fehler beim Zugriff auf die Datenbank! Error accessing the DB

Context:
File tiki-show_all_images.php
Url tiki-show_all_images.php?view=image&id=6
Query:
insert into `tiki_images_data`(`imageId`,`xsize`,`ysize`, `type`,`filesize`,`filetype`,`filename`,`data`) values (?,?,?,?,?,?,?,?)
Values:
0 0
1 80
2 80
3 t
4 771
5
6 80x80_
7 ....JFIF..>CREATOR: gd-jpeg v1.0 (using IJG JPEG v62), default quality...binary stuff

Message:
Error Message Duplicate entry '0-80-80-t' for key 1

There are no other DB problems so far. The Tiki mostly contains lots and lots of very very long text pages, which are seemingly intact.

And just a little side-note: I could never activate the .htaccess file or implement the tip documented here on tiki.org to increase size limits in .htaccess to override php.ini when having upload problems. This always results in a completely disfunct Tiki that always throws 500s, so I left that out.

Again, thanks for anyone who took the time to read this lengthy problem description and who is kind enough to write me some remarks or even tips how to sort this out and help me upgrade to current LTS, if possible with a clean DB and all images of my users... I do have backups from the internal Tiki backup and from MySQL Admin and I found copies of the damaged images in Tikis temp directory, but users tell me these would not be the very latest versions of the images.

Thanks
Oliver

posts: 1539 Canada

Hi!

I suggest you try a test upgrade to Tiki6 LTS. You may be getting an issue because your old Tiki (which was designed for PHP4) is on a more recent version of PHP.

You can do a direct upgrade. Tiki 6.x contains all the SQL instructions to upgrade from 1.8.x or any later version.

  • Make a backup of your current site
  • Install a Tiki 6.x and point to the DB backup


You have the option to store images on the file system instead of the database. This will solve the issue with uploading larger images. There is also a "mover" feature to go from filesystem to database or vice versa. See: tiki-admin.php?page=gal

In terms of image gallery vs file gallery: you can continue to use image galleries. There is not much dev on them, but they will only be removed when an upgrade script is available. No one has volunteered to take this on yet, and we need to migrate the data and make sure URLs still work.

About tiki-show_all_images.php, that was experimental and AFAIK, still is. There has not been any work on it in years:
http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/trunk/tiki-show_all_images.php?view=log

Please keep us updated with your progress.

Best regards,

M ;-)

posts: 166 Germany

Hi Marc,

thanks for your help. I'll try what you suggested.

Just for the sake of clarity, by the term 'backup' you're talking about backing up the MySQL DB with DB tools, and not about the internal backup tool in TikiWiki, right? At least in 1.9.8.3 the latter says that its use is discouraged. I do have the tools for a DB backup, but maybe I will have to upgrade them too :-)

posts: 1539 Canada

"Just for the sake of clarity, by the term 'backup' you're talking about backing up the MySQL DB with DB tools, and not about the internal backup tool in TikiWiki, right? "

Right, use external tools for backup.

posts: 166 Germany

Some analysis beforehand. I wanted to update my old phpMyAdmin 2.5.7, but then I found that by now my ISP has "built-in" phpMyAdmin. 2.6.3-pl, current version is 2.11.11.3 (no PHP 5 here, so no 3.x). Btw - I hope TikiWiki 6.7 LTS does not demand PHP 5?), but since the ISPs version is adapted to this ISPs MySQL, it should be fine.

So I checked into the database lying underneath my TikiWiki installation. And to my astonishment I found that all image data is right there in tiki.images.data, so all (!) uploads went okay, just something else went wrong. Checking the database finds no errors.

So now I can backup the entire DB, but I would like to extract the longblobs with the images in question just to make sure I have them as JPEGs on disk... Unfortunately there is no easy way to do this with phpMyAdmin.

And another remark, there seems to be a small issue with filenames, the DB is set to charset de-iso-8859-1 and some "umlauts" in filenames don't look right. However that is also true for images that work well inside the TikiWiki GUI.

posts: 166 Germany
Update: I can switch from PHP 4.4.9 to PHP 5, but only globally. So when I do this I'll have to check my personal (hand-written) PHP scripts. MySQL is already version 5.
posts: 1539 Canada

" I would like to extract the longblobs with the images in question just to make sure I have them as JPEGs on disk..."

There is the "mover" feature to go from filesystem to database or vice versa. See: tiki-admin.php?page=gal


charset de-iso-8859-1: Tiki 6 has a UTF-8 converter in the installer. This will assist in converting. But do test everything thoroughly on backup data. Because of legacy concerns and variations of data from hosts, it's doesn't always work well.


posts: 166 Germany

Okay, right now I am in the upgrade process.

I copied the database to a new MySQL 5 DB (and made a backup anyhow), switched from PHP 4.4 to 5. Uploaded 6.7 LTS.

Now I have an encoding problem. The old database entries were written in latin_german2_ci (the new db itself is already UTF-8). The installer offered me to convert to UTF-8.

This did not function correctly. All tables were converted - except for tiki_seachindex. And so the installier (rightly) complains.

I _hope_ that I can ignore this, as the searchindex should rebuild at some point? Can you give me a hint?

Thanks.

posts: 1539 Canada

tiki_seachindex: yes, you can just empty this.

You can also just use MySQL search instead, configurable at tiki-admin.php?page=search

M ;-)


posts: 166 Germany

I set the collation of table tiki_seachindex to UTF8_general_ci with phpMyAdmin. Then the installer did not complain again...

I converted and got a success message, with 113 SQL failures, from which only 2 were shown, and they looked minor (existing column find, and 119).

I locked the installer - and got to my Tiki. But - I'm locked out. I used the lock for maintenance feature before copying the database, so it should be okay that it is locked now.

But I cannot unlock it, when I enter my admin password nothing happens. It does not log me in and it does not show any error message. It just reloads the lock message...

So now I definitely need help...


posts: 166 Germany
Hm, it's not a wrong admin pwd. I reset this directly in phpMyAdmin as described here, does not help...

posts: 166 Germany

Oops, that was just a typo. So I managed to set an admin pwd and can now log in as admin.

But strangely admin does not seem to have any rights, he cannot see even the start page, despite to anything, and he cannot start anything administrative.

Users are less hampered, but user accounts are severly limited, too. The can see some things, but not change anything for instance...

posts: 1539 Canada

In the old days, the user "admin" had special rights. (and was not part of the Admins group)

For security reasons (you can make this known username have no perms), and to simplify the code, user "admin" needs to be part of the "Admins" group to have admin rights.

tiki-installer.php lets you do this.


posts: 166 Germany

I tricked myself in to be able to admin, I had a group "Subadmins" which I gave permission tiki_p_admin so I can now admin with my user account.

But when I call the administration panel, I get a warning that my database needs updating and that I should run installer.php. So I re-ran installer.php, and I still get the warning (and users have rights problems).

Something is wrong here...

posts: 1539 Canada

The installer should give you an option to ignore some of the upgrade errors.

About the permissions: I suggest you empty the cache at
tiki-admin_system.php?do=all

If still weird, try reconfiguring them.

M ;-)


posts: 166 Germany

Here's the output from the installer upgrade.
1.9 to 2.0:

  1. 2005-09-31: mdavey: make sure developers are using the 6-column version of tiki_events

ALTER TABLE `tiki_events` ADD `file` varchar(200) NOT NULL default '' AFTER `event`
Duplicate column name 'file'

ALTER IGNORE TABLE tiki_comments ADD UNIQUE parentId(parentId, userName, title, commentDate, message_id, in_reply_to)
Specified key was too long; max key length is 1000 bytes

  1. 2005-10-24 sylvieg to boost tiki_stats and tiki_orphan

CREATE INDEX toPage on tiki_links (toPage)
Duplicate key name 'toPage'

  1. 2005-11-14 sylvieg

CREATE INDEX positionType ON tiki_modules (position, type)
Duplicate key name 'positionType'

CREATE INDEX login ON users_users (login)
Duplicate key name 'login'

  1. 2006-06-07 sylvieg (merge from 1.9)

insert into users_permissions (permName,permDesc,level,type) values ('tiki_p_admin_objects','Can edit object permissions', 'admin', 'tiki')
Duplicate entry 'tiki_p_admin_objects' for key 1

insert into users_permissions (permName,permDesc,level,type) values ('tiki_p_admin_polls','Can admin polls', 'admin', 'tiki')
Duplicate entry 'tiki_p_admin_polls' for key 1

INSERT INTO users_permissions (permName,permDesc,level,type) values ('tiki_p_admin_rssmodules','Can admin rss modules', 'admin', 'tiki')
Duplicate entry 'tiki_p_admin_rssmodules' for key 1

ALTER TABLE tiki_comments DROP KEY parentId
Can't DROP 'parentId'; check that column/key exists

ALTER TABLE tiki_comments DROP KEY parentId_2
Can't DROP 'parentId_2'; check that column/key exists

ALTER TABLE tiki_comments DROP KEY parentId_3
Can't DROP 'parentId_3'; check that column/key exists

ALTER TABLE tiki_comments DROP KEY parentId_4
Can't DROP 'parentId_4'; check that column/key exists

ALTER TABLE tiki_comments DROP KEY parentId_5
Can't DROP 'parentId_5'; check that column/key exists

ALTER TABLE tiki_comments DROP KEY parentId_6
Can't DROP 'parentId_6'; check that column/key exists

ALTER TABLE tiki_comments DROP KEY parentId_8
Can't DROP 'parentId_8'; check that column/key exists

ALTER TABLE tiki_comments DROP KEY no_repeats
Can't DROP 'no_repeats'; check that column/key exists

alter table tiki_comments change userName userName varchar(200) not null default ''
Specified key was too long; max key length is 1000 bytes

alter table tiki_comments change userName userName varchar(200) default ''
Specified key was too long; max key length is 1000 bytes

  1. 02/01/2007 mkalbere & Jyhem 2007-06-14

ALTER TABLE `tiki_tracker_item_fields` DROP INDEX value
Can't DROP 'value'; check that column/key exists

ALTER TABLE `tiki_tracker_item_fields` DROP INDEX value_1
Can't DROP 'value_1'; check that column/key exists

ALTER TABLE `tiki_tracker_item_fields` DROP INDEX value_2
Can't DROP 'value_2'; check that column/key exists

ALTER TABLE `tiki_tracker_item_fields` DROP INDEX value_3
Can't DROP 'value_3'; check that column/key exists

ALTER TABLE `tiki_tracker_item_fields` DROP INDEX value_4
Can't DROP 'value_4'; check that column/key exists

ALTER TABLE `tiki_tracker_item_fields` DROP INDEX value_5
Can't DROP 'value_5'; check that column/key exists

ALTER TABLE `tiki_tracker_item_fields` ADD FULLTEXT KEY ft (value)
Duplicate key name 'ft'

ALTER TABLE `tiki_links` ADD INDEX `toPage` (`toPage`)
Duplicate key name 'toPage'

ALTER TABLE tiki_comments CHANGE title title varchar(255)
Specified key was too long; max key length is 1000 bytes

  1. sylvieg 2007/05/25

ALTER TABLE users_users CHANGE email_due email_confirm int(14) default NULL
Unknown column 'email_due' in 'users_users'

    1. 2007-07-10 sylvieg - thx tibi - duplication from 1_8to1_9

ALTER TABLE users_permissions ADD INDEX type (type)
Duplicate key name 'type'

ALTER TABLE tiki_articles ADD INDEX topicId (topicId)
Duplicate key name 'topicId'

ALTER TABLE tiki_articles ADD INDEX publishDate (publishDate)
Duplicate key name 'publishDate'

ALTER TABLE tiki_articles ADD INDEX expireDate (expireDate)
Duplicate key name 'expireDate'

ALTER TABLE tiki_articles ADD INDEX type (type)
Duplicate key name 'type'

ALTER TABLE tiki_forum_attachments ADD INDEX threadId (threadId)
Duplicate key name 'threadId'

ALTER TABLE users_users ADD INDEX login (login)
Duplicate key name 'login'

ALTER TABLE tiki_article_types ADD INDEX show_pre_publ (show_pre_publ)
Duplicate key name 'show_pre_publ'

ALTER TABLE tiki_article_types ADD INDEX show_post_expire (show_post_expire)
Duplicate key name 'show_post_expire'

ALTER TABLE tiki_comments DROP KEY object
Can't DROP 'object'; check that column/key exists

ALTER TABLE tiki_comments ADD INDEX objectType (object, objectType)
Duplicate key name 'objectType'

ALTER TABLE tiki_comments ADD INDEX commentDate (commentDate)
Duplicate key name 'commentDate'

ALTER TABLE tiki_sessions ADD INDEX user (user)
Duplicate key name 'user'

ALTER TABLE tiki_sessions ADD INDEX timestamp (timestamp)
Duplicate key name 'timestamp'

ALTER TABLE tiki_galleries ADD INDEX parentgallery (parentgallery)
Duplicate key name 'parentgallery'

ALTER TABLE tiki_galleries ADD INDEX visibleUser (visible, user)
Duplicate key name 'visibleUser'

ALTER TABLE tiki_modules ADD INDEX positionType (position, type)
Duplicate key name 'positionType'

ALTER TABLE messu_messages ADD INDEX userIsRead (user, isRead)
Duplicate key name 'userIsRead'

  1. nyloth 2007-07-15

ALTER TABLE tiki_menu_options ADD UNIQUE KEY uniq_menu(menuId,name,url,position,section,perm)
Specified key was too long; max key length is 1000 bytes

  1. sylvieg 2007-07-19

ALTER TABLE tiki_menu_options DROP KEY uniq_menu
Can't DROP 'uniq_menu'; check that column/key exists

ALTER TABLE tiki_menu_options ADD UNIQUE KEY uniq_menu (menuId,name(50),url(80),position,section(50),perm(50))
Duplicate entry '42-Newsletters-tiki-newsletters.php-900-feature_newsletters-tiki' for key 2

  1. 2007-07-18 sylvieg

ALTER TABLE users_users ADD valid varchar(32) default NULL
Duplicate column name 'valid'

  1. 2007-10-08 sylvieg

ALTER TABLE tiki_menu_options DROP KEY uniq_menu
Can't DROP 'uniq_menu'; check that column/key exists

INSERT INTO users_permissions (permName, permDesc, level, type) SELECT 'tiki_p_search','Can search', 'basic', 'tiki' FROM users_permissions WHERE @pcant = 0
Duplicate entry 'tiki_p_search' for key 1

ALTER TABLE users_users DROP KEY openid_url_1
Can't DROP 'openid_url_1'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_2
Can't DROP 'openid_url_2'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_3
Can't DROP 'openid_url_3'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_4
Can't DROP 'openid_url_4'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_5
Can't DROP 'openid_url_5'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_6
Can't DROP 'openid_url_6'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_7
Can't DROP 'openid_url_7'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_8
Can't DROP 'openid_url_8'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_9
Can't DROP 'openid_url_9'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_10
Can't DROP 'openid_url_10'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_11
Can't DROP 'openid_url_11'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_12
Can't DROP 'openid_url_12'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_13
Can't DROP 'openid_url_13'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_14
Can't DROP 'openid_url_14'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_15
Can't DROP 'openid_url_15'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_16
Can't DROP 'openid_url_16'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_17
Can't DROP 'openid_url_17'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_18
Can't DROP 'openid_url_18'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_19
Can't DROP 'openid_url_19'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_20
Can't DROP 'openid_url_20'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_21
Can't DROP 'openid_url_21'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_22
Can't DROP 'openid_url_22'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_23
Can't DROP 'openid_url_23'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_24
Can't DROP 'openid_url_24'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_25
Can't DROP 'openid_url_25'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_26
Can't DROP 'openid_url_26'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_27
Can't DROP 'openid_url_27'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_28
Can't DROP 'openid_url_28'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_29
Can't DROP 'openid_url_29'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_30
Can't DROP 'openid_url_30'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_31
Can't DROP 'openid_url_31'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_32
Can't DROP 'openid_url_32'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_33
Can't DROP 'openid_url_33'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_34
Can't DROP 'openid_url_34'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_35
Can't DROP 'openid_url_35'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_36
Can't DROP 'openid_url_36'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_37
Can't DROP 'openid_url_37'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_38
Can't DROP 'openid_url_38'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_39
Can't DROP 'openid_url_39'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_40
Can't DROP 'openid_url_40'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_41
Can't DROP 'openid_url_41'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_42
Can't DROP 'openid_url_42'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_43
Can't DROP 'openid_url_43'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_44
Can't DROP 'openid_url_44'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_45
Can't DROP 'openid_url_45'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_46
Can't DROP 'openid_url_46'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_47
Can't DROP 'openid_url_47'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_48
Can't DROP 'openid_url_48'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_49
Can't DROP 'openid_url_49'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_50
Can't DROP 'openid_url_50'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_51
Can't DROP 'openid_url_51'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_52
Can't DROP 'openid_url_52'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_53
Can't DROP 'openid_url_53'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_54
Can't DROP 'openid_url_54'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_55
Can't DROP 'openid_url_55'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_56
Can't DROP 'openid_url_56'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_57
Can't DROP 'openid_url_57'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_58
Can't DROP 'openid_url_58'; check that column/key exists

ALTER TABLE users_users DROP KEY openid_url_59
Can't DROP 'openid_url_59'; check that column/key exists

  1. 2008-08-18 sylvieg

ALTER TABLE users_users ADD pass_confirm int(14) default NULL AFTER challenge
Duplicate column name 'pass_confirm'

20081004_mindmap_menu_tiki:

  1. 2008-10-04 lphuberdeau

INSERT INTO `tiki_menu_options` (`optionId`, `menuId`, `type`, `name`, `url`, `position`, `section`, `perm`, `groupname`, `userlevel`) VALUES (197,42,'o','Mind Map','tiki-mindmap.php',255,'feature_wiki_mindmap','tiki_p_view','',0)
Duplicate entry '197' for key 1

posts: 1539 Canada

Hi!

All the "Duplicate" reports: no need to worry. In the old days, the upgrade script was not as smart as today, so there can be some harmless errors like this.

Maybe "Specified key was too long" will cause some issues. Just test all the features you use.

Best regards,

M ;-)

posts: 166 Germany

Okay, I could manoeuvre around the UTF-8 thing and the DB version warning in the admin panel: I dropped all tables and restored them from the old backup, then I wanted to redo the installation.

Installer somehow knew he wasn't starting from scratch anymore, and complained the DB had changed. I had it recycle the DB connection and made another upgrade.

This time installer did not complain about tiki_searindex not being UTF-8-ified (actually not mentioning UTF-8 at all, but in the end all tables were UTF-8), and gave me just the same SQL errors like before, which I quoted above. After completing installation admin panel never complained again.

So the Wiki is almost up and running. Still the admin is completely defunct, but I can work around with a priviledged user.

How do I repair the admin? I can log in as admin, but admin has less rights than anonymous... I checked the DB structure of the old Wiki. Admin is not group memeber in any groups, yet he has tiki_p_admin rights. Where do they come from? There isn't even a group for admins which would assign the rights.

Next I'll have to move images to file gallery, manually. I can move them from DB into the same directory where I want to place file gallery entries, but they are not recognized as such, so I guess I have to download them and reintegrate them.

And lastly I will have to reconstruct a Theme that I miss badly, geo-2. But that may be a longer task :-)


Upcoming Events

No records to display

Why Register?

Register at tiki.org and you'll be able to use the account at any *.tiki.org site, thanks to the InterTiki feature. A valid email address is required to receive site notifications and occasional newsletters. You can opt out of these items at any time.