(2016-12-07, 08:33)Hitcher Wrote: (2016-12-05, 20:11)rodalpho Wrote: Since it's broken in Confluence I guess you weren't kidding that nobody took your advice.
Can you report what's exactly broken in Confluence here please.
All of the details have already been posted in the last few of pages of this thread (worth reading for the complete picture), but I will try to summarise.
- Version 5.3.6 of YouTube has been updated to comply with the policy enforcement noted
here:
(2016-12-05, 17:18)phil65 Wrote: That might the uneducated opinion from someone who doesnt know the technical side of things
I explained things in more detail here: https://github.com/xbmc/repo-plugins/pull/771
On next estuary update some more viewtypes will be enabled for "videos" content type. (Wall and InfoWall)
- This causes the MediaInfo view to no longer be available to YouTube videos (only List, Big List, and Thumbnails are available).
I can confirm this with the Xonfluence skin, which is a Confluence Mod.
Martijn tried to help clarify the issue
here:
(2016-12-05, 19:53)Martijn Wrote: Do not forget the function to correctly set content was already available since 2015 which is pre-v16 so not only v17 Krypton. No one actually took our advise except a few.
This is where rodalpho's comment becomes relevant
here:
(2016-12-05, 20:11)rodalpho Wrote: Since it's broken in Confluence I guess you weren't kidding that nobody took your advice.
- The MediaInfo view is also now no longer available to YouTube videos in the Confluence skin either.
So Rodalpho was referring to the fact that even stock Confluence appears 'not to have taken Team Kodi's advice since 2015', because the same situation exists in Team Kodi's own skin.
Now, as above, phil65 mentioned:
(2016-12-05, 17:18)phil65 Wrote: On next estuary update some more viewtypes will be enabled for "videos" content type. (Wall and InfoWall)
I'm not sure what these new Wall and InfoWall views will look like in Estuary, but for YouTube and other similar video addons we still need something similar to the current "Episodes" in Confluence.
However this still doesn't help users right now, today, who are using Kodi 16.1 (the current stable release) and YouTube 5.3.6 (the current stable release, complying with Team Kodi policy).
The current suggestion seems to be that the skinners need to fix their skins.
Some more advice for skinners has been made available by phil65 in a new thread
here.
Does this mean that stock Kodi Confluence is/has updated to solve this situation?
Can Confluence Mod skinners now simply update their Mods from stock Confluence?
In addition there seems to be further situation in relation to 'Mark as Watched/Hide Watched', detailed
here:
(2016-12-05, 19:13)anxdpanic Wrote: I'm going to try to sum up the user side of this to hopefully help with some clarity on this.
Core/skins lack a default view per content type. (override view)
'Mark as Watched/Hide Watched' is not available to videos (wasn't aware of this until users presented it)
and
here:
(2016-12-05, 19:53)Martijn Wrote: If there is indeed an issue now with watched/unwatched we'll have to fix that and not hack around the problem.
Alternatively, I did make another suggestion
here, but so far this has gone unanswered by Team Kodi.
(2016-12-05, 20:11)jmh2002 Wrote: On a separate note, perhaps Team Kodi would be agreeable to this change not being enforced for addons in the pre Krypton repos?
Because 2015 or not, it seems that the skins are somewhat behind with the necessary changes, and regardless of whose fault this is it still has an immediate serious negative impact on everyday Kodi use for existing users who haven't actually done anything wrong.
Since it will take some time (possibly even some months) for all the skins to get themselves in line with Team Kodi policy, I still respectfully request that my above suggestion at least be considered, because at the moment the limited available Views for YouTube videos make the addon almost unusable from a daily practical point of view.
This will also be the case for any other video addon that updates to comply with the policy enforcement - there are more than 300 of them
here (but perhaps YouTube has been the first to implement the required changes?).
@Hitcher - Do I need to repost all of this in the Main Confluence thread that you referenced?
THANKS for continuing to look into this situation, it is most appreciated