Topic-icon og:url returning the wrong url

Active Subscriptions:

None
I was trying to figure out where the og:url information was being fetched from as right now its returning a improper url.. I recently tested Joomsef component on my site. and I'm worried that uninstalling that has something to do with my issue.
The topic has been locked.
Support Specialist
14 years 1 month ago #22246 by alzander
Can you give a URL that is using the wrong OG:url? From that, we can test and see what's happening. I'd recommend also:
* Clearing your Joomla Cache
* Use the Facebook Debug tool to verify that the og:url is actually wrong for the page:
developers.facebook.com/tools/debug

Good luck,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 1 month ago #22248 by fb_100000214934509
www.canbycubs.com/cub-scout-pack-503/344-pack-bbq is a example. the og:url being generated is www.canbycubs.com/cub-scout-pack-503?id=344 and is showing a 404 error on every item that is "SHARED"

I tried your suggestions prior to posting..
The topic has been locked.
Support Specialist
14 years 1 month ago #22258 by alzander
Sean,
What are you using for SEF URLs? If there is a system plugin associate with it (usually there is), try ordering things so that the SEF plugin is ordered before (lower number) the JFBCSystem plugin. Usually that does it, but frankly, sometimes the other way (after) is better.

Test that with the FB Debug Tool after each switch and let us know how it goes. If it still doesn't work, letting us know the SEF extension may provide more insight.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 1 month ago #22295 by fb_100000214934509
i discontinued use of the SEF extension and I'm just using the plain joomla built in SEF as for the re-ordering I tried a few changes and all of them have left things the same. It worked fine prior to the last 2 updates.
The topic has been locked.
Support Specialist
14 years 1 month ago #22302 by alzander
Sean,
Not sure why it's looking like that. Is that a standard Joomla article, or is it from some other extension. We did change how we generated the og:url tag slightly in this last release. The intent was to make it more compatible with a few links that weren't generated properly before. It's possible we broke something here. We test heavily with Joomla content and some other things, so that would be strange if that's what's broken, but always possible.

Let us know. We may ask for admin access as well, if you're ok with it, if it is Joomla content or something else that shouldn't have any issues so that we can see your configuration.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 1 month ago #22331 by fb_100000214934509
it is a standard joomla article. and that was my thought... somehow something was changed in the url processing. like I said it worked perfectly fine before i did the last updates.
The topic has been locked.
Active Subscriptions:

None
14 years 1 month ago #22341 by mhirschberg
Had similar issues after upgrading. I inserted override codes and it did the trick. But it's very strange. After thte updated everything went wack with the og:... my site is myucrivine.com
The topic has been locked.
Support Specialist
14 years 1 month ago #22348 by alzander
Can one of you Private Message me admin access to your site so we can test with your configuration? Like I mentioned, we did make a change in 4.2.x for the URL generation. It's been out a few weeks now, and we haven't heard of issues, but obviously, we'd like to fix any problems that may exist.

Also, let me know exactly how the current Open Graph tags are being added (when it doesn't work). I'm assuming you're just letting JFBConnect add it automatically, but if not, let me know.

Thanks, and we'll get you straightened out,
Alex
The topic has been locked.
Support Specialist
14 years 4 weeks ago #22419 by alzander
Sean,
Can you resend the admin details? The information you Private Messaged me isn't letting me into the admin area so I can check some things out. Would love to get to the bottom of this and include a fix in the 4.2.2 release (next week).

Thanks,
Alex
The topic has been locked.