- Issue created by @thomas.frobieter
- Status changed to Needs work
almost 2 years ago 7:31am 27 April 2023 Okay, we found the "issue".
After we have deleted the configured custom oembed provider, everything works fine.
@phjou are you aware of this change? Probably a change in the core oembed implementation or something?
If this is the case, the module description need to be updated, and now its much easier: Only the PeerTube instance URL needs to be added under /admin/config/media/peertube.
- 🇩🇪Germany Anybody Porta Westfalica
To sum the result up:
After we have deleted the configured custom oembed provider, everything works fine.
It should be documented that peertube module adds the custom oembed provider so it should not be added twice!
Could that please be added to the docs and perhaps module page @maintainer? - 🇩🇪Germany Anybody Porta Westfalica
Switching this to a minor documentation issue.
- 🇩🇪Germany Anybody Porta Westfalica
The error is back now - without any changes!
Could the maintainer please clarify, which entries are needed and which should be removed? Our current setup follows the README documentation.