Re: [visualization-api] Google chart API ERROR 502 Question ★PLEASE Check it out fast!!

The "chart.apis" server that you were using was deprecated for many years, and has finally been turned off. The "visualization-api" is an interactive charts library that works quite differently. Part of that library was a wrapper around the "image charts" which use the "chart.apis" server. See

Re: [visualization-api] QR CODE GOOGLE API

The "chart.apis" server that you were using was deprecated for many years, and has finally been turned off. The "visualization-api" is an interactive charts library that works quite differently. Part of that library was a wrapper around the "image charts" which use the "chart.apis" server. See

Re: [visualization-api] I needed help for Google Chart.

You'll need to add your custom tooltip column after each column that corresponds to a series that you want the custom tooltip to apply to. Alternatively, I believe you can aggregate all your tooltips into one 'category' tooltip. Use the focusTarget: 'category' option. See the "London Olympics

Re: [visualization-api] Problem with table page

I see what you mean about the missing current page highlighting. That's a bug. Thanks for reporting it. I don't see a problem with the next and previous buttons, with 20 data rows and page size of 10. Works for me. On Fri, Mar 15, 2024 at 12:49 PM Luana Motta wrote: > I have a table with a

Re: [visualization-api] Re: Is There any problem on chart api

This forum has been moderated for a couple years, since it has become a target for spammers. So new posters need to be approved, but I occasionally miss the notification. On Thu, Mar 7, 2024 at 12:10 PM chavan wrote: > Is this forum active? I posted a question and it never showed up. > > On

Re: [visualization-api] Query regarding ImageSparkLine - Image Charts

The confusing crossover is that Google Charts supports an interface to the Image Charts, in addition to several other non-image charts. And these Google Charts Image Charts will be broken as soon as the Google Image Charts goes away entirely. On Tue, Feb 6, 2024 at 1:39 PM 'Jon Orwant' via

Re: [visualization-api] Query regarding ImageSparkLine - Image Charts

All the "Image*" charts in Google Charts actually use the deprecated chart server. So you should stop using them asap. However, for the Google Charts corecharts, there is an undocumented theme: 'sparkline' option that will reduce any corechart to a sparkline chart. See if it works for you. On

Re: [visualization-api] GeoChart is free?

Hi Martin, While the GeoChart is free to use, the data it may require from Google Maps is a different story. It looks like you can get a limited supply ($200 usage per month) of data for free. But you can avoid requiring any Google Maps data by using explicit location codes rather than names

Re: [visualization-api] Google Maps JavaScript API has been loaded directly without a callback

This could be a bug in how Google Charts uses the Google Maps API. We'll have to look into it. This could explain the occasional flaky test we are seeing. If your geochart is otherwise working fine, then you may not need to be too concerned about this message. On Mon, Dec 4, 2023 at 3:07 PM

Re: [visualization-api] Re: Google Chart geochart language option not working

Hi Thomas, It looks like you are doing the right thing, so I would suspect this is a bug in the GeoChart. You might try the 'upcoming' version, which was updated last spring (never released) to use the updated geochartVersion and regioncoderVersion. See the configuration options at:

Re: [visualization-api] JavaScript Template Strings

Hi Ray Your chartStr is still a string, not an expression, even though it looks like an expression when you print it out. At best, you would have to evaluate the string to turn it into code. The drawChart function and ChartWrapper class do a lookup of the string name of a chartType in order to

Re: [visualization-api] I think google chart events are broken

If events are no long being fired, I would suspect that the chart is being rebuilt from scratch somehow. I am not familiar enough with react to be able to help you figure out why that might be happening. By the way, you normally would not want to add a click event handler every time the chart is

Re: [visualization-api] Google Chart CategoryFilter suddenly not works

We have not yet re-released an updated version 52. The problem may have been fixed in our development code, since we cannot reproduce it there, but there is at least one more breakage not involving controls that we still need to fix before we can proceed with the v52 release. On Wed, Oct 11,

