ready to publish, link doesn't work!!
Everytime I push the publish button I get an error, told to contact support. How exactly can you contact support anyway? and why isn't this publishing?
Forum Discussion
Hello mitchstein,
The nature of these posts is causing me great concern. There are many intelligent postings of well documented errors which appear to be the result of this conversion to Direct Publisher. After months of work, we were ready to launch this week - and I ran into an impossible piece of information to provide to move forward - The Roku API Billing Service Account from my Developer Account - this does not appear to exist, so I to my dismay, I found myself Here, combing through screens of stranded operators without any answers or replies to their questions. I have a degree in comp sci and a handful of real world earned Microsoft MCSE, MSCA certifications and I took one look at Direct Publisher and its slack security and I was appalled that in the face of Cyber Command calling on all us Sys Folks to lock down their resources that Roku would forward such a solution that besides denying the ability to accept subscribers, only seems to work when the solutions are share asset folders to Access All. My project, which I was preparing with all the proper AWS S3 security bucket permissions and entering my secret keys and perfectly sized pixel artwork into Instant TV Channe, has ground to a halt. I am very discouraged by what appears to be many people more talented than me at programming who have had their channels potential gutted. This post which I have added a non technical post to is written by a channel operator with much more experience than me, and if so many capable techies are being side lined by this bizarre Direct Publisher forced migration, my project, for posterity, for our Republic, is gravely threatened, which honestly puts a heck of a lot more at risk than if I was just posting an ego channel. the schulz
The nature of these posts is causing me great concern. There are many intelligent postings of well documented errors which appear to be the result of this conversion to Direct Publisher. After months of work, we were ready to launch this week - and I ran into an impossible piece of information to provide to move forward - The Roku API Billing Service Account from my Developer Account - this does not appear to exist, so I to my dismay, I found myself Here, combing through screens of stranded operators without any answers or replies to their questions. I have a degree in comp sci and a handful of real world earned Microsoft MCSE, MSCA certifications and I took one look at Direct Publisher and its slack security and I was appalled that in the face of Cyber Command calling on all us Sys Folks to lock down their resources that Roku would forward such a solution that besides denying the ability to accept subscribers, only seems to work when the solutions are share asset folders to Access All. My project, which I was preparing with all the proper AWS S3 security bucket permissions and entering my secret keys and perfectly sized pixel artwork into Instant TV Channe, has ground to a halt. I am very discouraged by what appears to be many people more talented than me at programming who have had their channels potential gutted. This post which I have added a non technical post to is written by a channel operator with much more experience than me, and if so many capable techies are being side lined by this bizarre Direct Publisher forced migration, my project, for posterity, for our Republic, is gravely threatened, which honestly puts a heck of a lot more at risk than if I was just posting an ego channel. the schulz
