Configuration warning: Images directory not writable

Installed from the modx-0.9.7-alpha-1.zip file. Install ran smoothly. When I started the manager, I received a warning

Configuration warning: Images directory not writable
What does this mean?
The images directory isn’t writable, or doesn’t exist. This means the Image Manager functions in the editor will not work! Please contact a systems administrator and warn them about this message!

I found two images directory under my install, both are writable.

manager/assets/ext2/resources/images
manager/templates/default/images

Am I missing a directory?

Mike

there is also an images folder found in the assets/ directory.

assets/images

Thanks, Breezer. I added manager/assets/images and made it writable. No joy. Still getting the same warning message.

$ find . -type d -name images | xargs ls -ld
drwxrwxrwx 4 user group 4096 2008-04-28 13:10 ./manager/assets/ext2/resources/images
drwxrwxrwx 2 user group 4096 2008-05-04 09:58 ./manager/assets/images
drwxrwxrwx 7 user group 4096 2008-04-28 13:10 ./manager/templates/default/images
$

you dont have to add a new folder, there should already be one in the top level of your site, not in the manager directory

ex: http://www.yoursite.com/assets/images/

edited: well if I woulda bothered to read the version you are running... the posts I made apply to 096, I havent looked at 097 yet...ugh sorry

Breezer, that did it. I did not have an assets folder at the top level. I created that and the subdirectory images. Warning has gone the way of the walrus.

Thanks
Mike

After having a glance at the 097 package, I am wondering if this may be an installer quirk from using some older installer code, but really have no clue lol.

Glad it worked for you but it may not have been the proper solution so watch for any glitches this may have caused

The 097 package I got this morning has the assets/images check part removed from the installer on 4/28, so perhaps your version was downloaded prior to that... check the modification date of:

setup/includes/modinstall.class.php (lines 305 - 323 should be commented out)

If it is listed as modified prior to 4/28 that is likely the issue and you should be able to safely remove the directory you created as it is not needed.
(assets/images)

Again, I apologize for not reading the thread thoroughly before offering help

Breezer, I downloaded the modx-0.9.7-alpha-1.zip file this morning. That was what I used to install. That file has the time stamp that you mentioned.

-rw-r--r-- 1 user group 41013 2008-04-28 12:43 modinstall.class.php

Plus, those lines are commented out in the script. I wonder, though, if this is related to the problem. I’m seeing it in the content manager after the install is complete - in fact, it’s after the setup directory is deleted. I think that what I am seeing is due to line 63 in the core/model/modx/processors/system/config_check.inc.php file

if (!is_writable(MODX_ASSETS_PATH . ’images/’)) {
$warningspresent = true;

I’m seeing that MODX_ASSETS_PATH is defined in the core/config/config.inc.php file.

if (!defined(’MODX_ASSETS_PATH’)) {
$modx_assets_path= ’/var/www/assets/’;

When I installed, I had to override the path. On my development box, I have a symbolic link from /var/www to /some/other/path/. MODx picked up on the link and I overrode it so that I can keep the same path names from development to test to production. Maybe I had a typo when I did?

Mike

The images folder is not included by default in the newer 097 installation. It just needs to have the legacy code checking the old default location removed.