you need to run yourdomain.com/upgrade.php and that should fix it.

thanks for the reply Cim, but I done that but still nothing

Are you trying to load the back up in the same host or on a different machine?

Different machine

Read http://docs.elgg.org/wiki/DuplicateInstallation

Thanks a lot Team Webgalli, the problems was that I didn't export the database. I was using the backup from the host thinking that was it !! Thanks again.

Hello,

I need tips in restoring my site. Upon restoring my site from a backup (that is, loading the backup into the same host), all my plugins on the dashboard were all busy. They cannot display the contents from the database. But when I click and go to any particular plugin page (say, groups), the contents are displayed.

Any ideas on how to resolve this problem? Thank you very much in advance.

@brotherbrix - Are you on 1.7? By "busy" do you mean they got stuck with the loading icon (an animated "e")? If so, it means you have a JavaScript problem. Did you run upgrade.php?

@Brett, Yes, I'm on 1.7. And thank you very much. The upgrade.php resolve my problem.

However, that is only the start of my problem. My concern now is how to update to 1.8. I revert to my backup copy (version 1.7) because the site crashed when I made the update. The main reason could be because I customised my 1.7 directly on the source codes. But I'm not sure. It's a bad idea but I was new to Elgg then. Now that I have the book "Elgg 1.8", I want to do the right way.

So, the question is: How do I move to 1.8 version while (1) keeping the contents (like the users, their discussions, etc.) from 1.7, and (2) identify the customized source codes so I can create a separate plugin(s).

Any tips to go about this process is highly appreciated.

Thanks in advance!

The content (database) will be automatically upgraded for you when you run upgrade.php, so you don't need to worry about that.

The easiest way to figure out the differences between your files and stock files is to download the version of Elgg you modified and compare those files with your live files using a diff tool. Once you've identified the changes, you can start to pull them out into a plugin that will work on 1.8.