Menu

#1063 More specific upgrading instructions desired

closed
nobody
5
2008-12-13
2007-11-03
svanslyck
No

The text at

http://localhost/phpmyadmin/Documentation.html#upgrading

currently says

" Simply copy ./config.inc.php from your previous installation into the newly unpacked one...."

I am really not quite sure what to do. I don't wish to create a "new" installation but to upgrade my current installation. I *think* what these instructions say is to:

First, Unzip/Unpack the installation file into a temporary location, e.g., C:\PHP\).

Second, Replace the ./config.inc.php file in the unpacked directory (e.g., C:\PHP\) with your current ./config.inc.php file.

Third, Copy all of the files in the temporary location, e.g., C:\PHP\) into your current php directory (e.g. C:\phpMyAdmin\)

Is this accurate and complete?

Discussion

  • svanslyck

    svanslyck - 2007-11-03

    Logged In: YES
    user_id=1928688
    Originator: YES

    See http://wiki.cihar.com/pma/Upgrading#Specific_Steps_-_Windows_Example . If you disagree with what I wrote there, please fix it. If you agree with what I wrote there, please consider incorporating my text into official documentation and README's. Thank you kindly.

     
  • Jürgen Wind

    Jürgen Wind - 2007-11-03

    Logged In: YES
    user_id=1383652
    Originator: NO

    >Second, Replace the ./config.inc.php file in the unpacked directory
    >(e.g., C:\PHP\) with your current ./config.inc.php file.
    Say "Copy your current ...." because there is no ./config.inc.php in the distributed packages.

    >Is this accurate and complete?
    There might be files in the old folder that are not needed any longer.
    Better delete the content of your old folder before moving the new files.
    You also have to empty all your browser caches to force a reload of the .js files.

     
  • Marc Delisle

    Marc Delisle - 2007-12-03

    Logged In: YES
    user_id=210714
    Originator: NO

    On Linux/UNIX we generally use symlinks to have a "generic" name like phpmyadmin that points to some directory. Therefore we can install many versions, test them, and point to the one we want for our users.

    On Windows, a sysadmin would want to test the new version, this is why a copy over the old directory is not a good idea (I also agree with windkiel's idea that there would be older files left).

     
  • Michal Čihař

    Michal Čihař - 2008-11-28
    • status: open --> pending
     
  • SourceForge Robot

    • status: pending --> closed
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • svanslyck

    svanslyck - 2008-12-13

    Yes, I think that's right. It's been a long time. If I recall corrrectly the idea was to replace all the old files with all the new files except for the config.inc file. <legalstuff>Your mileage may vary.</legalstuff>