Ok, I think I'm getting closer. When I look in my production environment I see:
---------- 1 root www 566 Mar 20 11:44 arismartcontent_config.php


Where in my development environment the file has rw permissions, so this is the problem.

I'm going to investigate a bit more...

So based on our security my admin said:

"But I see you are wanting a php file to have access. The second line above explicitly forbids that. The idea is that we don't to execute php scripts from a writeable area of the site (like temp or cache). This reduces the chance that someone can upload something malicious and execute it with the privs of the web server."

We basically set all php files to not be writeable when in a 'writeable directory'...

Any other ideas?

thanks.

We will update this functionality in the next version of the extension. It will be ready within couple of days.

Regards,
ARI Soft

Thank you. I look forward to trying it out.

Another question, any chance you'll be moving to an SSL environment soon? your site is not 'secure', my university frowns upon us using tools from 'non-secure' sites...

thanks,
Laura

We are not able to have any .php files sitting in our 'cache' folder. Is there a fix for this?

---------- 1 root www 566 Mar 20 11:44 arismartcontent_config.php

This is because we can't have .php files sitting in a 'writeable' directory... such as cache...

from our administrator:
"But I see you are wanting a php file to have access. The second line above explicitly forbids that. The idea is that we don't to execute php scripts from a writeable area of the site (like temp or cache). This reduces the chance that someone can upload something malicious and execute it with the privs of the web server."

Please help!

thanks
Laura

When will this be fixed? As we cannot have a .php file in a writeable directory...

thanks.