Re: [visualization-api] Etiquetas de valores

The labels on the vertical axis cannot be angled, at this time. There is usually not much need to do so for vertical axes, since the reason for angling labels on the horizontal axis is to allow more labels to be displayed along the width of the axis. But there would be a small benefit for

Re: [visualization-api] How to id certain columns or header rows in Table API

The DataTable is transformed by the chart code into the elements of the visualization, typically SVG, but possibly HTML for a couple chart types (e.g. Table). The DataTable API does have a generic property mechanism, so you can associate arbitrary property name-value pairs to columns, and these

Re: [visualization-api] Pie Chart

How do you know that the code is correct? How can we tell? It would be best if you could create an example web page that we can see showing the problem you are experiencing. Try using jsfiddle to create such an example. On Wed, Aug 9, 2023 at 10:53 AM JESSICA MARIE MENDOZA <

Re: [visualization-api] Weird Behavior with Google Charts and Angular

I would look into whether you can narrow down the problem with this one computer by disabling all chrome extensions. Also check whether the problem occurs with other browsers. Chrome itself is updated frequently, so perhaps there was some conflict introduced that only affects this one computer

Re: [visualization-api] Re: Google Charts New Release Candidate: V52, Feb 20, 2023

There are two known regression bugs in v52. 1. CategoryFilter css problem 2. fontName option used (via webfonts.js) with material charts. So I rolled back the rollout, so 'current' is (or soon will be) '51' again. It would be great if more people could keep testing the 'upcoming' version before

Re: [visualization-api] Issue with category filters using Google charts version 52

This is a regression bug in v52. I rolled back the rollout, so 'current' is (or soon will be) '51' again. On Tue, Apr 4, 2023 at 1:43 PM Saravanan Kandaswamy wrote: > From yesterday, I am seeing the category filters are not working as > expected.. The options are appearing far below from the

Re: [visualization-api] Google Chart CategoryFilter suddenly not works

This is a regression bug in v52. I rolled back the rollout, so 'current' is (or soon will be) '51' again. On Tue, Apr 4, 2023 at 1:43 PM P.Udayasooriyan wrote: > i been using Google Chart almost a year. it was working without issue. > > but suddenly today CategoryFilter in TableChart not

Re: [visualization-api] Re: Google Charts New Release Candidate: V52, Feb 20, 2023

The 'current' version is now '52'. Due to caching, it may take a couple hours before you see the change. For most people, there should be no visible change. On Mon, Mar 20, 2023 at 12:44 PM Daniel LaLiberte wrote: > For some reason I am not yet aware of, this group was blocked for the past >

[visualization-api] Re: Masking Loader.js References for Firewall

By "masking" I would guess you mean that we should load remove the "https://www.gstatic.com; prefix on links within the loader, so that it loads from wherever you are getting the loader from. I believe I understand your reason for needing this, but there are security reasons why the full URL

[visualization-api] Re: Potential error in stylesheet warning

