Compatibility Issues With Easy Digital Downloads and Frontend Submissions
-
I’m building a site using Easy Digital Downloads and their Frontend Submissions extension so vendors can sign up and create their own stores/products.
In the vendor profile, they are able to upload an avatar (this is a simple media file upload field, separate from the Gravatar based WordPress avatar system). The file gets uploaded just like any other normal file, into the wp-content/uploads/ folder/sub-folders.
When the avatar is uploaded, WordPress (or the Frontend Submission extension itself actually) creates a new image and appends “-avatar” to the filename. So say I upload an avatar named “jackson.jpg”. If I visit the /wp-content/uploads folder on my local server, I see “jackson.jpg” and “jackson-avatar.jpg”.
With W3 Total Cache turned on, using the Amazon S3 functionality, I see that WordPress pushes “jackson.jpg” to my S3 bucket, but NOT “jackson-avatar.jpg”, even though both files exist on the local server.
All other images work totally fine, it’s just this one avatar field that isn’t pushed to Amazon S3.
Of course, I can hack the Frontend Submissions extension to not append “-avatar” if I want to use W3 Total Cache, but there should be a proper fix, and I don’t know how to implement that.
- The topic ‘Compatibility Issues With Easy Digital Downloads and Frontend Submissions’ is closed to new replies.