Author Topic: Restore won't play  (Read 1388 times)

vtm

  • Posts: 19
    • View Profile
Restore won't play
« on: October 10, 2005, 06:01:26 am »
Hi Dean
My host moved sites from one server to another, and I can't seem to get the Restore working. (created by Backup/Restore)
Initially the login box wanted the 'install' password but then said the database has already been created so it could not complete.
So I installed a fresh copy of LM with a fresh database. The only difference was the password. It installed OK.
I uploaded the backup and changed the extension to .lm, but Restore could not see it. So I used the hosting control panel to restore the .lm file. Now I can't even log in, with either the old or new password - 'Incorrect password'.
What would you suggest?
Laurie

DW

  • Administrator
  • Posts: 3787
    • View Profile
    • https://legacy.listmailpro.com
Restore won't play
« Reply #1 on: October 10, 2005, 10:20:06 am »
Laurie,

Do you still have access to the old site/server/database?  You may want to do a manual backup using PhpMyAdmin (as per this post) to make sure all the data is there.  There is a test feature to warn you of missing data in the latest ListMail release available from the members area.  ListMail backup files are simply plaintext MySQL "dumps" of the database data.

To restore: Set up a MySQL database, username, and password on the new host; set up this information in ListMail's config.php; then import your data using ListMail (*.LM) or PhpMyAdmin's "SQL Query" command.  If all is done correctly you should be able to login with the OLD/restored password.

The problem with the filename could have been that the extension was lowercase, ie .lm instead of .LM.  On Linux, filenames are case sensitive.

Regards
Dean Wiebe
ListMailPRO Author & Developer - Help | Support | Hosting

vtm

  • Posts: 19
    • View Profile
Restore won't play
« Reply #2 on: October 11, 2005, 04:18:03 pm »
Thanks Dean

The .LM rather than .lm made the file visible, but clicking it didn't seem to do anything. Upgrading from v 1.83 to v1.84 seemed to do the trick.

Laurie