Open
Reported for: Toolset Forms 2.4
Toolset Forms offers 2 ways to upload media:
There is an issue when using Amazon S3 and Cloudfront plugins, and using the native WordPress Media Uploader in Forms. In this case, Featured Images are not saved against the created (or edited) post. They are uploaded, but not added to the post.
If instead, you disable the WordPress Media uploader for forms, Featured Images are added to the post properly, however, any custom media fields will store the local (server) upload path as value, instead of the generated Offload URL.
Update: A client reports the same issue for Bunny CDN, too.
One part of the issue can be avoided by using the WordPress Media Uploader in Forms and re-saving the Post Meta for the Featured Image using custom code.
Since all custom media fields, in this case, will already work properly, the problem will be solved with this step.
However, if you do not use the WordPress media Uploader, there is currently no stable solution for this issue.
Our developers are aware of both issues and will provide a fix in the future Forms update.
I think this is possibly a poor solution because I am finding that audio files (which are also attachments) are getting recorded as the post featured image which of course is incorrect
The issue described here is only about Featured Images, unless you use the old method to upload media (not the WordPress Uploader) – then it affects all custom fields.
With the workaround you can solve only the issue appearing when you’d use the WordPress Uploader, the issue referring to the Custom Fields cannot be solved yet.
I suggest opening a ticket if any of this doesn’t fit what you see.
I’m sorry, I completely had missed your point and Minesh has now informed me about what is meant, of course, the code is wrong. I will work on a proper solution that uses only the featured image, not all attachments, tomorrow. I will then update this erratum.
Not a problem at all. I’m grateful for your help.
I’ve updated the related Support ticket and on Monday when people are back on shift the erratum also will be updated with new code.
I have now also updated the Erratum, FYI.
I’m sorry to say that this new version also isn’t working for me. If I use the WP Media library and try to attach an existing image, something is added as data to the featured image but no image is attached (I know something is added because I check in the view for existence and if not present a standard filler image; the filler image is not appearing either)
Is this the ticket you have open for this issue?
https://toolset.com/forums/topic/forms-2-4-media-library-use-not-working-with-amazon-s3/page/2/
I suggest to follow up there.
I have now removed any workaround here, because it’s not working for all cases. I will not add it again, as there are cases where this is not solving the issue at all and in all cases, it does solve only part of the issue.
The actual problem will be looked at by developers in its entirety, and then we’ll update with adjustments.
Is there any update on this? This not working means that anyone who uses S3 can’t use post edit forms because when they are used on an existing post, the image is removed.
No, there is no news. I will update this erratum as soon there are. I have nagged the developers to fix this ASAP as well.
I just discussed this internally and we will try to fix this ASAP like all other issues reported here in the errata section.
However this will likely not happen 2019, this due to the current major focus on Gutenberg and Blocks features. Please do not expect a fix for it this year, however, I would mean you can slate some expectations in the early coming year.
For now, there is no solution for this in Toolset Forms.
Is there any further update? This has been open for a very long time. This is a significant issue for us as it drives up AWS costs by forcing us to store duplicate images and forces users to upload images which they’ve already uploaded several times. Thanks
Please can I ask for a status update on this issue? It has now been open for almost a year
I ran into the same problem. So I cant use any images until this is fixed.
Thanks, but this has been open for almost a year. Can you please impress on 2nd tier how disruptive this is? In particular, it means images and files are duplicated which increases storage costs, and as far as I can tell it renders use of things like image compression unusable because they depend on using the image library uploader.
For any significant website, use of a could storage method is essential so this seems to me to be a major flaw which ought to be fairly easy to address in less then 12 months.
I love Toolset but this isn’t good at all.
Hi, I ran into the same problem with dynamic images for the gallery. I also use S3 to store my images. Toolset image fields cannot be rendered from S3. At least can you give us an update?