Errors for EasySocal users

Buzzy,
The section of code that warning is being thrown in is when JFBConnect is trying to determine the height and width of an image set using og:image tag.

You can disable that image size functionality in the JFBConnect -> Social Meta -> Configuration area with the setting "Image Size Tags". We provide an option to disable it because some servers don't allow reading from files like we do there. That's an easy way to hide the warning as well, though on a production site, turning off error reporting in the Global Configuration area is a good idea anyways.

The PHP warning is just a warning and, essentially, it's saying the file can't be found.. which it sounds like it can't.. it doesn't exist. The tag is being set in our /plugins/opengraph/easysocial/easysocial.php file. Around line 69, you should see:

$avatarUrl = JURI::root().'media/com_easysocial/users/'.$joomlaId.'/'.$user->avatars;

If the files are really in the directory you mention, try updating it to:

$avatarUrl = JURI::root().'media/com_easysocial/avatars/users/'.$joomlaId.'/'.$user->avatars;

That may get you going. It's possible that EasySocial changed their avatar directory and we didn't update properly.. Feel free to test and let us know if that helps and we can try to do some more investigation on our own as well.

Thanks,
Alex

Thanks for letting us know that worked. We'll look into that fix for the next release.

Yes, it sounds easy, but we need to also make sure it won't break users on older versions of EasySocial. If it does, then we need to add some compatibility code or figure out a more dynamic way to load the image. Either way, I've added this to our to-do list to get sorted out.

Glad we could help you get things going now, but if you need anything else, just let us know!

Thanks,
Alex

Well then, we're unsure either. We did tests with both old and new versions of EasySocial and that code did work. It's possible this is a Windows server issue, permissions issue for those folders or something else more obscure.

Would you be able to PM us FTP access to your site? We should be able to narrow it down quickly once we have that.

Thanks,
Alex

Buzzy,
Thanks for the FTP access, though I didn't make much progress.

I registered on your site and went to my profile. On that page, there is an og:image tags of:That has the /avatars/ in the URL like it should. Also, the image dimensions are being properly detected. The original warning happened when the image dimensions couldn't be detected because the file couldn't be found.

Since that was working right, I then looked at the EasySocial open graph plugin file and the code hasn't been modified from our 8.0 version. I was thinking maybe you had fixed the URL so it would always have 'avatars' or something, but you hadn't.

So, from what I can see, the URL is correct in the og:image tag and the functionality is as I'd expect.

Can you double check that you're still having this issue? All I can think is that there was some caching issue on the server that cleared itself up after a while with the new release. If not though, just let us know.

Thanks,
Alex

The front-end test site does not allow Facebook authentication right now, with the following error:

URL Blocked: This redirect failed because the redirect URI is not whitelisted in the app’s Client OAuth Settings. Make sure Client and Web OAuth Login are on and add all your app domains as Valid OAuth Redirect URIs.

Could you fix the application settings to allow for the test site? Additionally, could you send Alex superadmin credentials for the backend test site?

-Melissa