(Your message was marked as spam in my gmail, so I didn't see it until now. Not sure why, but probably because of the links. Perhaps this is related to why the group was blocked for a few days. Not your fault, of course.) There is no string in the Google Charts code matching what you are

Re: [visualization-api] sporadic error in googleChart visualization

There is no string in the Google Charts code that matches that message: "getInitChartSizeValue". I don't get any match for that in google search either. But "googleChartLibrary" is found by google search, though it is not in the code. So you must be using some external library that wraps around

Re: [visualization-api] Re: Google Charts New Release Candidate: V52, Feb 20, 2023

For some reason I am not yet aware of, this group was blocked for the past week, but at this time it appears to be open again. If you attempt to post but it was rejected, please try again. On Saturday, March 11, 2023 at 5:55:31 PM UTC-5 Daniel LaLiberte wrote: > > > Daniel LaLiberte > 5:35 

Re: [visualization-api] Re: Google Charts New Release Candidate: V52, Feb 20, 2023

Daniel LaLiberte 5:35 PM (17 minutes ago) Reply to google-visualization-api I've updated v52 with a fix for the orgchart bug (when the table would have colspans greater than 1000). There are also a large number of changes to the module structure of the code, all to eliminate the "var

Re: [visualization-api] Re: chartRangeFilter, how to use the statechange inProgress property

There is an internal test of the 'rangechange' event having an inProgress property, but the test was disabled in October 2021, with the comment (by me) that the test seems to not be coordinated with actual events. The 'rangechange' event is not documented, and I don't know exactly what its

Re: [visualization-api] Re: Google Charts New Release Candidate: V52, Feb 20, 2023

Unfortunately, I did not have time to work on the histogram bug that you pointed out previously. https://github.com/google/google-visualization-issues/issues would be the ideal place to post a bug about this, which you can then track. We have not properly followed up by maintaining this issues

[visualization-api] Re: Google Charts New Release Candidate: V52, Feb 20, 2023

If you are using both Google Charts and Google Maps in the same document, you might have a problem using the 'upcoming' version. I am seeing a single instance of "var google = {};" in the default package of v52, which is loaded before any other package, or even if no other package is loaded.

Re: [visualization-api] Google charts and typescript

OK, I would like to find a workaround for you, while also figuring out what exactly is going wrong. I'll need you to do some experimenting, or if you can give me a link to an example that shows the problem you are experiencing, especially a simplified example using jsfiddle or something similar,

[visualization-api] Google Charts New Release Candidate: V52, Feb 20, 2023

Google Charts version '52' is now available. You can use this upcoming version by loading 'upcoming'. Please test the new features and let us know if you experience any issues. google.charts.load('upcoming', {packages: ['corechart']}); This release primarily consists of a large

Re: [visualization-api] Queries giving error only on Mobile Devices

Hi Avadhoot, I tried your link on my android phone, and the Table chart seems to work fine. I don't see anything in the error screenshot that you attached that suggests this is related to the Table chart. In particular, there is nothing about an ".exe" file used by Google Charts. Also,

Re: [visualization-api] List of locales

Hi Daniel, We should publish the following list of supported locals. It's a rather large subset of all the locals that Google supports. const Languages = { 'af': true, 'am': true, 'az': true, 'ar': true, 'arb': 'ar', 'bg': true, 'bn': true, 'ca': true, 'cs': true, 'cmn': 'zh', 'da': true, 'de':

Re: [visualization-api] Histogram bars between hAxis ticks

This might not be what you want, but try adding the undocumented 'type' option to your hAxis option with its value being 'category' or 'categorypoint'. It seems to override the 'ticks' option as well as affect the placement of the tick value on the edge of the bars rather than centered under the

Re: [visualization-api] DataTable "Cannot read properties of undefined" error loading json array in JS

Your jsonDataTest seems to work fine as is in this jsfiddle: https://jsfiddle.net/dlaliberte/avdgy4ws/6/ Could you create a jsfiddle that demonstrates the problem you are seeing? On Tue, Oct 4, 2022 at 1:26 PM maxdatabook wrote: > I took this json DataTable example from Google documentation and

Re: [visualization-api] Radar/spider chart

There is no off-the-shelf radar chart in Google Charts, but if you use the VegaChart, there is an example of how a radar chart can be generated. See https://developers.google.com/chart/interactive/docs/gallery/vegachart_examples#radar-chart-example Hope that helps. On Tue, Oct 4, 2022 at 5:45

Re: [visualization-api] Loading google Charts as module

The only way to use Google Charts now outside of Google is via the dynamically loaded library. We're working on open-sourcing a subset of the library, which you would be able to compile as a module into your code. No idea when that will become available. Unfortunately, even that subset will not

Re: [visualization-api] Histogram bucketSize option is ignored

Hi Emmanuel, Sorry for the delay. I've been preoccupied with other tasks. I looked into the bug and possible fixes a couple weeks ago after your messages. I didn't find an easy solution at that time, not without possible implications for always using the bucketSize option to override other

Re: [visualization-api] Google Charts License Type

Google Charts API is still proprietary at this time. You can only use the binary form of the library, and you can only do that by dynamically loading the code from www.gstatic.com. We are, however, working on open sourcing a subset of the code. On Thu, Jun 9, 2022 at 12:22 PM Efrain Rosas

Re: [visualization-api] Histogram bucketSize option is ignored

Hi Emmanuel, Thanks for posting about this problem. Glad to hear so many students are using Google Charts. I believe what you are seeing is that the bucketSize option is not actually ignored. If you change your example to set the option to each of 1, 2, 3, 4, and 5, you will see the chart

Re: [visualization-api] Try to load google sheet to interact with chart

A few points: - The 'jsapi' modules are named as such because the gstatic charts/loader.js was originally designed to serve frozen versions of the code available via the old jsapi loader. - The main thing you are missing is in your google.charts.load call, which should be:

Re: [visualization-api] Default visualization library at Google

It would be hard to argue that Google Charts, aka GViz, is the company recommended visualization library since Google doesn't support it with any headcount at this time. It is being used by over 450 projects, and I will continue to contribute my 20% time, though that is not enough time to do all

[visualization-api] Re: Why is my on pie label not aligned?

This problem of misaligned labels in the PieChart is typically due to drawing the chart when it is not visible. Maybe just move your div to before the script. It might also help to move the loader.js script tag to the header of your document. On Sunday, October 17, 2021 at 12:23:47 AM UTC-4

Re: [visualization-api] Tooltip not displaying when multiple charts on page

Hi Gary, It should certainly be possible to draw multiple charts on the same page with full interactivity for each, including tooltips. But you have to make sure you are loading, building, and drawing your charts such that they are not going to get confused with each other.We have

[visualization-api] Google Charts 'upcoming' release of v51

Google Charts version '51' is now available. You can use this upcoming version by loading 'upcoming'. Please test the new features and let us know if you experience any issues. google.charts.load('*upcoming*', {packages: ['corechart']}); *Anticipated production release date*: June

Re: [visualization-api] Re: getSelection() method stopped working

Hi Simone, The getSelection method should return whatever the current selection is, which sometimes can be "nothing". Clicking on a selected item also typically toggles the selection, so that whatever was previously selected no longer is. So, in order for us to reproduce the problem you are

Re: [visualization-api] Missing Palette (Legend) In VegaChart Heatmap

Thanks for your report, Stanley. I'm not sure yet why there is a difference between the two cases you attached, and worse, why the examples on the vegachart documentation examples now show very truncated axes. There was a change in the latest version of Google Charts (v50) such that the default

Re: [visualization-api] Re: "b.split is not a function" since version 50

Thanks for verifying that this issue is specific to MooTools < 1.6.0. This particular change that uses Array.from (which I made, actually) is part of a large migration of old code to use ES6, and from there, to use TypeScript, and along the way, avoid using some parts of the internal Google

Re: [visualization-api] Re: "b.split is not a function" since version 50

I bet it is the MooTools polyfill that implements Array.from() differently, by not supporting the Set object, or by returning something it probably should not. Here is the source of the function with the b.split call: getCells() { const cells = Array.from(this.selectedCells_); const

Re: [visualization-api] Re: "b.split is not a function" since version 50

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

[visualization-api] Re: Google Charts 'upcoming' release of v50

As of now, Google Charts 'current' version is v50. If you want to keep using v49, you can load it with, e.g.: google.charts.load('*49*', {packages: ['corechart']}); Please report problems in the google-visualization-api group. On Wed, Mar 31, 2021 at 7:49 PM Daniel LaLiberte wrote:

[visualization-api] Google Charts 'upcoming' release of v50

Google Charts version '50' is now available. As before, you can use this upcoming version by loading 'upcoming'. Please test the new features and let us know if you experience any issues. google.charts.load('*upcoming*', {packages: ['corechart']}); *Anticipated production release

Re: [visualization-api] Issue with Ajax/JSON

google.visualization.arrayToDataTable is not a constructor, but just a function that internally calls the DataTable constructor. So remove the 'new' operator and both might work. Not sure why it would work differently for each of your calls. On Wed, Mar 31, 2021 at 3:56 PM Chris Thomas wrote:

Re: [visualization-api] Re: Google Visualization API Sample

Hi Culley, The problem you are having *might* be related to the change of how queries are made in the last release, such that they are now more secure. Older versions of spreadsheets can't process the queries in the new way, hence the failure, so one solution might be to convert your spreadsheet

[visualization-api] Re: Data Source JSON response implementation

Thanks for your reports here and your feedback. This may be considered a bug in how the response is processed since it probably should not fail due to missing the semicolon. On Thursday, February 4, 2021 at 9:19:38 PM UTC-5 clade...@gmail.com wrote: > So.. finally found what was wrong... > >

Re: [visualization-api] Re: Challenges with the Select event or getSelection method?

The selection event toggles the current selection. Maybe you want just the 'click' event instead. I agree that being able to get the column index (or id even) when clicking on a table cell, and selecting a table cell, or whole column, would be a convenience for many applications. It will

Re: [visualization-api] Google Charts -- radar -- image in area?

Hi John, There is a potential solution involving use of blends to implement masking. See the issue that started it: https://github.com/vega/vega/issues/2311 The change that added blends: https://github.com/vega/vega/pull/2422 The mark documentation - look for the blend color property.

Re: [visualization-api] Data Manipulation in Table Charts - Grouping for multiple levels & in both dimensions

Hi Jamie, While the Table chart does not support a multi-level structure of rows or columns, we have been thinking about adding support for it eventually. Not that it will help for your case, but there are a couple charts that support two levels of groupings that generalize to any number of

Re: [visualization-api] Re: Google Charts 'upcoming' release of v49

Slides, Sheets, and other docs now use a separate implementation of charts, as far as I am aware. The split started a couple years ago, when the docs team wanted better support for mobile platforms, which was a problem for the Google Charts architecture at the time. Maybe after we reimplement

Re: [visualization-api] Re: Google Charts 'upcoming' release of v49

Hi Georgi, I am expecting that VegaChart will be the basis for internally reimplementing all the existing charts, as well as many new ones, while preserving the same API for each chart. The features outside of individual charts, such as Query, DataTable, and Dashboard will be maintained, and

Re: [visualization-api] Creating a custom GeoChart for US counties

d allow me to debug it. >> >> On Wed, Jul 8, 2020 at 2:58 PM Donal Harrigan >> wrote: >> >>> I downloaded all the files and took the comments out of the mapList.js >>> and couldn't find any in the .js files in the mapfiles subfolder. I put it >>>

Re: [visualization-api] Combining style, interval and certainty in Google Charts

The 'annotationText' seems to not be working, however. Maybe this particular way of rendering the annotation interferes with showing the annotationText (which is like a tooltip for the annotation). Changing it to 'tooltip' at least shows that the text is in the data. On Fri, Oct 16, 2020 at 3:33

Re: [visualization-api] Combining style, interval and certainty in Google Charts

Hi David, Your chart works fine if you include all your data columns in the DataView columns. Here it is with the necessary change: https://jsfiddle.net/dlaliberte/cvu3t7se/6/ On Fri, Oct 16, 2020 at 11:40 AM David Hyde wrote: > Hi. Have a look at https://jsfiddle.net/DavidHyde/fkuonb5s/.

Re: [visualization-api] Merging Scatter Chart and Combo Chart

Yes, it is possible to use 'scatter' as the series type. The documentation for series.type is missing 'scatter': type - The type of marker for this series. Valid values are 'line', 'area', 'bars', 'candlesticks' and 'steppedArea'. On Wed, Oct 7, 2020 at 3:49 PM Imtiaz Nur wrote: > Is it

Re: [visualization-api] Re: Time-out errors and version 49 of chart not working at all

The errors you are seeing now are at least unrelated to the query errors you saw before, so that's progress. The error about the "Container is not defined" is due to creating the chart object when the container element is not yet defined. I don't see where that is happening in your page, but

Re: [visualization-api] Re: Time-out errors and version 49 of chart not working at all

Yes, starting with a new spreadsheet document, even in the same account, should use the latest version of spreadsheets. I don't think that happens if you just copy a spreadsheet, however. On Thu, Oct 1, 2020 at 10:55 PM Hartmut Gunther wrote: > Thanks so much for the reply Daniel. > Just

Re: [visualization-api] Re: Time-out errors and version 49 of chart not working at all

Hi Hartmut, Sorry to hear about your experience, and thanks for your report. Although I don't understand why the Query requests would timeout sometimes, when using v48, but not consistently all the time, the problem with v49 is understandable since your spreadsheets appear to be using an older

Re: [visualization-api] angular & "ReferenceError: google is not defined"

That article you reference appears to be doing the kind of things I imagine are necessary to load the loader and then call google.charts.load. At the end of the second part is a link to the source

Re: [visualization-api] angular & "ReferenceError: google is not defined"

Hi Andrea, That kind of error, "google is not defined", means that at the time you use the google symbol, the loader has not finished loading. I suspect the problem might be that ngOnInit is called before the component html has been defined and/or used, so the loader has not necessarily finished

Re: [visualization-api] Custom tooltips for Timeline chart

The tooltip column for the Timeline chart should be column 2 (starting with 0). See: https://developers.google.com/chart/interactive/docs/gallery/timeline#data-format On Fri, Sep 25, 2020 at 9:31 AM Sergey Zinovkin wrote: > Hello i am trying to make custom tooltips for my timeline. As

Re: [visualization-api] Code No Longer Works: b is undefined/Cannot read property 'd' of undefined

Check in your browser's debugger to see what is coming in over the network when you try to load the page. On Sat, Sep 19, 2020 at 2:56 PM Sean Noble wrote: > No, I mean I wonder if my domain is banned from using this. Is there a way > to check if my domain was banned? > > On Saturday, September

Re: [visualization-api] Code No Longer Works: b is undefined/Cannot read property 'd' of undefined

Are you asking if the gstatic.com domain was banned? That's where the loader and all of the Google Charts API is loaded from. The error you reported suggests that you are getting a mix of different incompatible versions, perhaps due to caching, or something else going on in your web page or

Re: [visualization-api] Code No Longer Works: b is undefined/Cannot read property 'd' of undefined

It's working fine for me: https://jsfiddle.net/dlaliberte/hsuft0k1/ Can you point to your web page, in case there is something different about it? On Sat, Sep 19, 2020 at 11:53 AM Sean Noble wrote: > This code has worked without issue and now a few days ago it stopped? > There is nothing in

Re: [visualization-api] Tooltips and html content - too strick JSON validation from version 46?

OK, now I am seeing problems on the Tooltips documentation page. I'm not sure yet exactly what is failing, but I'll be looking into it. Insertion of a "script" tag in your tooltip HTML is probably disabled, and that is probably necessary because dynamically constructed scripts could do virtually

Re: [visualization-api] Tooltips and html content - too strick JSON validation from version 46?

The strictness of JSON was one improvement (for security) in recent versions, but another improvement that was also imposed is the more rigorous encoding of HTML in cases where HTML is not allowed. It should still be the case that HTML in tooltips is allowed, but as the documentation says: you

Re: [visualization-api] Re: Error "Cannot read property 'DataTable' of undefined" in code working since years

I still see: window.setTimeout(drawChart(), 5000); Which calls drawChart immediately, not after a timeout. I expect you want to wait until after the timeout, so you should instead do: window.setTimeout(drawChart, 5000); The value of the expression drawChart is a function, and setTimeout

Re: [visualization-api] the curve is not drawn completely

ould appreciate your help > > > > > > *De: *'Daniel LaLiberte' via Google Visualization API > > *Enviado: *miércoles, 2 de septiembre de 2020 02:57 p. m. > *Para: *Google Visualization API > > *Asunto: *Re: [visualization-api] the curve is not drawn completely > &g

Re: [visualization-api] the curve is not drawn completely

It's not clear if your chart is produced inside sheets (which uses a separate internal charting library), or separately using Google Charts. If it's the latter, my guess is that you should enable the interpolateNulls option, and also sort the data by whatever you are using for the horizontal

Re: [visualization-api] Google Timeline :: Bad version while using gstatic

The instructions on how to use the loader are at: https://developers.google.com/chart/interactive/docs/basic_load_libs Change 'current' to a particular version number, as described on the Release Notes page: https://developers.google.com/chart/interactive/docs/release_notes You can use your

Re: [visualization-api] Google Timeline :: Bad version while using gstatic

The loader at https://www.gstatic.com/charts/loader.js is really just the top-level loader that then redirects to another loader based on which version you are loading as specified with your google.charts.load call. So you are not escaping the dynamic loading of code by downloading the top-level

Re: [visualization-api] Re: When loading a chart, google charts shows me a message: Error in query: Request timed out OrgChart

Hi Chris, The problem is most likely that your spreadsheet URL is redirected to a new URL that you should use instead. You should be able to see the redirect in your browser's debugger, when using Google Charts version 49. Unfortunately, the redirect loses security information that is now relied

Re: [visualization-api] Re: Error "Cannot read property 'DataTable' of undefined" in code working since years

The problem is due to your window.setTimeout(drawChart(), 1); This actually calls drawChart immediately, since you wrote drawChart() rather than just drawChart. What it does after 10 seconds is try to call the undefined result of calling drawChart. You should wait for

Re: [visualization-api] Google Chart Service is not working in our application

Since you downloaded jsapi, then you missed that we are now redirecting it to the new loader. Also, the server that the jsapi loader used to load code from is now dead, which is why your copy no longer works. See the instructions on how to update your loader code at:

Re: [visualization-api] Query Wrapper Examples are throwing a "Request Timed Out" Error

Apparently some older spreadsheet URLs are redirecting to newer ones, and the redirect process is dropping some security related headers that are required for the current way queries are being done to be more secure and faster (using XHR). If you look in your browser's debugger console, you

Re: [visualization-api] Randomly getting the error "TypeError: google.visualization.DataTable is not a constructor"

Hi Alex, The angularjs component you are using should be fixed to load Google Charts properly. That may take time for someone (any idea who?) to implement. In the meantime, you should be able to add a timeout loop to your code before you start making calls to the Google Charts functions.

Re: [visualization-api] Randomly getting the error "TypeError: google.visualization.DataTable is not a constructor"

Hi Alex, Since you are calling your loadChart independent of whether google.load is done loading, then sometimes it won't be done. You need to use one of the callback mechanisms documented here: https://developers.google.com/chart/interactive/docs/basic_load_libs#callback Also, please switch

Re: [visualization-api] Re: google.visualization.Query times out in Microsoft Edge

Hi Joseph, Yes, we tested on all the modern browsers. In fact, a big reason for the change was to accommodate MS Edge. The problem now seems to be that some spreadsheet URLs get redirected (perhaps via server-side, so not visible?) which results in failures because the CORS related info is not

Re: [visualization-api] Re: When loading a chart, google charts shows me a message: Error in query: Request timed out

I believe the general problem with the timed-out Query calls that are happening in the latest version (v49) is that the original spreadsheet URL is being redirected to another server but the redirect is not done in a way that works. I've seen this happen in a couple different cases already, and I

Re: [visualization-api] Re: Google Charts 'upcoming' release of v49

I recreated your page on https://jsfiddle.net/dlaliberte/ok23q7v5/9/ and it works there, but only after I replaced your 'spreadsheets.google.com' URL with the one that it was redirected to: '

Re: [visualization-api] Re: Google Charts 'upcoming' release of v49

I don't know if this is related to why your domain appears to be 'null', but I can see that your page is loading the loader.js, and also loading the old jsapi loader, which now redirects to the new loader.You should stop loading jsapi in case that is causing the loader to be confused.

Re: [visualization-api] Re: Google Charts 'upcoming' release of v49

Hi Андрей, I believe this is due to the change in how the Query is done, such that it requires two things on the part of the server. I previously mentioned that the response must use strict JSON notation, if the server is returning a JSON response. But I neglected to mention that the server

[visualization-api] Re: Google Charts 'upcoming' release of v49

As of July 23, 2020, loading 'current' will load version '49'. If this causes problems for your use of Google Charts, please let us know, but in the meantime, you can change 'current' to '48' to get the previous version. See the Version History

Re: [visualization-api] Limit on number of charts on one page?

Looking again at your page that is not loading, there really is nothing being loaded in the browser except for an empty document, no attempt to load either the old jsapi loader or the new gstatic loader. So I would push back on the server guys to look further. If they don't have any error log,

Re: [visualization-api] Sortable table with null values always last

Hi DJC, The Table chart sorting feature doesn't have any option for sorting nulls (or undefined, etc) always at the end, regardless of the sort direction. That's an interesting idea, however, and I can see that it would be useful. We'll consider it as a feature request. Maybe the easiest

Re: [visualization-api] Limit on number of charts on one page?

There is no limit from the Google Charts side of the equation. Trying to load your page that is not loading, I don't see that it has made it very far, using the Chrome devtools, looking at the Network tab.I would guess there is some problem on your server side, but there is no evidence of

Re: [visualization-api] UTC time on LineChart xAxis

Hi Jeff, You can use the DateFormat to format a column of your data, as shown in this example: https://jsfiddle.net/dlaliberte/cxkh14sj/3/ However, that doesn't format your tick values, and unfortunately, the format option for the axes does not currently accommodate the 'timeZone' option, as

Re: [visualization-api] Winnovative HTML-to-PDF no longer converts Google charts

I pushed out another change to the loader so that IE11 won't fail. The fact that your PDF converted is working again appears to confirm that it depends on IE11 in some way, or perhaps an earlier version of IE. On Fri, Jul 10, 2020 at 1:35 AM Phil Winant wrote: > Well suddenly everything on our

Re: [visualization-api] Winnovative HTML-to-PDF no longer converts Google charts

The older jsapi loader is no longer available, except as a redirect to the new loader. The closest version of Google Charts compared to what used to be available via the jsapi loader is '45.2'. Try that version to see if it helps. Otherwise, I don't know how to help you because I don't know what

Re: [visualization-api] Winnovative HTML-to-PDF no longer converts Google charts

Hi Phil, If there is an IE11 browser involved in this converter, that would explain it. The latest loader includes a change that breaks when run in IE11 due to a missing polyfill. If this is the problem, I hope to have a fix soon. Otherwise I have no idea. That's the only thing that has

Re: [visualization-api] Re: AnnotationCharts stopped working in IE over night.

The problem is with the loader itself, since the compiler implicitly uses Object.assign when compiling code like settings = {...settings}.This was unexpected (by me) but I believe I will have a fix in a couple hours. On Thu, Jul 9, 2020 at 12:03 PM 'Cliff' via Google Visualization API <

  1   2   3   4   5   6   7   8   9   10   >