• Index
  • » Users
  • » Corsulian
  • » Posts



So I created a new application, updated the keys, and tested things out: worked just as intended.

When logged into <!-- m --><a class="postlink" href="http://www.corsulian.com">http://www.corsulian.com</a><!-- m -->, I could connect with Facebook without a problem.

I then decided to follow the cross-domain receiver error instructions as well just to make sure that didn't happen.

Now, upon navigating to <!-- m --><a class="postlink" href="http://corsulian.com">http://corsulian.com</a><!-- m -->, I was expected to be redirected to <!-- m --><a class="postlink" href="http://www.corsulian.com">http://www.corsulian.com</a><!-- m -->.  I was not redirected.  When I tried connecting by Facebook while still at <!-- m --><a class="postlink" href="http://corsulian.com">http://corsulian.com</a><!-- m --> and that's when the whole "new window with no navigation" weirdness appeared.  That was probably always the case but I just never bothered to type "www" for my own site.

I repeated the steps a few times to confirm.

<!-- m --><a class="postlink" href="http://www.corsulian.com">http://www.corsulian.com</a><!-- m --> works just fine.
<!-- m --><a class="postlink" href="http://corsulian.com">http://corsulian.com</a><!-- m --> sporadically throws the cross-domain receiver error and, when it doesn't, it opens the site in a new window with no navigation.

It seems the problem may lie somewhere in the redirect - but I compared the two app settings just to make sure and I was surprised to find differences as I had only filled in the minimum things for both:


Profiles tab
Publisher Mode
Old App: Inline
New App: Dialog (Legacy)

Canvas tab
Canvas Callback URL
Old App: <!-- m --><a class="postlink" href="http://www.corsulian.com/">http://www.corsulian.com/</a><!-- m -->
New App: <!-- m --><a class="postlink" href="http://www.corsulian.com">http://www.corsulian.com</a><!-- m -->

Advanced tab
Session Secret Whitelist Exception
Old App: Disable
New App: Enable

Attached examples for both IE and Mozilla.

I use Firefox - though IE7 is showing the same thing.

Good - that's where I had set the redirection just as a test.

I switched it back to "home" and, oddly enough, when I tried to log in with Facebook just now, I received the cross-domain error receiver URL:

The Facebook Connect cross-domain receiver URL (<!-- m --><a class="postlink" href="http://***/index.php?option=com_jfbconnect&view=xdreceiver&format=raw#fname=_opener&%7B%22t%22%3A3%2C%22h%22%3A%22fbCancelLogin%22%2C%22sid%22%3A%220.255%22%7D">http://***/index.php?option=com_jfbconn ... .255%22%7D</a><!-- m -->) must have the application's Connect URL (<!-- m --><a class="postlink" href="http://www.corsulian.com/">http://www.corsulian.com/</a><!-- m -->) as a prefix. You can configure the Connect URL in the Application Settings Editor.

This has happened before so I did what I always do in this case: log into Facebook, click Connect on my site, and then click Logout on my site.  At that point, I can login with Facebook just fine.

Still giving me no navigation.  I tried with another Facebook account - same result.

I actually had no callback URL listed in the Canvas section.  I added it but it had no effect.

I have it set not to redirect on a Joomla login.  I tried setting it to redirect to a few different areas on a Facebook login but, no matter what I selected, the home page always came up.

<!-- m --><a class="postlink" href="http://www.corsulian.com">http://www.corsulian.com</a><!-- m -->

My login module and connecting with Facebook have always worked just fine on my site.  However, the successful connection brings up the site in a new window with no navigation scroll bars or menus.  Just a navigation bar and no apparent way to get these things back.

This is while using Mozilla Firefox 3.0.10, Joomla 1.5.10, and the latest JFBConnect.  No JomSocial or CB integration.

That worked beautifully.

Thank you.

How did you "deny access" to it in phpmyadmin?

I also received this exact error upon uninstalling the component.  I tried just re-extracting the component and making sure the files referenced in the errors are there - but it has had no effect.  I suppose the issue was uninstalling the component prior to uninstalling the plugins?

Warning: plgAuthenticationJFBConnectAuth::include_once(***/public_html/administrator/components/com_jfbconnect/models/config.php) [function.plgAuthenticationJFBConnectAuth-include-once]: failed to open stream: No such file or directory in ***/public_html/plugins/authentication/jfbconnectauth.php on line 20

Warning: plgAuthenticationJFBConnectAuth::include_once() [function.include]: Failed opening '***/public_html/administrator/components/com_jfbconnect/models/config.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in ***/public_html/plugins/authentication/jfbconnectauth.php on line 20

Fatal error: Class 'JFBConnectModelConfig' not found in ***/public_html/plugins/authentication/jfbconnectauth.php on line 21

Yeah that outlines what I was thinking pretty well.  I only had it in the CB thread because, at least on the sites I was envisioning this for, I currently use CB - wasn't sure how much that changes the code used in mapping.

While we're dreaming, some level of "account synchronization" would be helpful but that's not entirely realistic (e.g., change your phone number on Facebook and it changes it on Joomla - but would become very complicated between different field types, privacy settings, and master-slave relationships).

I would never try to compete with the features Facebook offers - it's futile.  But I think your components can really leverage Facebook's broad recognition.  People are registered on dozens of forums and sites at any given time.  Convenience keeps them coming back.  If I can tell them, "don't worry about remembering how to log in - just use your Facebook account," then that simplifies things.

This might be against the grain but...

What is the potential for a version that only focuses on the authentication?  I have several sites that do not support open registration.  That is, only known members of an organization are permitted to be registered.  I would specifically not want any sort of user creation mechanism - the only thing I'd look for is the authentication piece so that someone registered could log in with Facebook credentials.

I get different behaviors throughout the day when testing the login module & component.  Sometimes I get the whole invalid URL prefix - but only every so often.  I have the URL correctly specified in the Facebook application itself.

More strangely is that while using Firefox and logging in with Facebook credentials, the site loads in a new window that has no navigation options.  No sliders, no menus, nothing.

Sometimes, when I logout, I receive an error page stating that the correct page cannot be found.

Other than the new window with no navigation, none of these errors seem to have any consistency.

Consider this an official request.

  • Index
  • » Users
  • » Corsulian
  • » Posts

Board Info

Board Stats
Total Topics:
Total Polls:
Total Posts:
Posts today:
User Info
Total Users:
Newest User:
Members Online:
Guests Online:

Social Stream
Refer and Earn

Like our extensions? You're not alone! That's why they're used on tens of thousands of websites. Now you can earn 20% of any sale you refer to SourceCoast.com.

We provide excellent documentation, well laid out sales pages and great support. All you need to do is spread the word and we'll take care of the rest.

Learn About Our Affiliate Program