aoberoi

oh man im sad to hear that this isn’t working… this would be really useful for me too.

can the developer respond to let us know if he is working on fixing it? if not, then I wouldn’t mind getting into the code to fix it myself, but i don’t want to duplicate efforts.

same issue… images get cached to my server, but then the image does not get attached to the post in which it came from.

here’s what is possibly unique:

the link was to the image on the other server, but the img tag itself was to an image on my server. i was hoping for this plugin to cache the remote image, then replace the link and img tag with the local server cached image. I knew that was asking a lot, but at the very least it sounds like the expected functionality is to cache the remote image, replace the link, add the remote image as an attachment to the post, and leave the img tag alone. what actually happened was that it cached the remote image, replaced the link, and did no attaching to the post and left the img tag alone.

FIX!

okay so the key concept here is that the file_inherit and directory_inherit flags only work for NEW files that are created inside those directories. since i was uploading an image and it was trying to write to an existing directory (2010/12), i was getting the error because the ACL’s permissions wouldn’t apply. the solution is to manually apply those permissions to all of the directories inside (which seems a little less elegant than it should be – so if you have any ideas on a better way please tell) and now uploads work as they should.

proof that you don’t need 777 on ur uploads folder though.

i don’t even think this is a permissions thing anymore because i set chmod 777 uploads/ and i STILL get the same error message.

I’ve also set the uploads directory to wp-content/uploads in the Settings area. Any other ideas here?

I have a related question.

I am interested in making a custom post type that i feel mostly is based off an ‘attachment’ as opposed to a post. So I would like to include the capabilities of an ‘attachment’ as a base and then be able to add a taxonomy to extend the type.

I would then like to use a Page to display a list of all of these custom posts divided by that taxonomy.

The documentation leads me to believe that this can be done by setting ‘capability-type’ to ‘attachment’ when it says that it uses this argument to construct capabilities.

Documentation

capability_type
(string) (optional) The post type to use for checking read, edit, and delete capabilities.
Default: "post"
By default the capability_type is used to construct capabilities.

Does anyone know if this is possible?

Also, how would it show up in the Admin UI?