direct publisher limitations and observations
I'm starting this out with a bit of criticism. However, it's intent is to either learn why, make people aware for positive change, and or help a few others out with what I percieve as issues. Direc...
Forum Discussion
"Pasnow" wrote:"belltown" wrote:5) updates via the direct publisher website, such as category changes and/or uploading new xml files do not seem to appear on the endusers device until it gets updated.
Possibly, the way the DP channel code is implemented, the feed url changes with each update the developer makes through the developer dashboard. That would explain why the users' channels have to be updated to get the new feed. I'm not sure why they wouldn't want to use a fixed url for the channel so that the channel has access to the new data as soon as the developer updates are made.
Hmmmm, just curious, do the DP channels ever auto update, or only when the customer manually update their settings & device? Honestly I was just using a changing url thru myjson I have a wordpress website and I couldn't add on a 'json only' page to it, but I should be able to using a subdomain I suppose.
My guess is that whenever the Roku is updated (EITHER by the user doing a manual update from the Roku Settings>System>System update menu OR automatically, which usually seems to happen daily), then the DP channel will be updated to the latest feed url, if necessary. Channels can't update by themselves; they're only updated when the Roku device is updated. And then they are all checked for any Channel Store updates.
I don't see how that has anything to do with you using a changing myjson url or a Wordpress file, however. If what mitchstein said is accurate, it should make no difference when/how your JSON feed is hosted and how or how often you update it, since the update won't appear on the user's Roku until their Roku undergoes a system update.
