Re: Zend Server and Wordpress Automatic Updates

Minimally, as I understand it, in order to see things in a directory, you need *X and sometimes *RX to all parent directories. *X for directories means the ability to search the directory.

Assuming you have rights to the objects themselves and to the immediate parent. Just as with libraries, you can block all access to files in a directory by excluding from the parent directory.

That's just from memory of recent investigations. It's not our sysytem 38's oldsmobile, is it?

Vern

On 6/29/2010 4:06 PM, Richard Schoen wrote:

What if you give QTMHHTTP authority at the main /htdocs folder level,
will the permissions carry through any new subfolders ?

I'm not familiar with how the IFS does inherited object permissions.

Could also give QTMHHTTP *ALLOBJ authority. Wouldn't recommend that,
but it would work :-)

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------

message: 4
date: Tue, 29 Jun 2010 13:08:04 -0600
from: Pete Helgren<Pete@xxxxxxxxxx>
subject: [WEB400] Zend Server and Wordpress Automatic Updates

Anyone using Zend Server with Wordpress and are able to get automatic
updates to work? I get a "Could not create directory:
/www/zendsvr/htdocs/petesworkshop/blog_wp/wp-content/upgrade/wordpress-3
.tmp"
error for every folder it attempts to create. The "missing link" is
that folders are created with *my* user ID and permissions and I think
Zend (or Apache) wants to have QTMHHTTP to have permission. Since I
cannot sign on with QTMHHTTP, I have to manually add the user to every
folder the WP update creates.

Any ideas here? I could do the manual update but I am curious to see if
anyone has a workaround to the problem.

Pete