-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Radio.de add is not working anymore #4568
Comments
The right place to report this, is at the source repository of the add-on. Not here. |
@basrieter I report it here because as I mentioned, its already reported in the source repository. But this belongs to the same org as the index, however, nobody replies there. As I already wrote in the issue, I am asking you to remove a non-functional addon from the repository to avoid people getting annoyed by installing a broken plugin. |
@basrieter I am especially wondering why there is a category to report broken addons if you don't want those issues to be opened. Am I missing something? |
The original add-on author needs to create e PR to mark an add-on as Only of the owner is unknown or not active we could do this. So let's just wait for now and I will reach out to the devs in the meantime. |
@basrieter Thank you for the info! I filed a PR to mark the addon as broken, before I've read your comment. Sorry if this is useless now, but I think its fair to mark the addon as broken for now. Just so you are aware: I am planning into fixing the issue, but it might take a while. |
No worries, I will tag the original devs for an OK. |
Add-on details:
Ownership
Broken because:
Whatever action I want to take in the addon, there is a network error. I think the radio.de API changes and the changes are not yet reflected in the repository.
I am not aware if thats the right ways to report such issue. In the addon-repository the malfunction is already reported, see XBMC-Addons/plugin.audio.radio_de#61 or XBMC-Addons/plugin.audio.radio_de#59 . However, no action is taken. I'd suggest to remove the addon from the official repository until its fixed.
If you are aware of any maintainer of the addon, I might be interested in helping getting the plugin running again. Let me know if there is a way to get involved.
The text was updated successfully, but these errors were encountered: