WordPress.org

Ready to get started?Download WordPress

Forums

Visitor Maps Extended Referer Field
[resolved] Upgrade to version 1.1.1+ problems (5 posts)

  1. President McCheese
    Member
    Plugin Author

    Posted 2 years ago #

    If you experience problems with your website after updating from older versions, simply restore the .htaccess file from the file .htaccess.backup, which is locate in the root WordPress folder. Then, deactivate/reactivate Visitor Maps Extended Referer Field. There was a bug which may have caused htaccess to be improperly written.

    If you continue to experience problems, contact me for help.

    http://wordpress.org/extend/plugins/visitor-maps-extended-referer-field/

  2. FidoSysop
    Member
    Posted 2 years ago #

    Just a FYI: I just tried installing this plugin on another blog. When activating i got the following error: Visitor Maps Extended could not backup /home/content/53/9530553/html/naru/blog/.htaccess. The installation was terminated.

    Maybe a check is in order to see if an .htaccess exists in the blog home directory, and if one is not found continue the installation. I have my .htaccess file in the hosting account root so it denies access to other services running, besides WordPress.

    I think this plugin and especially the latest addition of IP and Referrer blocking is a great addition. Keep up the good work!

  3. FidoSysop
    Member
    Posted 2 years ago #

    Forgot to say i created a blank .htaccess to continue the installation. The plugin activated fine that time.

  4. President McCheese
    Member
    Plugin Author

    Posted 2 years ago #

    I made it so it would throw that error if there was no htaccess present in the root WordPress folder. This plugin relies on htaccess for banning IPs and referers. In the future, I will make an option so you can customize the path to htaccess, or write to multiple htaccess files at once.

    Thanks for your input!

  5. FidoSysop
    Member
    Posted 2 years ago #

    I would suggest just sticking to writing to a .htaccess within WordPress. Writing to an existing .htaccess in the hosting account's root could possibly hose something else up.

    While we understand .htaccess many of the others who run WordPress do not.

    Just my two cents worth :)

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.