jlotito

Hi, I have develop my own solution for this issue.

All the design is located in the file ilab-media-tools/classes/tools/s3/ilab-media-s3-tool.php. And only takes a few code lines.

For the delete action bug.. I have modified line 390 “$this->delete_file($s3,$data[‘file’]);” for “$this->delete_file($s3,$data[‘s3’][‘key’]);” and now whatever prefix I have set.. the delete action is able to find it and erase from the bucket too

For the versioning bug. I have added the function get_object_version_string() from the plugin wp-offload s3, adpating the format to my requeriments, and i have also added new two options to the prefix in lines 292 and 293

$prefix = str_replace(“@{versioning}”, $this->get_object_version_string(), $prefix);
$prefix = str_replace(“@{site-id}”,sanitize_title(strtolower(get_current_blog_id())), $prefix);

These two options “@{versioning} and @{site-id}” allow me to implements the same path that i had in the bucket.. Using the “multisite” folder, and the “versioning feature”.

I think that this develop colud be great if were implemented in the master branch of the project. Please write me if anyone wants the file modified, in order to include it in the repository. That wolud be very grateful for me, because by this way, I will not have errores in futures plugin updates

Thanks a lot for your time

Hi!!

I have benn testing the new update and it works as expected.. Now i can set a prefix according to my path in my s3 bucket. But the main problem still happens, in wp-offload s3 plugin.. there is an option in which you can upload your images with a versioning control, this means that in every file you upload it is created a new folder with a timestamp wich represents the version.. This is made because is normally to have your s3 bucket configure with an aws cloud-front, by the way, the versioning option helps to the invalidations produced in the cloud-front and ensure that the file your are looking for, is downloading in the last version.

On the other hand the last develop about the prefix has broken the delete action.. When I set a new prefix, upload a new file, and afterwards i delete from the wordpress (with the option dletes in s3 too, activated), the file is not found, and consequentely is not erased.

Last, I would like to use the plugin using all the features I mentioned earlier, including the ability to use it in a multisite installation. (corrected by the prefix develop, but not working for the versioning feature)

Thanks for listening to me. Sorry for my long post.. I will be impatient waiting for your answer.

Thanks!

Thanks!! You are the best! I ‘m going to update the plugin now and test it.

Hey,

Same problem here. Have you find any solution for this?

Thanks