For the index, can you loggin with SSH to your server? When yes, go in the shop root, then in the folder “shell” and type “php -f indexer.php reindexall”. Sometimes this helps when the index cannot refreshed in the admin panel.
Broken indexes are a big problem, i`ve saw this dozends of time....there`s a official database repair tool, i would try it.
Link: http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/db-repair-tool
There`s also a new untested version on the site.
I have tried to repair the database as what you said but the reindex problem is still there, but the good news is the links what I said in my first post is ok now.
So do you have any other methord to solve the reindex problem, please?
Hmm, i would try to debug the index process an find the element(s) which has the failed foreign key constraint and delete them...but that`s not done in a few minutes.
Yes, I also think it’s foreign key problem. When I migrate the database, some docs said I should choose “disable foreign key check” but I have not choose that item so the data base always have the problem.
Another problem for my magento is the old order records has not products details and have not “ship” item for each order, if I re-export the database with “disable foreign key check”, do you think everything will be ok, please?
Try it, backup the database, and reimport the database with disabled foregin key check and test the system, the index, and so on. But don`t forget save a backup.
I am considering if I export the data from now database with “disable foreign key check” and delete the database and import the backup, do you think I can solve the problem?
I want to do because we have about many new orders base on old database, so I want the above methord, do you think it’s workable, please? Or I have to export the old database to try?
When you dump with phpMyAdmin, you can add the “disable foreign key check” option to the dump. That means, that the dump runs normally und when you re-import the database (clear before) with the dump, the dump ignores the foreign key check during the import.
I install a new magento on other domain but when I import the database by phpMyAdmin, it show one error and I find there is any data imported.
I have attached the error picture, could you check that for us, please?
By the way, about the price reindex problem, if we don’t consider that, it will be fatal problem, please? If it’s not big problem, I want to keep this because I can’t find better methord to solve that.
I have not delete the old table, I just think the new import database could cover the table. Should I delete old table and import the database, please?
If so, I think it’s no need to reinstall the blank Magento, is that right?
Today, I also tried another methord, which I copy all old server files and import the database to blank database and everything is ok but the problem is when I visit the new domain, it redirect to http://www.herawigs.com and I tried many methord to solve that but can’t work so I decide to install one blank Magento. Do you have any good idea to solve the redirect problem what I said, please?
