Serendipity Forums

Hi everyone,

I have enough of Textpattern and want to migrate to another software. S9Y seems the right system for me. I installed it and wanted to use the TXP importer, but it does not work for me.

My problem:

TXP DB-Server: mysql.my.domain.xy (MySQL 3)
TXP DB: db98983
TXP user: db98983
prefix: txp_
S9Y DB-Server: mysql5.my.domain.xy (MySQL 5)
S9Y DB: db98983_5
S9Y user: db98983_5

First try: import directly from my TXP DB (MySQL 3), but then I get the following error

Import fehlgeschlagen: Die Benutzerinformationen von Access denied for user: 'db98983@localhost' to database 'db98983_5' konnten nicht gelesen werden.

Nexy try: import the TXP database into my S9Y database via phpmyadmin and then import using the new userdata gave the following error:

Import fehlgeschlagen: Die Benutzerinformationen von konnten nicht gelesen werden.

So what to do now? The first error-message seems strange for me, since it obviously mixes up the two databases. Then my TXP version is 4.0.1 and not 1.0 RC1. May this be my problem?

I also renamed my S9Y Admin username, so it differs from the TXP one, no help.

Is there any documentation how the importer works? I searched bud didn't find anything.

Greets, Dr. Love

The only info you should have to put inside the importer is the database host, database user, database password, name, and table prefix for your TextPattern...so your s9y database/username/pass is water under the bridge and we shouldn't worry bout it.

Next, make sure your CHARSET is right. I converted a friend from wordpress and had to switch from UTF-8 to ISO-8859-0...I received access denied errors until I changed the charset. Give that a try and see what happens.

Also, I gave my user for s9y temporary access to the wordpress mysql tables...full access just to be safe. After the import, I changed it back. Perhaps this could help?

Hi!

It might very well be that TXP 4.0 has a different structure. I didn't know they make a 4.0 version jump in only less than a year :-O

Anyways - the problem when you get the "Could not select user info" is when this SQL DB query fails from the importer:
So check what you entered in the importer as prefix to your TXP DB and if tha prefixtxp_user Table exists and has the fields that are mentioned in the SELECT statement?

Also, in the importer you need to enter the DB access data that s9y needs to connect to the target DB: In your first try this didn'T work because often the MySQL DB is only accessible from localhosts, and not all hosts. So copying it to your local s9y database was a very good idea!

There you should only need to enter the DB access data that you also entered for Serendipity. Only the prefix will differ there.

As I mentioned, check if that table above exists. If not it would help me if you could show me the part of your SQL dump, then I will patch the importer code so that it works.

I can promise you we will work this out.

Best regards,
Garvin

garvinhicking wrote: It might very well be that TXP 4.0 has a different structure. I didn't know they make a 4.0 version jump in only less than a year :-O

I installed this version in September 2005, so there was a version-jump in just three months Don't ask me, TXP isn't any transparent for me.

Code: Select all

FROM {$this->data['prefix']}txp_users

That was the problem: I missunderstood the prefix thing. When I do not enter any prefix, it works great, so you do not see the txp_ prefix as a prefix, but I did.

Also, in the importer you need to enter the DB access data that s9y needs to connect to the target DB: In your first try this didn'T work because often the MySQL DB is only accessible from localhosts, and not all hosts. So copying it to your local s9y database was a very good idea!

I know, my hoster is very srict, but S9Y works on the same webspace, the SQL-servers differ because I can choose between MySQL 3, 4 and 5 and they are addressed via their subdomains. So the access rights are the same.

I can promise you we will work this out.

You are right Thanks.

Hi!

Ah, great. Actually the way how TXP prefixes their table is strange, because "txp_" is fixed, and usually you would think that is their Prefix! But if you choose to install TXP with the "txp_" prefix, your tables would end up with "txp_txp_"

Best regards,
Garvin