Hi all,

I have just recently moved a site to a new server. I used XOOPS DB Backup & Restore 3.0 to back up the db. Dumping the whole db was out of the question due to two tables, so I dumped each table separately (all 84).

The two problematic tables where bb_posts_text and protector log (error messages listed below). Researching the issue I found that many had had the same problem with the bb_posts_text table and they all found their own creative ways to get around the issue. I used the source from the modules to create the tables, then dumped the data.

I don't think this is an issue with the integrity of the back up file or method (i.e.: manual import through phpmyadmin, gzip, or SQl) as I and others have tried many methods and seem to have problems with the same tables.

My Question: Is it possible to edit the code in the modules that produce the problematic tables or the code in XOOPS DB Backup & Restore to provide an entire db dump?

This one's over my head as I'm not a programmer and weak with mysql. I just read/test/anguish for each and every problem.

Thanks for any advice/help in advance.

Steve

Errors:




*/

EDIT: Forgot to add: PHP 4.4, XOOPS v2.0.16, Protector v2.57, Multimenu v1.74, Document Management Systems (DMS) v1.87, CBB v3.08, DLinks v1, Formulize v2.2, Pageworks v2.2 and Multi Theme Hack.

Most likely you are encountering differences in the MySQL versions (old site v. new site).

If you compare the sql from your backup to the sql for the table creation in the modules, I will wager you will find differences in how the fields are defined when they are created.

As for the tables you had problems with - the bb_posts_text table would certainly be one to import to your new site, since it contains content for your forums, but the protector_logs table could be dumped.