I'm struggling with my Facebook Connect after December the 13th.
Here my Facebook.php based on the old PHP SDK 2.0 - hoping someone can point me in the right direction in order to make it functional again.
http://pastebin.com/Mvu1JeZY
I've read that $session is now $user - and params in the JavaScript is now scope.
What else would need to be changed?
Specifically, is this still valid?
http://pastebin.com/8VAv0te5
My JavaScript is getting the login and user correctly. Its my PHP which needs an update.
there was many changes between SDK 2.0 and 3.x.
As I see in your code, you use old cookie function which will not work. There was similar problem here
Some changes and quick fix for them you can find here
You should use the new oauth sdk : http://developers.facebook.com/blog/post/614/
Related
So it's the first time I'm trying to use the google reCAPTCHA v3 (actually it's the first time I'm using any kind of captcha).
I followed the documentation and a very basic tutorial.
What I understand is that I should be able to see the token in my browser inspector.
The first issue is that i can see the logo on the bottom right of my screen, but there is definitely no token in my input.
The second issue comes from the browser console which indicates 3 kind of errors.
I'm working with Symfony Framework on a local environment.
Any clue would be much appreciated !
My twig & javascript files
Browser screenshot
Content-Security-Policy issues
So i figured out how to get the token....
I just had to remove those lines in the js file:
function onclick(e) {
e.preventDefault();
I still didn't find about the Content-Policy issues.
I am new to Kong and microservice. I am using Kong CE version 0.14.1 and I need to secure an existing API through Oauth2.0 plugin.
I tried to follow the instructions in the documentation kong-oauth2-hello-world provided by Kong.
The problem is when I click on the Authorize button, I always get undefined. I don't get the code that provides the token like the documentation.
I think I missed something or I misunderstood the instraction.
Here the environment variables I used by the Node.js application.
Could anyone help me understand the reason why I get undefined ?
Thank you
I just replaced "openweathermap.org" with "mockbin.org" and it works fine
This video is showing how to embed tweets in umbraco 7. In the current version it does not seem to work anymore. When I try to do it I get the error message "not supported".
Is there anything additionally to do to get this working? Any additional packages?
I think that feature uses OEMBED, it's possible that Twitter have updated their API and the functionality is broken. I'd log an issue on the Umbraco Issue logger: http://issues.umbraco.org so that the core dev are aware of the issue and can investigate further.
Could also try this package https://our.umbraco.org/projects/website-utilities/utwit/ , have used it before and works perfect but haven't tried it on v7 yet but it says it work and i trust Matt (the guy that made it big umbraco dev and contributor) so should work.
I need rally api to get data for Release Burnup, to display chart in iOS. I tried rally rest api, but i'm having a trouble to figure out how it works. Can anyone help me? Here is the link for https://rally1.rallydev.com/slm/doc/webservice/ where you can get more info.
See Developer Portal here for links to API toolkits and for javascript AppSDK2. There is no toolkit specific for iOS. A built-in ReleaseBurnup served by a first generation analytics service can be displayed via AppSDK2rc3 StandardReport component. This is the same report that used to be available in AppSDK1, so for the supported config parameters see this page.
End up using look back apis, worked for me.
I'm trying to use the 'GetKeywordVariations' method of the google adwords API, documentation at this page. According to the documentation, it should return these fields, including lastMonthSearchVolume. When I try this, i get all the fields except for lastMonthSearchVolume. Does anyone know why?
I found the answer. i was using the older version of the API. Updating to the latest version fixed it .