EE4 compatibility updates:
- Publisher is EE4 and EE5 compatible, but it does not currently support the Fluid field (it's in the works).
- Reel is EE4 and EE5 compatible, but it does not currently support the Fluid field.
Ticket: Wyvern Video feature requests
| Status | Resolved |
| Add-on / Version | Reel 1.2.8 |
| Severity | Trivial |
| EE Version | 2.7.2 |
Bjørn Børresen
Dec 03, 2013Hi, I had some issues w/Dukt Videos on a website and considered switching to Wyvern Video. Looks like it is being resolved now, but I made some notes while setting up Wyvern .. consider them feature requests 😊
If you specify a user that does not exist for the Vimeo Username then you’ll not get an error in the settings, but there will be a js console error when loading an entry.
“When the video dialog opens it will automatically display all videos from this user’s account.” -> when this setting is disabled for YouTube but enabled on the Vimeo account neither will show up (I expected that this would show Vimeo only).
Shouldn’t the addon use the users API keys not yours? I see this specified in a
public $vimeo_key = ‘08a7668f9e10bcc2e8bbf58220566ed7’;
public $vimeo_secret = ‘59294c10bbabab55’;
BoldMinded (Deprecated)
Yes the show all thing is wonky right now b/c it always defaults to opening YouTube first. As for the API keys, I think Channel Videos from DevDemon is doing the same thing. The API key doesn’t reference your user videos, its just an gateway in, so to make setup easier I just use the same key for everyone. I kind of followed Channel Videos’ lead on that one. I have thought about making it a required setting a few times, just never got around to changing the code.
Bjørn Børresen
Yup, not sure how the Vimeo API works but I imagine you might encounter issues if they suddenly start capping or limiting the number of requests daily or something like that. Anyway, nothing that can’t be fixed with an update in that case.