• martinjt

    (@martinjt)


    Hi,

    I am receiving the below error:

    _____________________________________________________
    The Adaptive Images settings are saved, but the .htaccess file was not able to be updated yet.
    Please try to save the plugin settings once again in Adaptive Images Settings. If the problem persists, then you should contact your system administrator and inform them about the issue.
    The .htaccess file permissions are: /opt/bitnami/apps/wordpress/htdocs/.htaccess => .

    _________________________________________________-

    When I attempt to find the file on the server itself I am unable to do so in the given path.

    I am running a pre-built Bitami image on Amazon’s EC2 cloud.

    When I apply setting I get the below:

    _____________________________________________
    Adaptive Images — Settings updated.
    The settings have been saved in the database.
    The .htaccess file could not be updated. This probably means a filesystem error or a permissions problem: /opt/bitnami/apps/wordpress/htdocs/.htaccess => .
    Consider adding this code to your .htaccess file manually:
    # BEGIN Adaptive Images
    #=======================

    <IfModule mod_rewrite.c>

    RewriteEngine On

    # Watched directories
    RewriteCond %{REQUEST_URI} /wp-content/uploads [OR]
    RewriteCond %{REQUEST_URI} /wp-content/themes

    # Redirect images through the adaptive images script
    RewriteRule \.(?:jpe?g|gif|png)$ /wp-content/plugins/adaptive-images/adaptive-images-script.php [L]

    </IfModule>

    # END Adaptive Images
    User settings file could not be updated. This probably means a filesystem error or a permissions problem./opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/adaptive-images/user-settings.php => .
    The plugin will still be able to function but with its default settings until this problem is resolved.

    __________________________________________________

    I also attempted to find the referenced user-setting.php file but that was also not where it is indicated.

    https://wordpress.org/plugins/adaptive-images/

