I am using "webtechnick CakePHP-Facebook-Plugin" for my site for login and authentication. My site is in cakephp. I have placed the plugin in proper folder as guided in the video. But when I am running my site I am getting the error:
Fatal error: Call to undefined method Facebook::login() in
/home/depasser/public_html/var/www/html/fb_app/app/views/elements/login.ctp on line 12
I have tried a lot to solve this issue but haven't succeeded. Can anyone guide me how I can solve this issue?
Is the helper in your controller for this view, if the 'Facebook.Facebook' helper is not there it wont work.
Related
With Facebook SDK V5, I'm trying to develop a php script who list all my pages where I'm admin. Then the goal is to add a Custom Tab on the selected Facebook page.
The first part works well but when I'm trying to add the Custom Page, I have a Fatal Error.
I want to clarify that I already develop this king of script with SDK V4 (who works well). So my 2 facebook apps are well configured (manage_pages is ok for install and Secure URL of the Page tab is complete).
This is the lines of code who generate the Fatal Error:
$addTab = $fb->post('/' . $page['id'] . '/tabs', array('app_id' => 'myappid'), $page['access_token']);
$addTab = $addTab->getGraphNode()->asArray();
print_r($addTab);
The contents of $page['id'] and $page['access_token'] are OK. When I test the Acccess Token, it's also ok.
When I execute the script and try to add the custom tab, I have this message:
Fatal error: Uncaught exception 'Facebook\Exceptions\FacebookAuthenticationException' with message '(#33) This object does not exist or does not support this action' in /home/web/...
I don't understand the problem, so any help is welcome and will be of great help to me. Thank you!
i have a problem here maybe sameone can help me: i install the Socialite pakcage to my laravel project and in start it work perfect with facebook , google and linkedin provider. But now it get always this message when i try to connect with facebook , and other provider connect perfectly.
What's wrong ?
ClientException in RequestException.php line 111:
Client error: GET https://graph.facebook.com/v2.8/me?access_token=&fields=name,email,gender,verified,link&appsecret_proof=5fbda0d218f94cb8024712269c053f0186d360efd82cd358b588eaf621e0c79c
resulted in a 400 Bad Request response:
{"error":{"message":"An active access token must be used to query information about the current user.","type":"OAuthExce (truncated...)
I fix the problem !
You need the make same changes in vendor/laravel/socialite/src/Two/FacebookProvider.php file
See here:
github socialite
composer update will fix it by updating the laravel/socialite version
Oh, so I'm not the only one. Good. Waiting on the answer, I've lost like at least 60mins trying to figure this out, I'm quite sure it's gonna be something Facebook related. They're killing their 2.2 api, I guess, today, maybe they messed up something. :/
On our server-side authentication with Facebook we get a random and weird issue. Facebook calls the call back URL two times with the same code. This is only happening for some users and not on every login.
This is the flow we have implemented on our side: https://developers.facebook.com/…/manually-build-a-login-fl… . We have been using it since the beginning of 2013 and we haven't noticed any issues so far.
And this is the error we get when we are exchanging the code for an access token the second time.
{"error":{"message":"This authorization code has been used.","type":"OAuthException","code":100,"fbtrace_id":"traceID"}}
We tried to log this issue as a bug on https://developers.facebook.com/bugs but unfortunately it doesn't work.
It keeps showing unexpected error. Not to mention that i was unable to find the correct bug category.
Any idea on how we can fix this?
Thanks!
Could it be that users are clicking twice to process auth service? Try disabling the button before calling Facebook auth service
What language are you using?
I just had this problem in Ruby using Devise for Rails. I had created an omniauth.rb initializer file, and added a config line item in the devise.rb initializer file.
If you did this too, you can remove the omniauth.rb initializer file and you should be good to go!
i have been following some online screencasts and tutorials about zend_auth.
i have a basic zend application created by the zf tool.
within the index controller index action i place a little code to test if a user is authenticated.
if(!Zend_Auth::getInstance()->hasIdentity())
{
$this->_redirect('login');
}
now as far as i'm aware this should check to see if the current session has been authorised with an identity if it hasnt (ie returns false)
it will redirect the screen to the login controller index action.
all i get is the default error action page stating
An error occurred
Application error
does anyone have an idea wtf is going on.
i have a suspicion it has something to do with needing to set up an autoloader but i have already set an include path to the library folder . (plus i have no issues with accessing controller actions and the likes.
i had another issue with a form stopping my application from rendering anything but i will create another question about that.
thanks keyne setting the error reporting on was a good idea
for some reason i thought i had my app sent to development but it was production.
after looking at the error report i found i had forgotten to create a data folder on my test server to hold the session information.
so zend_auth creating a session failed to location the directory.
Has anyone succeeded in using AsyncFileUpload in DotNetNuke? Although the module is marked as "allow partial render", I get two errors in web page, as alerts:
Unhandled exception: Access is denied
and
Unhandled exception: the requested file uploading problem
How can I solve it? The classical input type="file" is not working with ASP.NET AJAX.
I believe classic input type=file does not work within an AJAX UpdatePanel as the file does not get posted to the server. You can get around this by using a PostBackTrigger (http://www.codeproject.com/KB/ajax/simpleajaxupload.aspx).
I'm afraid I'm not sure about why it won't work in DNN.