Bugzilla – Bug 16063
Podcast Shortcut only displays default podcasts on IP3K
Last modified: 2010-06-10 15:12:58 UTC
When installing the Podcast Player app from Mysqueezebox.com on a Squeezebox Boom or Squeezebox Classic, you are given the option to add a shortcut to the home menu. This shortcut links to Odeo and Top 10 lists from Podcast Alley, but not to the users Podcasts as intended. The Podcast Player App is still functional in the My Apps menu, but no matter what steps are taken to add this app shortcut to the homepage, it always links to the old podcast player.
You are describing the default podcast list on the mysqueezebox.com podcast app. Have you tried to manage that list from there? See also bug 16061
Same with me (see also http://forums.slimdevices.com/showthread.php?t=77563) using Squeezebox Classic. On SBS I have the Podcast Player in the main menu with _my_ podcasts - managed via MySqueezebox. On MySqueezebox I have the Podcast Player in the main menu, too, but with randomly changing podcasts - yesterday about 120 podcasts of a WDR-affine listener, today 20 podcasts, most of them in spanish. Using "My Applications" - "Podcast Player" I get _my_ podcasts - but that's rather uncomfortable.
btw: it's a MySqueezenetwork problem neither than a boom or classic specific one.
Please address this issue if possible, the Podcast Player list on the Home screen for MySB.com on the SB Boom and SB Classic does not reflect the Podcast Player App list, only the default listings of Odeo and Podcast Alley.
I've actually just confirmed this on my Boom. IP3K behavoir: Podcast Player link added to home menu > Only default podcast are displayed Squeezeplay behavoir: Podcast link added to home menu > both default and user added podcast are displayed and available.
This is a dupe of the master bug which says: "Podcast management is utterly broken". We have two ways to configure podcasts, which are completely independent and don't show up on the same interfaces. It's conceptually broken. We should never have considered bug 14467 fixed. It's not.
*** This bug has been marked as a duplicate of bug 16061 ***