"Add Media" NOT responding for a PODS Custom Setting with a WYSIWYG field set with oEmbed, Shortcodes and Add Media enabled #6663
-
Description"Add Media" for a PODS Custom Setting with a WYSIWYG field set with oEmbed, Shortcodes and Add Media enabled. However, with the same PODS Custom Setting with added another field - i.e. Image, Add Media works. Setting the added another field with a Hidden UI, Add Media will not work Version2.8.17 Testing Instructions
Screenshots / ScreencastNo response Possible WorkaroundDowngrade to PODS v2.7.31 - issue resolved. Site Health InformationNo response Pods PackageNo response |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 2 replies
-
@sc0ttkclark / @JoryHogeveen , can you reconfirm if this is indeed a bug? Is this already a know issue? |
Beta Was this translation helpful? Give feedback.
-
Hi @papa-pup |
Beta Was this translation helpful? Give feedback.
-
Hi @JoryHogeveen I have NOT met with the issue as describe on #6283. By the way, I tested again on 2.8.19 to 20 and the problem still persist. |
Beta Was this translation helpful? Give feedback.
-
@JoryHogeveen , any update to any fix will be done? |
Beta Was this translation helpful? Give feedback.
-
Hi @papa-pup I tested this again and still cannot reproduce this. No matter what I do, the "Add media" button opens the modal for images. Cheers, Jory |
Beta Was this translation helpful? Give feedback.
-
2022-07-05T15-49-13D2-47.webm Please note - This is create a Custom SETTING and not a CPT. |
Beta Was this translation helpful? Give feedback.
-
Hi @papa-pup |
Beta Was this translation helpful? Give feedback.
-
@JoryHogeveen Brother, |
Beta Was this translation helpful? Give feedback.
-
any news about that? is there any workaround (except using code view)? |
Beta Was this translation helpful? Give feedback.
-
As far as I can tell, this is fixed in 2.9.x, or at least in 2.9.4 which I've been testing with. This should be all good after 2.9.4 is released. |
Beta Was this translation helpful? Give feedback.
As far as I can tell, this is fixed in 2.9.x, or at least in 2.9.4 which I've been testing with. This should be all good after 2.9.4 is released.