File exists and contains non-aMember code unmodifiable by aMember

Discussion in 'Setting-up protection' started by dimitri, Sep 19, 2009.

  1. dimitri

    dimitri New Member

    Joined:
    Oct 7, 2008
    Messages:
    6
    Hi,

    Here is the error message when I try to protect a new directory:

    File exists and contains non-aMember code unmodifiable by aMember. If you don't need this file, delete it and aMember will automatically create a new aMember compatible .htaccess file to replace it.

    .......

    I dont know what file I need to delete. I've tried to erase .htaccess but the result is the same.

    How to find this please ?

    The only one who have do something in files is the webhosting technical support when my website was infected with Trojan Gumblar. But I've never modify anything.
  2. davidm1

    davidm1 aMember User & Partner

    Joined:
    May 16, 2006
    Messages:
    4,437
    The directory already has a .htaccess file in it.
    Can you show us the contents and I can tell you if its ok to delete?

    David
  3. dimitri

    dimitri New Member

    Joined:
    Oct 7, 2008
    Messages:
    6
    Thank you for your offer.

    Here is the content of this .htaccess

    ............................

    <Limit GET POST>
    deny from all
    </Limit>

    ............................

    Nothing else... weird isn't it ?

    Is it the "normal" .htaccess in the data directory of Amember ?

    I want to protect my directories with .htpsword but I don't know what I need to do to let Amember create the good file .htaccess for that.

    Thank you again.
  4. davidm1

    davidm1 aMember User & Partner

    Joined:
    May 16, 2006
    Messages:
    4,437
    Are you trying to protect your amember directory? This is not to be done! It will create a loop.

    If this file is in a content directory, it can be deleted.

    David
  5. dimitri

    dimitri New Member

    Joined:
    Oct 7, 2008
    Messages:
    6
    Hi,

    No the directory I need to protect isn't the Amember directory but an other one.

    Dimitri
  6. dimitri

    dimitri New Member

    Joined:
    Oct 7, 2008
    Messages:
    6
    Amember is installed in the main domain in a multi-domains account. It was working perfectly for nearly 4 years but in july we had a Trojan attack (Gumblar) and our technical support had work on our account to clean it and protect it more. But now we have a new product to add and this product is available in a new directory and I can't protect it.

    But all other protected directories are well protected with .htpasswd without problem.

    Dimitri
  7. davidm1

    davidm1 aMember User & Partner

    Joined:
    May 16, 2006
    Messages:
    4,437
    I believe the htpasswd protection will also place an htaccess file in the directory.

    David
  8. dimitri

    dimitri New Member

    Joined:
    Oct 7, 2008
    Messages:
    6
    ok but...

    If it will create this file, why Amember send me this error message ?

    Here is the error message when I try to protect a new directory:
    ..............

    File exists and contains non-aMember code unmodifiable by aMember. If you don't need this file, delete it and aMember will automatically create a new aMember compatible .htaccess file to replace it.
    ..............

    I try to find where and what is this "non-aMember code unmodifiable by aMember" to delete it and let aMember do what it is suppose to do but I don't find it. How to find it please ? Where to find this code "unmodifiable by aMember" ?

    Dimitri
  9. dimitri

    dimitri New Member

    Joined:
    Oct 7, 2008
    Messages:
    6
    Thank you for your help. The technical support of aMember have done the work for me and now the directory is well protected. Thank you again for your time.
  10. skippybosco

    skippybosco CGI-Central Partner Staff Member

    Joined:
    Aug 22, 2006
    Messages:
    2,526
    @dimitri: Just in case others run into this issue in the future, can you confirm that aMember support just replaced the .htaccess in your folder with an aMember specific one
    (ie. deleted the one previously and then protected via aMember)

Share This Page