Help!

I have been using XOOPS for some years now and have recently had to restore my databases from a backup.

I have in the past used MySQL dump to back them up to another offsite server.

I needed to restore my site and found corroupt data. Unfortunatly this also included some of my backup files. The tables I have managed to save are the user table and stories table (using the stores module).

The stories which I extracted I have been able to restore using sql commands. The users appear to be restored and I have made links in the user_linking table that appear on browsing to be correct.

When I search for all users the only use that XOOPS can find is the admin user I created when reinstalling on my server even though the information for my other users appears in the tables XOOPS does not recognise this. I have been looking around the dbs thinking it may be to do with activateion but I have been unable to find anything which stands out.

Has anyone got any ideas about why XOOPS is doing this I am using version 2.0.10 with a debian install and the most up to date version of MySQL with apt_get (I don't have the verson number at present).

Any help would be appreciated.

Cheers

Sally

Don't know about your current problem, but take a look at this article: Regular Database Backup with Cron(updated) Shows a mysqldump script I have tested on my site for full database restores. Another article there dealing with the restore process.

So far in testing (and with the update added this weekend to the script) it seems to work well. I use cron to do a backup every day, and keep 7 days worth available. This way if a major crash I only loose a maximum of one day of data.

Thanks for your thoughts on that I was using cron to backup to a friends isp, he took the machine I was backing up to offline to revamp it and silly me (because I was sick of cron emailing every day) had piped it out to dev null.

I need to set that up again, saving seven days sounds like an awesome idea.

Do you know how the user activation works? That I think may be a key part of this.

No, as I stated above I do not. Plus I noticed that you are using version 2.1.1 on your site. This is a development version, and I believe the way users are handled has changed some, due to the extended profiles module included. So in fact this could be a problem with the XOOPS beta. But I will let a developer answer that.

As stated with the 2.1.1 release, it should not be used on production sites, unless you want to test it. But as with all betas it is best to test on a non production site as some bugs may cause data and functionality loss. Better to use the stable 2.0.10 on production sites, and 2.1.1 on a test site.

OK with a little fiddling around I have been able to search for users by populating the table xoopsdb_user_profile with incrementing id numbers and a table size matching the number of users. - I am getting there.