Fork me on GitHub

Existing Installation Detected where there is none  Bottom

  • Hi there,

    I have a very strange bug when installing MS1 from either the release or the latest snapshot.

    I uploaded the installation into a folder on my web server as ./website/

    I go through the installation wizard and can create the SQL tables, enter passwords etc, but when I select the theme (doesnt matter which) it throws up a screen with this error: -

    Quote

    We detected an existing installation. You must log in as the Administrative user to proceed.


    If I type in the user name and password it just goes back to the beginning of the installation and repeats the message over again.

    Now here is the bit I REALLY am confused about, If I rename the folder it is installed in to something like ./PN800/ , drop all tables and re-upload the config folder, It works fine and I can install OK!

    But if I then repeat the process and revert back to ./web/ or ./www/ it gives the same error as before.

    It may sound silly but I have tried this backwards and forwards multiple times and still find that certain directory names are OK while others throw the error.

    I dont have root access to my server since I work for a school and it is hosted by the local authority but its running Apache 2.0.52, PHP 4.3.9 and MySQL 4.1.20.

    I know this isn't a support forum but any clues as to where to look would be appreciated!

    Codeus
  • The existing installation detection is based on a setting in config.php. The setting is changed when an install is completed. For additional security to perform another install this must be reset. Either reset the installed flag in config/config.php or re-upload a fresh copy.

    -Mark

    --
    Visit My homepage and Zikula themes.
  • Hi Mark,

    Thanks for the response.

    I mentioned in my original post that I have re-uploaded the config files each time but am still getting this problem with some folder names, i have also dropped all SQL tables and cleared cookies on the client etc.

    As I mentioned, the installer works fine until I hit 'next' on the theme selection stage (the last stage of installation) - before that point it doesnt consider it an 'existing installation'. The moment I hit next it gives the message I quoted.

    Also: I failed to mention, along with the 'Existing Installation' message it also says 'Failed to login, please check and try again.' and presents me with an Administrative User login box which just takes me back to the start.

    Does it automatically login after the install completes? Perhaps this is where my problem is coming from. But why with some directory names and not others?

    I am wondering if the webserver has a screwy config someplace.

    Cheers,

    Codeus


    markwest

    The existing installation detection is based on a setting in config.php. The setting is changed when an install is completed. For additional security to perform another install this must be reset. Either reset the installed flag in config/config.php or re-upload a fresh copy.

    -Mark





    edited by: Codeus, Aug 22, 2006 - 01:38 PM
  • I don't understand what you mean by 'but am still getting this problem with some folder names;' The directory to which PN is installed has no bearing on the existing install check.

    The existing installation detection is a simple check for $PNConfig['System']['installed'] in config/config.php. If this is 1 then the installer prompts for the admin account from the earlier install (based on the database settings in the same config file). If 0 then installation procedes as a new install.

    -Mark

    --
    Visit My homepage and Zikula themes.
  • Lets say I do a clean upload to ./mywebsite/ and place all files under there. When I get to the end of the installation I get the error messages, 'Existing installation found', 'Failed to Login'.

    Now if I upload to ./pn800/ or some other folder names and place all files under there it works fine, installation completes fully with no probs!

    Absolutely no difference apart from the it works when installed in folders of certain names and not in others. I understand what you are saying that this is irrelevant to the existing installation check but this is what is happening.

    For example I tested these directory paths for installation: -

    ./ - Error
    ./web/ - Error
    ./www/ - Error
    ./site/ - Error
    ./pn800/ - Success
    ./A500/ - Success
    ./A50/ - Success
    ./A5/ - Error
    ./A5W/ - Error


    As I mentioned, it could be something misconfigured on the server. I was having login problems with 762 too.

    But because it's such an odd-ball problem I don't really know where to start looking. icon_frown

    Kind regards,

    Codeus
  • Based on the the way the code works that doesn't make sense. There must be something else going on... Sorry but I can't suggest anything else - this one is down to you to debug icon_wink

    -Mark

    --
    Visit My homepage and Zikula themes.
  • Hi,

    Have the exact same problem. And I hardly doubt it is a server issue, and if so, it should not create such a big problem. The only thing I can think of while not having tested it, is external DB connection not working properly. The DB is populated, but I'm not sure stuff is read back.

    Not the best first impression of .8, but nothing is perfect ;)

    // Edited
    I dropped DB and rebuilt by manual run which made me able to use PN. Since the bug using the graphical installer is in the last phase it should be possible to narrow it down. It seems to me

    that the installer script may set 'installed' to 1 to early, causing the conflict we expirience...





    edited by: aase, Oct 01, 2006 - 10:39 PM
  • Do you have a personal_config.php?

    --
    itbegins.co.uk - Zikula Consulting

    birtwistle.me.uk - Personal Blog


    Please read the Support Guide
  • At the last phase I had the similar problem with the graphical interface... Site seems to be up and running...

    I do have an error log 546k big, created by PN... anyone interested..?

    - Igor
  • I had the same problem using a wampp server. I have no idea what is the reason for this but in my case the problem disappeared after switching from php5 to php4 . With php4.4 it worked fine.



    edited by: pasokonkun, Oct 02, 2006 - 10:26 PM

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