I am a bit surprised that loading the old jsapi, which now redirects to the
new loader, causes this indirect problem resulting in the "b.split" error,
and only (?) when MooTools is also loaded. But I suspect this is due to
some variation in load order (since the redirect imposes a delay until
after the new loader is loaded), combined with how and when polyfills are
applied.
Sorry for the confusion this is causing, but I am glad people are finding
workarounds. Freezing on version 49 is not desirable, however, so I am
curious to learn what the underlying cause is.
On Fri, Apr 16, 2021 at 12:08 PM Richard Manly <rcma...@gmail.com> wrote:
>
> Hi Chris,
>
> If it's any help:-
>
> On my page mootools is definitely loaded.
>
> I'm adding the script using the following:-
>
> $document->addScript('https://www.gstatic.com/charts/loader.js');
> google.load("visualization", "1", {packages:["corechart"]});
>
> The above triggers the error.
>
> Changing the corechart load to;-
>
> google.charts.load('49', {packages: ['corechart']});
>
> ...works
>
>
>
>
>
> On Friday, 16 April 2021 at 16:29:44 UTC+1 Chris G wrote:
>
>> I have now identified the problem for several sites, including the two
>> examples in my original post. Where sites are using the old (jsapi) method
>> of loading the Google Charts code, and the site also loads MooTools (tested
>> with v1.4.5), the "b.split is not a function" error always occurs. The mere
>> presence of MooTools is enough to trigger the error. For these sites, the
>> problem can be fixed either by switching to the new (loader.js) method of
>> loading the Google Charts code, or by removing MooTools from the page. I
>> would still like to know why this is the case, but at least we know how to
>> fix it.
>>
>> We understand that other cases exist that trigger the error when using
>> the new (loader.js) method of loading the Google Charts code, however I
>> don't currently have a case I can work on.
>>
>> On Friday, April 16, 2021 at 11:26:49 AM UTC+1 rcm...@gmail.com wrote:
>>
>>> I have also seen this bug, only resolved through forcing a load of
>>> library V49.
>>>
>>> On Wednesday, 14 April 2021 at 11:21:27 UTC+1 pescu...@gmail.com wrote:
>>>
>>>> Hello,
>>>>
>>>> I had the same problem since yesterday using the latest version of the
>>>> library.
>>>>
>>>> Like you in the meantime I blocked the loading of the library on
>>>> version 49 while waiting to find a cause and a solution at the root of the
>>>> problem.
>>>>
>>>> If anyone has the reason for the problem and a way to fix it I'm also
>>>> interested.
>>>>
>>>> Le mercredi 14 avril 2021 à 09:10:38 UTC+2, Chris G a écrit :
>>>>
>>>>> I have a product that enables sites to use Google Charts in the Joomla
>>>>> CMS. Since version 50, a small number of users have reported the chart
>>>>> error "b.split is not a function". This is a small error on a red
>>>>> background that appears in the chart element instead of the chart itself,
>>>>> so a Javascript error caught by the Charts API itself.
>>>>>
>>>>> By debugging, we know that the error occurs deep within the Google
>>>>> code, but since we don't have the source, it's difficult to follow, and
>>>>> impossible to figure out the cause.
>>>>>
>>>>> Since only a small number of sites are affected, we assume that the
>>>>> problem is provoked by another plugin, and we have confirmation from one
>>>>> user that that was the case for him. But we have other users unable to
>>>>> identify the provoking plugin.
>>>>>
>>>>> By Googling "b.split is not a function", I can find more sites
>>>>> affected by the error. Neither of these examples uses our software, and in
>>>>> the first case, it's not a Joomla site. Quite possibly the owners of these
>>>>> sites are not aware of the problem yet:
>>>>>
>>>>> http://gestiondepymes.es/features/google-charts/area-chart
>>>>>
>>>>>
>>>>> https://www.kankakeehealth.org/infectious-disease/covid-19-response-and-recovery/
>>>>> (open the sliders to see the errors)
>>>>>
>>>>> These are just examples. There are more.
>>>>>
>>>>> For our own users we have "solved" the problem by enabling them to
>>>>> load API version 49, but obviously we would like to get to the bottom of
>>>>> this.
>>>>>
>>>>> Can anyone shed any light that would help us to track down the problem?
>>>>>
>>>> --
> You received this message because you are subscribed to the Google Groups
> "Google Visualization API" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-visualization-api+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/9861e505-a26f-468d-8e14-1e073891ab70n%40googlegroups.com
> <https://groups.google.com/d/msgid/google-visualization-api/9861e505-a26f-468d-8e14-1e073891ab70n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
• Daniel LaLiberte
• SWE
• Cambridge MA
• dlalibe...@google.com <dlalibe...@google.com>
--
You received this message because you are subscribed to the Google Groups
"Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-visualization-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMXHwayt797oi9k0-cfx7RzTvMmuiCc0t-iQ9G3S9MCWQ%40mail.gmail.com.
