<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic BUG: Bad character encoding in cloud.ruckuswireless.com (UTF8 -&amp;gt; LATIN-1?) in RUCKUS Cloud</title>
    <link>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/BUG-Bad-character-encoding-in-cloud-ruckuswireless-com-UTF8-gt/m-p/7119#M76</link>
    <description>Ruckus Cloud has a bug in which accent characters typed in any field get saved in non UTF-8 encoding and end up producing gibberish characters. 
&lt;BR /&gt; 
&lt;BR /&gt; This completely breaks integration any time non-english localization is involed. 
&lt;BR /&gt; In Quebec for instance, or if someone creates a spanish localized portal and AUP(Acceptable Use Policy) 
&lt;BR /&gt; 
&lt;BR /&gt; For example: On our guest wifi network if we use any of Guest wifi options(Captival Portal, Self Sign-in, Managed Guest, etc.) and have a message like "Bienvenue à [business]". Once this message is saved, it gets displayed like this "Bienvenue �� [business]". 
&lt;BR /&gt; 
&lt;BR /&gt; This applies to every field. So when we create a bilingual Acceptable Use Policy for the guest wifi, we wont be able to use accent characters at all, which makes french not make sense anymore. 
&lt;BR /&gt; 
&lt;BR /&gt; When creating a venue, the address entry fields 'force' auto fill with saved address data from a database you host. The source database has the correct character encoding(UTF-8). cloud.ruckuswireless.com's platform database does not(its using LATIN-1 or something similar. REALLY dangerous). 
&lt;BR /&gt; 
&lt;BR /&gt; That means for example that I cant type 
&lt;BR /&gt; "123 Rene-Levesque, Montreal, Quebec" 
&lt;BR /&gt; and click save(as it shouldn't). 
&lt;BR /&gt; 
&lt;BR /&gt; Instead, it forces you to select the referenced address with the correct spelling(with accents) 
&lt;BR /&gt; "123 René-Lévesque, Montréal, Québec". 
&lt;BR /&gt; It will only save the venue if I let it 'correct' the spelling. 
&lt;BR /&gt; 
&lt;BR /&gt; The result of this misconfiguration is that after hitting 'save' the data gets perpetually displayed as follows: 
&lt;BR /&gt; 123 Ren��-L��vesque, Montr��al, Qu��bec 
&lt;BR /&gt; 
&lt;BR /&gt; Database character encoding mistakes like this will cause gradual and cascading problems over time that can be literally impossible to fix(or take hundreds of hours of manual correction). 
&lt;BR /&gt; 
&lt;BR /&gt; What are the chances we could see this fixed in the near future?</description>
    <pubDate>Sun, 13 Nov 2016 03:40:22 GMT</pubDate>
    <dc:creator>dara3</dc:creator>
    <dc:date>2016-11-13T03:40:22Z</dc:date>
    <item>
      <title>BUG: Bad character encoding in cloud.ruckuswireless.com (UTF8 -&gt; LATIN-1?)</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/BUG-Bad-character-encoding-in-cloud-ruckuswireless-com-UTF8-gt/m-p/7119#M76</link>
      <description>Ruckus Cloud has a bug in which accent characters typed in any field get saved in non UTF-8 encoding and end up producing gibberish characters. 
&lt;BR /&gt; 
&lt;BR /&gt; This completely breaks integration any time non-english localization is involed. 
&lt;BR /&gt; In Quebec for instance, or if someone creates a spanish localized portal and AUP(Acceptable Use Policy) 
&lt;BR /&gt; 
&lt;BR /&gt; For example: On our guest wifi network if we use any of Guest wifi options(Captival Portal, Self Sign-in, Managed Guest, etc.) and have a message like "Bienvenue à [business]". Once this message is saved, it gets displayed like this "Bienvenue �� [business]". 
&lt;BR /&gt; 
&lt;BR /&gt; This applies to every field. So when we create a bilingual Acceptable Use Policy for the guest wifi, we wont be able to use accent characters at all, which makes french not make sense anymore. 
&lt;BR /&gt; 
&lt;BR /&gt; When creating a venue, the address entry fields 'force' auto fill with saved address data from a database you host. The source database has the correct character encoding(UTF-8). cloud.ruckuswireless.com's platform database does not(its using LATIN-1 or something similar. REALLY dangerous). 
&lt;BR /&gt; 
&lt;BR /&gt; That means for example that I cant type 
&lt;BR /&gt; "123 Rene-Levesque, Montreal, Quebec" 
&lt;BR /&gt; and click save(as it shouldn't). 
&lt;BR /&gt; 
&lt;BR /&gt; Instead, it forces you to select the referenced address with the correct spelling(with accents) 
&lt;BR /&gt; "123 René-Lévesque, Montréal, Québec". 
&lt;BR /&gt; It will only save the venue if I let it 'correct' the spelling. 
&lt;BR /&gt; 
&lt;BR /&gt; The result of this misconfiguration is that after hitting 'save' the data gets perpetually displayed as follows: 
&lt;BR /&gt; 123 Ren��-L��vesque, Montr��al, Qu��bec 
&lt;BR /&gt; 
&lt;BR /&gt; Database character encoding mistakes like this will cause gradual and cascading problems over time that can be literally impossible to fix(or take hundreds of hours of manual correction). 
&lt;BR /&gt; 
&lt;BR /&gt; What are the chances we could see this fixed in the near future?</description>
      <pubDate>Sun, 13 Nov 2016 03:40:22 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/BUG-Bad-character-encoding-in-cloud-ruckuswireless-com-UTF8-gt/m-p/7119#M76</guid>
      <dc:creator>dara3</dc:creator>
      <dc:date>2016-11-13T03:40:22Z</dc:date>
    </item>
    <item>
      <title>Re: BUG: Bad character encoding in cloud.ruckuswireless.com (UTF8 -&gt; LATIN-1?)</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/BUG-Bad-character-encoding-in-cloud-ruckuswireless-com-UTF8-gt/m-p/7120#M77</link>
      <description>Welcome DR,&lt;BR /&gt;&lt;BR /&gt;
&amp;nbsp; Can you please open a ticket with Tech Support, who can use your input to file&lt;BR /&gt;&lt;BR /&gt;
a bug with our Engineering?&amp;nbsp; We're trying to find these examples to fix them, thanks!</description>
      <pubDate>Mon, 14 Nov 2016 17:04:44 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/BUG-Bad-character-encoding-in-cloud-ruckuswireless-com-UTF8-gt/m-p/7120#M77</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2016-11-14T17:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: BUG: Bad character encoding in cloud.ruckuswireless.com (UTF8 -&gt; LATIN-1?)</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/BUG-Bad-character-encoding-in-cloud-ruckuswireless-com-UTF8-gt/m-p/7121#M78</link>
      <description>Ticket submitted.</description>
      <pubDate>Mon, 14 Nov 2016 17:07:18 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/BUG-Bad-character-encoding-in-cloud-ruckuswireless-com-UTF8-gt/m-p/7121#M78</guid>
      <dc:creator>dara3</dc:creator>
      <dc:date>2016-11-14T17:07:18Z</dc:date>
    </item>
  </channel>
</rss>

