• amirulazhar

    (@amirulazhar)


    Hi,
    We are using {unique-id} as file prefix. Now our storage at EC2 is full because temporary folder that is created on each upload file to S3. The path is upload/folder/{unique-id}/image.jpg
    The image file itself is deleted but the folder created by {unique-id} is still on EC2.
    is there any workaround beside manually deleting the image folder?

    Also there is compatibility issue with Revolution Slider. Is there any plan for next update for this?

    Great plugin btw.
    Thanks ??

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author interfacelab

    (@interfacelab)

    Stop using {unique-id} ??

    I’ll look into adding empty folder deletion soon.

    What compatibility issue is there with Revolution Slider? I know some of these slider plugins do their own upload stuff, side stepping WordPress’s upload, or they try to get fancy and directly grab URLs from the DB which they shouldn’t do.

    Thread Starter amirulazhar

    (@amirulazhar)

    Thank you for your reply.

    We using {unique-id} because we had a problem as the image with the same filename will be replace on S3 – using {date:format}. Would you have other suggestion on this?

    When the Revolution Slider and Media Cloud both active the site become 500 Internal Server Error.

    Thanks ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘{unique-id} folder not deleted on server’ is closed to new replies.