Facebook Javascript library inclusion

I'm at a loss. I'm not sure what's causing the difference. I installed JFBConnect v4.3.4 (the last of the v4 series), and the buttons showed. When moving to v5.0, they no longer show.

Sorry, my message got cut off:
Here's what I can tell you:
* The buttons show with the standard RT Gantry template
* It doesn't seem to be a system or content plugin interfering
* Something is specifically removing our buttons from the page. If you open the HTML, you'll see a div with a class of "scsocialbuttons". Inside that div is where our social buttons should be.
* Additionally, if you disable the JFBCSystem plugin, you'll then see all of our tags ({JFBCLike xxx}) showing up on the page. Those tags are replaced with the social buttons.

So, something in the specific template you're using is removing the buttons we're inserting, and I don't know how or why.

Oh, and additionally, the difference between v4 and v5 is that we switched the HTML that we insert into the page to use Facebook's newer (and recommended) system.

The v4.x tags looked like:The new v5.x tags are more HTML compliant and faster. They look like:
At this point, the only things I can suggest are:
* Using v4.3 of JFBConnect. I wouldn't recommend v4.2 due to how old it is.
* Contact RocketTheme to see if they have any ideas why that specific template would be removing those tags.

You may also want to try adding a JFBCLike module on the page and see if that gets stripped. Just out of curiousity as it may help narrow things down.

Hope that helps, though there's no great solutions in there.

Thanks,
Alex

Mfazalb,
Strangely enough, in v4.2 and 4.3, if you enabled the RokBooster plugin, you would have run into the same issue. At that point RocketTheme's 'optimization' plugin was replacing any instances of:withIn other words, they were removing the fb: from the statement, which was required. You can see the note about it in our v5.0 changelog "Enh: Compatibility improvements with RokBooster by RocketTheme

The change we made was to move to the newer methods that Facebook recommends for implementing the widgets, which is to use the following tag:So, I don't know why that specific RocketTheme template is stripping out the code between the scsocialbuttons tags (which you can see on the page). It's not happening with other RocketTheme templates and it's not being caused from a system or content plugin. The only remaining 'unknown' is the specific template that you're using. And again, we've seen RocketTheme extensions modify our code in the past.

I don't have an answer for you, and I'm not sure I'm going to be able to get you one. I'd highly recommend contacting RocketTheme and ask them if they have a clue as to what may be happening. I don't know their template architecture or know all that goes on in them, so it would be difficult for me to diagnose.

The only suggestion I have would be to use v4.3 until we have an answer from RocketTheme. If you want, I can send you JFBConnect v4.3 through Private Message and you can use that.

Thanks,
Alex

I'm not seeing where the JFBCComments should be appearing on that page. The 'div' that should contain our comment box isn't appearing at all. Are you sure it's configured properly to show there? I'd love to see it showing, or not showing (with the same behavior on the content pages) as that would help narrow things down a bit.

For the other FB Like plugin you're using, can that be configured to show within content articles?
Can you configure a JFBCLike module to show on all of your pages, content and SobiPro, so we can see if it works on the Sobi pages?

We'd love to get to the bottom of this as much as you, but there isn't anything in our code that I can imagine that would be displaying the behavior we're seeing. There must be some other extension/template conflicting and we just need to narrow down why and why. The 2 tests above could be very helpful since, if the other extension does work on content it says there may be something wrong with JFBConnect. Whereas if our extension works on Sobi pages (or on content pages, but not 'within' the article), that would point to something RocketTheme is doing to filter out social stuff inside the content area.

Even our login button *was* upgraded to use the new syntax, and that's working site-wide. So that's making me think it's something specific to social widgets within content.

Keep me posted,
Alex