Installation, Configuration, & Upgrades  :: 
Question about Database Restoring
 Top

  • Hi all,

    I recently lost my entire site due to a server error (not using that host anymore!), the last time I backed up (I know this was bad ... but life took all my time) was in October when I had version .71 o .72 (can't remember)... so here's my question.

    If I were to install the newest release on my new server and then were to restore the weblinks table (the only one that really matters to me) ... would this work? Or were there additions to the weblinks table that would make it impossible for me to restore my old database onto the new release?

    Thanks so much for your help!!

    PS. The email in my profile was tied to the site that's down ... I can't seem to change it ... keeps telling me my password is wrong ... the point is ... don't email me I won't get it!
  • I just checked the 6 weblinks tables:

    • [prefix]_links_categories
    • [prefix]_links_editorials
    • [prefix]_links_links
    • [prefix]_links_modrequest
    • [prefix]_links_newlink
    • [prefix]_links_votedata)

    and compared the tables between one of my sites that is running .723 and one that is running .714 and they look to be exactly the same, so you should be fine. Let us know what happens.
  • If you've got .714, you should be able to just upload the old database, then upload the new files and run the upgrade process.

    I'd suspect that if you upload your database and the upgrade fails, you could just clear the database and run the .72 upgrade.
  • If you saved the tables correctly, you should be able to inject what you want pretty easy with phpMyAdmin.

    If you open your SQL for the site in an editor I use CuteFTP for this, look for...

    Code

    #
    # Table structure for table `nuke_links_categories`
    #

    DROP TABLE if EXISTS nuke_links_categories;
    CREATE TABLE nuke_links_categories (
      pn_cat_id int(11) NOT null auto_increment,
      pn_parent_id int(11) default null,
      pn_title varchar(50) NOT null default '',
      pn_description text NOT null,
      PRIMARY key  (pn_cat_id)
    ) TYPE=MyISAM;

    #
    # Dumping data for table `nuke_links_categories`
    #


    this part above, and everything below it as Raleigh has posted are the ones what you want. Down to where the next table starts. not having to do with links_

    which should be table `nuke_message`

    depending on the size of this specific amount of data, you may be able to inject it all at once, if you did it in parts just make sure you keep track of where you started and stopped while highlighting to copy and paste into phpMySQL.

    --
    Friends rock, bullshit walks
  • Thanks to you all :) I'll get to play with this over the weekend and see if I can restore all my hard work :)
  • Okay I have only one problem left:

    I get this error above every one of my news posts:

    Code

    Warning: Invalid argument supplied for foreach() in /home/taleria/public_html/includes/pnAPI.php on line 828


    http://www.taleria.net/index.php

    See what I mean?

    Any ideas?
This list is based on the users active over the last 60 minutes.