Bugzilla – Bug 17202
Missing string: SLACKER_RADIO
Last modified: 2011-05-25 21:26:57 UTC
Created attachment 7264 [details] server.log See attached log. I'm only seeing this in onebrowser, not in 7.6.0 trunk.
BTW, I don't have the Slacker plugin loaded and have all mysb.com integration in in SBS turned off.
> BTW, I don't have the Slacker plugin loaded and have all mysb.com integration > in in SBS turned off. That's a good point: some of the strings are fed by mysb.com when SBS logs in to it. We should include all strings used locally though. I'll double check. Thanks!
== Auto-comment from SVN commit #32405 to the slim repo by mherger == == http://svn.slimdevices.com/slim?view=revision&revision=32405 == Bug: 17202 Description: add some of the so far SN only strings to reduce the number of "string not found" messages
== Auto-comment from SVN commit #10567 to the network repo by mherger == == http://svn.slimdevices.com/network?view=revision&revision=10567 == Bug: 17202 Description: use SBS strings instead of SN only strings to reduce the number of "string not found" messages
This issue should be fixed once 7.6 and MySB.com have been updated. Until MySB.com has been fulls updated with above change you might still get that message.
Whatever works. Thanks.
Confirmed fixed in 7.6.0 32398
I don't understand. You've added a number of strings to strings.txt, but failed to define the one string that I'm seeing causing errors.
*** Bug 15994 has been marked as a duplicate of this bug. ***
The larger change was mysb.com side. See comment #4. It might take a few weeks until it's released, but it's fixed none the less.
That's what I don't get. Why add _some_ strings to keep the bugs from appearing, but not others?
Most of the actual values ("Slacker Radio") were duplicated in mysb.com and SBS, but not using the same token. mysb.com was returning the token defined on mysb.com, thus needed to send the translation back to SBS too. By using SBS' token on mysb.com, SBS would receive the token it already knows locally, thus doesn't need to receive the translation too. This bug reported this issue: SLACKER_RADIO is the token being used on mysb, while SBS is using something like PLUGIN_SLACKER_RADIO. By changing mysb to use that same token we didn't need to add a SLACKER_RADIO to SBS. It's a mysb side change only (comment #4). Now there were exceptions to this rule, where SBS didn't have its own token for a value. Thus I added them to SBS (comment #3).
*** Bug 15831 has been marked as a duplicate of this bug. ***