Error with plugin

Warning: fopen(/index.php) [function.fopen]: failed to open stream: Permission denied in /www/snapblogger.com/wp-content/plugins/snapshot/lib/snapshot_utilities.php on line 842

Warning: fopen(/.htaccess) [function.fopen]: failed to open stream: Permission denied in /www/snapblogger.com/wp-content/plugins/snapshot/lib/snapshot_utilities.php on line 849

  • Jason
    • The Incredible Code Injector

    sounds like your permissions for the files are set too strict.

    In your ftp client try setting the permissions to 755 and see if you still get the same error.

    I would set them on the plugin folder by right-clicking on "snapshot" folder under wp-content/plugins and click on properties (depending on your ftp client) and then adjust the permissions there.

    Let me know how it goes!

  • Jason
    • The Incredible Code Injector

    As a sidenote to the developers.

    It's IMO that plugins should never create files. The files should just be included in the archive with the plugin.

    I use nginx, as do many others, and .htaccess files serve no purpose.
    Creating it is a waste of cycles and bloat on the plugin. Granted it's hardly any bloat at all, but a little here and a little there doesn't make for a healthy diet.

  • aecnu
    • WP Unicorn

    Greetings Snapsean and Jason,

    @snapsean We have not heard back from you as to the status of this issue.

    If you are still having an issue please let us know so that we may try to get you fixed up as soon as possible by choosing to check mark this ticket as unresolved below and posting any new errors or symptoms you are noticing.

    This action will also bring your ticket up front back in plain view again within the ticket system.

    @Jason htaccess rocks the world and the ruler of the domain. Nothing beats the versatility and capability of this little file when applied correctly. Have doubts? Check out and stay tuned for my upcoming article about htaccess that will be announced soon.

    It may have no use in the by far minority nginx world, but in my Apache world it is rocking the paradise.

    Thank you both for being WPMU Dev Community Members!

    Cheers, Joe

  • Jason
    • The Incredible Code Injector

    @aecnu

    Dude, no doubt there is "Powa" in .htaccess, and anyone who's a spiderman fan knows, that with great power comes great responsibility.

    Truth be told, .htaccess offers less flexibility than nginx configs, and poses serious security risks, and impacts to performance. So much so, that even the apache devs have admitted it as one of their biggest challenges on improving apache because it's the best way to delegate rewrite rules.

    A quote from Apache's documentation is appropriate here: You should avoid using .htaccess files completely if you have access to httpd main server config file. Using .htaccess files slows down your Apache server. Any directive that you can include in a .htaccess file is better set in a Directory block, as it will have the same effect with better performance. –

    (Taken from ) http://httpd.apache.org/docs/current/howto/htaccess.html

    Apache knows how bad and abused the .htacees can be. They only provide it because it's easy for people to use if they don't have control over their apache's config files (Like on a shared host)

    Here's a great article from a real expert on the issue. http://cwells.net/2012/03/27/why-doesnt-nginx-support-htaccess-files/

    Note the first comment as well. It's a really good read, and was an eye opener for me as well.

    I'm not reopening the issue, just inviting a discussion about these files and trying to raise awareness that almost every web developer needs to get caught up on.

  • aecnu
    • WP Unicorn

    Greetings Jason,

    This is a pretty cool subject.

    A quote from Apache's documentation is appropriate here: You should avoid using .htaccess files completely if you have access to httpd main server config file. Using .htaccess files slows down your Apache server. Any directive that you can include in a .htaccess file is better set in a Directory block, as it will have the same effect with better performance.

    Absolutely agree, and how many of these people actually have access to the httpd main server config file (httpd.conf)? Only those with Dedicated servers and possibly some but very few VPS servers. Otherwise it ain't happening.

    In addition, if it is such a security risk, then I challenge anyone who wants to try and break it to do so without extra retribution from me that my servers will dish out to you for trying anyway ... lol ... : http://aecnuwpmu.us

    The hole --> try and access the htaccess file and/or do a security breach on the URL above.

    I agree that it is better to add the commands to the httpd.conf file rather then htaccess files, but not for security purposes but for performance because then the commands is native to Apache from start up.

    Actually compared to consumers themselves, htaccess is the least of my worries when it comes to security or performance problems.

    Cheers, Joe

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.