You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a blogpost over the IOS WordPress app, I would like to add a video block and add the video as URL (in my case from our NexctCloud site) like it is possible when editing a blogpost in a browser window, e.g. in Firefox.
Actual behavior
When creating a video block in a blogpost in the WordPress IOS app, you can choose the video from the following sources only:
Choose from device
Take a Video
WordPress Media Library
Other Apps
Tested on [device], iOS [version], WPiOS [version]
Apple iPhone 7 Plus, iOS 15.4.1, WPiOS 19.9.1
The text was updated successfully, but these errors were encountered:
Just installed the new WordPress IOS app update to version 20.0.1. Now it is possible to add images sung 'Insert from URL' - this is already a nice feature but it would be more important for videos as they can be way over 100MB. Keeping them on two locations /WordPress library and e.g. a cloud) does waste expensive storage space and data transfer usually takes much time.
So, maybe the same part of code of the image block can be reused in the video block?
As @tiagomar mentioned in this comment, we already added this feature in version 20.3 via this PR. Hence, I'm going to close the issue but please feel free to reopen it if there's anything related to this feature that we're missing, thanks!
Expected behavior
When creating a blogpost over the IOS WordPress app, I would like to add a video block and add the video as URL (in my case from our NexctCloud site) like it is possible when editing a blogpost in a browser window, e.g. in Firefox.
Actual behavior
When creating a video block in a blogpost in the WordPress IOS app, you can choose the video from the following sources only:
Tested on [device], iOS [version], WPiOS [version]
Apple iPhone 7 Plus, iOS 15.4.1, WPiOS 19.9.1
The text was updated successfully, but these errors were encountered: