I have been using the legacy Featureloader.js.php script for some time now without any problems at :
https://ssl.connect.facebook.com/js/api_lib/v0.4/FeatureLoader.js.php
For some reason this server seems to have stopped responding in the last day or so - i get a server not found response in Chrome developer tools -
We want to continue to use the Fanbox plugin, as it allows us to style the returned content appropriate to our site - the new likebox doesnt have that option
Wondered if anyone knew why that server is currently not responding, and whether it's simply a temporary problem or might be a permanent issue?
Thanks
From the Facebook blog:
Removing FeatureLoader JavaScript SDK. As part of the OAuth2 migration, we announced that the FeatureLoader SDK is no longer supported as of October 1st, 2011. On February 1st 2012, we will remove FeatureLoader. Please ensure that your app is using the JS SDK.
See here: https://developers.facebook.com/blog/post/638/ (under "Upcoming Breaking Changes on February 1st 2012")
Related
I am trying to implement a project when I get some data from a google spreadsheet and insert into a database. Inserting part is not important for me yet. When I am trying to get the data from google spreadsheet document I get this Warning!
WARNING! You must upgrade to the latest version of google-spreadsheet!
Google's deprecation date for the v3 sheets API is March 3rd 2020
Bad news - this version of this module will stop working on that date :(
Good news - the new version of the module uses the newer v4 api :)
However, there are breaking changes, so please see the docs site
https://theoephraim.github.io/node-google-spreadsheet
It's still give me the data, but I get the warning.
Somebody who knows how do i get rid of that warning?
The Google Sheets API has been upgrade from version v3 to version v4
What does it mean?
It means that certain method names, parameters and building of the authentication client have changed.
If you are using an old code based on v3, so building the authentication client as
const sheets = google.sheets({version: 'v3', auth});, your code will stop working in the near future
While Google specifies March 3rd 2020 as the deprecation date, there is still some grace period, but your code could stop working any time!
So, please update your code by changing to const sheets = google.sheets({version: 'v3', auth});
Adapt other parts of the authentication flow if necessary to the new procedure provided in the quickstart for v4
Go through the references to see if any of the requests you are using has changed and adapt as necessary.
We are using the Office Plugin with the Office javascript API version 16.0. After the update on August 13th to version 1907 (Build 11901.20218) for our Monthly Channel and version 1902 (Build 11328.20392) on our Semi Annual Channel users we are no longer getting the email address from the userProfile using the javascript API call to Office.context.mailbox.userProfile.emailAddress. This returns a null on every call. Is anyone else experiencing this issue? Or know of a solution? Thanks.
We have tried this on versions of Outlook prior to the August 13, 2019 update and the plugin works as expected.
The solution I found was to reference the CDN office.js from appsforoffice.microsoft.com/lib/1/hosted/Office.js instead of a local version of the office.js
I am using two different third party programs (different companies) that apparently use the Google Maps Javascript API. When they load the map, the world map is shown, but an Error message is displayed: "Der von Ihnen verwendete Browser wird von Google Maps Javascript API nicht unterstützt. Verwenden Sie einen anderen Browser". (Translation: The browser you are using is not supported by Google Maps Javascript API. Use another browser). I am using Windows 7 and Internet Explorer 11.0.48. Early 2017 the programs were working correctly. I changed the default browser to Chrome using the option provided by chrome, but the error still appears.
Is there a workaround on the user side?
Regards
Peter
One of the programs is downloadable from http://www.codres.de/google-map-saver (GMS.NET), the other one came with a GPS logger from Canmore GPS on CD ROM and dates from 2013.
Both show the same behaviour, GMS.NET after clicking the button "Go to location", GPS Photo Tagger right after start up. The english error message is "You are using a browser that is not supported by the Google Maps JavaScript API. Consider changing your browser. Learn More, Dismiss". When I click "Learn more" I am told that IE 11 is my current browser. When I click an internet link in an e-mail Google Chrome is used (as default browser). It seems to me that the JavaScript API does not recognise Chrome as the default browser. IE11 is not run in compatibility mode. The Notebook I am using runs Windows 7 64bits.
I clicked the link in geocodezip's response. This sample works correctly calling Chrome (even when I copy the code into MS Word). When I open the link in IE11 it also works correctly. Is it possible to define the InternetExplorer as default browser in the Javascript API? This might be the reason for the different behaviour of the geocodezip sample and my programs. In this case the programs would have to be mended.
It seems a number of programs show this error since late 2017. The underlying problem here seems to be that they are all using an embedded webbrowser relying on IE technology. This embedded webbrowser needs to signal the proper IE version to the Google Maps JS library. Unfortunately, only the programmers of that software can do this. Adding the following to the page's source usually helps:
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
Look here
https://developers.google.com/maps/documentation/javascript/versions
<script async defer src="https://maps.googleapis.com/maps/api/js?v=3.31&key=YOUR_API_KEY&callback=initMap">
see v=3.31
latest is now 3.32 and if is not specified it will use the latest
And here
https://console.developers.google.com/apis/credentials/key/
check all api restrictions
I had the same issue with users on Windows 7 IE and no Chrome browser installed.
Added the following line :
<meta http-equiv="X-UA-Compatible" content="IE=11" />
Which seems to have resolved.
It seems that Google has dropped support for legacy systems (like Windows 7, earlier versions of IE) in Javascript API even with v3. It was working until this month, and what i also noticed that adding "v=3" string to maps api URL is no longer helping IE clients to run it without error. It's not a good behaviour of Google that there are older clients using v3 api with older IE verions which were working perfectly until this month.
I have copied the sample code from the OneDrive Picker JS example to my playground site, replaced the clientId with mine, and then when trying it in MS Edge, the new window will open. After signing in, it displays the original page instead of the picker. Why isn't it showing the picker? In all other major browsers (including IE 11) it shows the picker...
I tried toggling the option Allow Implicit Flow in the App registration page but that didn't help.
Update 9/23/2016
I downloaded the sample code to my site, pasted in my clientId and loaded it in Edge - the issue still persists. This leads me to believe it is an issue with the app registration. In the app registration I see that there are options for selecting Microsoft Graph Permissions - both Delegated Permissions and Application Permissions - I tried adding Files.Read and then Files.Read.All but neither improved the situation. Is there another setting in the registration I should configure?
Update 10/3/2016
I noticed the other day that the browser requirement for Edge is version 25+ and I had version 20. I spent a few hours installing non-critical updates to the OS, which updated Edge to version 38. Now when I try the sample code on my playground site I see the new window open, the main window will refresh within a few seconds and after I login in the new window, it stalls on this oauth2 authorize url.
Turns out it was a Windows 10 network group policy that was blocking this.
I am newbie to scripting and website designing. I am helping as well as getting hands on experience on my friends website. Earlier instafeed was working but since last couple of days its not showing any instafeed.
check the website. http://qminmagazine.com/
Please help me to figure out whats wrong.
Thanks in advance.
-Jitu.
So, a simple network capture throws the following error:
Error from Instagram: The access_token provided is invalid.
On June 1st 2016, Instagram rolled out new API restrictions, which limits users to accessing only their own content through the Instagram API by forcing each app into a sandbox. To get access to public content, your app must be manually approved by Instagram.
Chek Instagram's update from the 17th of November 2015 :
Instagram Platform and documentation update. Apps created on or after Nov 17, 2015 will start in Sandbox Mode and function on newly updated API rate-limits and behaviors. Prior to going Live, and being able to be used by people other than the developers of the app, these apps will have to go through a new review process. Please read the API documentation or the Change Log for more details.
Any app created before Nov 17, 2015 will continue to function until June 2016. After June 2016, the application will automatically be moved to Sandbox Mode if it wasn't approved through the review process. The previous version of our documentation is still available here.
With the new rules, having Instagram tag feeds of public content isn't an acceptable use case, so even if you try to get your app approved, it most likely won't. So, with Instafeed you can only get your own posts, severely limiting its functionality.
This GitHub discussion delves deeper into the topic and available workarounds.
How to submit for permissions review
Go to Manage Clients and select the app you'd like to submit for Permissions Review
Click the Permissions tab
Click the Start Submission button
Describe the purpose of your application and how you intend to use each permission