Viewing 15 replies - 1 through 15 (of 19 total)
  • Thread Starter martinjt

    (@martinjt)

    Here is the Debug info:

    ____________________________________________________

    Debug info
    ✔ PHP GD library is installed.
    ✖ Image cache directory has not been created.
    It seems that the directory is not writeable. This is probably a filesystem permissions issue.
    Consider adding manually the image cache directory: “/wp-content/cache/adaptive-images”.

    /opt/bitnami/apps/wordpress/htdocs/wp-content/cache =>
    ✖ Installation .htaccess file is not properly setup.
    The .htaccess file is not writeable so it might have not been updated.

    /opt/bitnami/apps/wordpress/htdocs/.htaccess =>
    ❖ Adaptive images settings dump:
    array(12) {
    [“resolutions”]=>
    array(9) {
    [0]=>
    int(1920)
    [1]=>
    int(1536)
    [2]=>
    int(1334)
    [3]=>
    int(1136)
    [4]=>
    int(1080)
    [5]=>
    int(960)
    [6]=>
    int(750)
    [7]=>
    int(640)
    [8]=>
    int(480)
    }
    [“landscape”]=>
    bool(true)
    [“cache-directory”]=>
    string(21) “cache/adaptive-images”
    [“watched-directories”]=>
    array(2) {
    [0]=>
    string(18) “wp-content/uploads”
    [1]=>
    string(17) “wp-content/themes”
    }
    [“jpeg-quality”]=>
    int(75)
    [“sharpen-images”]=>
    bool(true)
    [“watch-cache”]=>
    bool(true)
    [“browser-cache”]=>
    float(30)
    [“hidpi”]=>
    bool(false)
    [“cdn-support”]=>
    bool(false)
    [“version”]=>
    string(6) “0.6.42”
    [“sanitized”]=>
    bool(true)
    }

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello there,

    Thank you for your thorough report!

    It seems that the Bitnami image has some paeculiarities. Perhaps you could help me investigate them?

    1) Is the VM using an Apache installation? If not then what is it? Is in NginX? If so then this is a very special case!

    2) If the .htaccess file is not in /opt/bitnami/apps/wordpress/htdocs/ then where is it? It has got to be somewhere! What is the root directory of your WordPress installation?

    3) Same as in 2 goes for the /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/adaptive-images/user-settings.php file. If it is not where it is expcted then something unusual is going on with the directory structure in your installation.

    Cheers,
    Takis

    Thread Starter martinjt

    (@martinjt)

    Yes, I can try to assist but I’m by no means a subject matter on this. I just started to pick all this up so if you can bare with me I can try.

    1) I see an Apache folder so I would imagine it’s safe to say it is Apache.
    /opt/bitnami/apache2

    2)No clue on either point. How can I tell? I can say for certain that the .htaccess file is not present here: /opt/bitnami/apps/wordpress/htdocs/. What I do see are numerous files and three WP folders, admin, content and includes.

    3) No clue, what I do see there are 9 adaptive-images-xxx.php files, index.php, licence, readme,todo and uninstall. This is the path i am looking at, to confirm I’m not seeing something incorrectly. /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/adaptive-images

    Thread Starter martinjt

    (@martinjt)

    I found this in the changelog so it looks like apache for certain: Apache to 2.4.18
    Version 4.4-0

    Here is some more, albeit older info; I figure it might provide good info as to what is running:

    Updated Apache to 2.4.18

    Version 4.4-0 2015-12-09
    * Updated WordPress to 4.4
    * Updated MySQL to 5.6.28
    * Updated OpenSSL to 1.0.1q
    * Updated phpMyAdmin to 4.5.2

    Version 4.3.1-1 2015-11-17
    * Updated libpng to 1.5.24 (security issue)
    * Fixed minor issues setting permissions
    * Updated Varnish to 4.1.0
    * Updated MySQL to 5.6.27
    * Updated Apache to 2.4.17

    Version 4.3.1-0 2015-09-16
    * Updated WordPress to 4.3.1
    * Updated PHP to 5.5.29

    Version 4.3-0 2015-08-19
    * Updated WordPress to 4.3.0
    * Updated phpMyAdmin to 4.4.13.1
    * Updated PHP to 5.5.28

    Version 4.2.4-0

    Plugin Author Takis Bouyouris

    (@nevma)

    Ι suspect that the Bitnami installation has very strict filesystem access rights, which does not allow PHP code to write files in directories other than /wp-content/uploads.

    1) Have you tried saving your permalink structure with pretty permalinks? If that doesn’t create the .htaccess file, then the problem is most certainly the filesystem access rights. You either need to change them or create the .htaccess file manually!

    2) Can you check and see what the filesystem access rights actually are in your root directory?

    Thread Starter martinjt

    (@martinjt)

    Hi,

    I don’t see anything that’s described as “pretty” within the permalinks section. Right now i have “post name” selected. Interestingly enough, I noticed that there is a small blurb almost at the bottom of this section, above a small box with some code. It says the following above the box with the code:

    —————————————-

    If your .htaccess file were writable, we could do this automatically, but it isn’t so these are the mod_rewrite rules you should have in your .htaccess file. Click in the field and press CTRL + a to select all.

    ——————————————-

    I’m going to see if I can open a case with Amazon Cloud Services in the meantime. I might be able to figure out how to modify the permissions if I could even find the file! 🙂

    Plugin Author Takis Bouyouris

    (@nevma)

    Yes, this is what we call “pretty” permalinks. Forgive me for using the internet slang! All in all it seems that the problem is indeed your filesystem access rights.

    Let me know how it works out for you!

    Cheers,
    Takis

    Thread Starter martinjt

    (@martinjt)

    Plugin Author Takis Bouyouris

    (@nevma)

    Well, it seems that there is a whole set of sys-admin steps you need to follow to make the necessary changes. But, from what it seems, it should work!

    Thread Starter martinjt

    (@martinjt)

    It would seem there have been some significant changes to how the WordPress is deployed. I’m using a pre-configured image, or AMI, from Amazon’s EC2 which incorporates all these changes. I have spent a lot of time reading and trying to follow instructions but if there is anything out there that provides instructions on how to overcome the limitation I’ve encountered I cannot find it.

    This is what I found on Bitnami, talking about the deployment and configuration of their image and how it impacts the htaccess conf file in particular.

    The odd thing is that even though I see the following message on the permalinks page, “If your .htaccess file were writable, we could do this automatically, but it isn’t so these are the mod_rewrite rules you should have in your .htaccess file”, it must somehow still be doing so, writing the changes some place, because the “pretty” permalinks works when I change the setting, to that or any other.

    Thread Starter martinjt

    (@martinjt)

    Plugin Author Takis Bouyouris

    (@nevma)

    Well, I believe the first link you mentioned http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/hosting-wordpress.html has the solution to your problem. It does require system administration knowledge to do what it instructs of course.

    The second link, the one from Bitnami, is only useful once you have managed to setup an .htaccess file via WordPress or manually.

    However this is not a WordPress “per se” problem. It is a system requirement for WordPress to function as expected and you should get help from a system administrator on this.

    Thread Starter martinjt

    (@martinjt)

    I agree, I would say it’s not a WP issue, I believe it might be better said that the issue has to do with how it was deployed in this instance.

    I tried to follow all manner of tutorials but all of them led to dead ends because files/folders simply were not where they ought to be.

    As to link you referred to, I looked at it but that speaks to setting up WP from scratch and what I have is a pre-configured image. As such, I may need to scrap the whole server and start again but for now, it will stay that way. Thanks for your help in any case.

    Plugin Author Takis Bouyouris

    (@nevma)

    Glad to be of help!

    However, in the link to the Amazon docs, I believe you only need to follow the last part of the instructions, the one that refers to the .htaccess file!

    Thread Starter martinjt

    (@martinjt)

    Talk about frustrating, not even these instuctions line up with what I’m seeing.

    In the below:
    ___________________________________________________
    Open the httpd.conf file with your favorite text editor .

    [ec2-user wordpress]$ sudo vim /etc/httpd/conf/httpd.conf

    Find the section that starts with <Directory “/var/www/html”>.
    ______________________________________________________

    There is no such file or even the path to the file.

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Adaptive Images Error — The .htaccess file is not updated’ is closed to new replies.