When I do the acidfree/test as directed in the readme (which should have a .txt on it, please), it comes out like this:

Acidfree albums

1. Image module sanity check passed.
2. Temporary path okay.
3. video_image module weight okay.
4. acidfree module weight okay.
5. gd image toolkit installed and properly configured

No errors were detected. But this doesn't mean that Acidfree is guaranteed to work flawlessly. It is a complex system and still under development. Please be patient while all the wrinkles are found and ironed out.
Published, promoted and sticky configuration

* Albums: Published, Not promoted, Not sticky. Acidfree recommends Published, Not promoted, and Sticky
* Images: Published, Not promoted, Not sticky. Acidfree recommends Published, Not promoted, and Not sticky

PHP configuration

* Maximum file upload size is 2M (upload_max_filesize)
* Maximum POST size is 8M (post_max_size)
* Maximum execution time is 300 seconds (max_execution_time)
* Maximum memory usage is (memory_limit)

If these limits are smaller than the files you plan on uploading, you should change the settings in your php.ini file

Comments

vhmauery’s picture

vhmauery commented

This seems to be fine for me...

Can you look through your php.ini file and look for the line that specifies the memory limit and tell me what variable it is setting? I don't know if the php version for windows uses the same variable or not.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented 
ini_set('arg_separator.output',     '&');
ini_set('magic_quotes_runtime',     0);
ini_set('magic_quotes_sybase',      0);
ini_set('session.cache_expire',     200000);
ini_set('session.cache_limiter',    'none');
ini_set('session.cookie_lifetime',  2000000);
ini_set('session.gc_maxlifetime',   200000);
ini_set('session.save_handler',     'user');
ini_set('session.use_only_cookies', 1);
ini_set('session.use_trans_sid',    0);
ini_set('upload_max_filesize',      '768K');
ini_set('url_rewriter.tags',        '');
ini_set('memory_limit',             '24M');
vhmauery’s picture

vhmauery commented
Status: Active » Closed (won't fix)

Well, in that case, I don't think there is anything we can do to fix this one. Acidfree calls ini_get('memory_limit') which should be returning the same value as your ini_set. But it doesn't, so I don't think this is Acidfree's issue -- more like php's problem.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Hmm, I've been wondering why php_info doesn't ever show that setting. Maybe it's been broken all along. I wonder how I've managed to not run out of memory.