I couldnt get the button showing, no matter if I set the option to content, block, or links area. i grabbed the src of the iframe and started playing with it in a new window. I found that if I removed the language parameter out of the url the button would show. So back in the settings on the page I've removed the default english language code from the field and now the button displays!

Comments

BruFFy’s picture

Had same problem with 7.x-2.2 version.
Thx for sharing your work around!

anthonylindsay’s picture

I can confirm that this works a treat. I had actually already hacked the module to eliminate the language parameter when I saw this thread... doing it through the settings page is much neater!

Co-operatives UK’s picture

Got exactly the same problem but deleting the language setting doesn't do anything: it just reverts back to en_US.

Anonymous’s picture

#3: I had the same issue.

I found I was able to remove the language setting only when I changed another parameter at the same time. I suspect that the configuration CRUD code sees an empty language box as no-change and doesn't save.

I was able to remove the language setting only from the dynamic config, not from the static config.

I believe the language setting should be removed from the module entirely. Facebook's own button generator does not include it.

hwasem’s picture

Thanks for the language tip. I also had the same problem and removing the language en_EN from the last field fixed it. I'm using the dynamic settings option.

lliss’s picture

This was actually a bug in the settings page. I have fixed this as of the latest dev version of the 7.x branch. I'll work on backporting it to the 6.x branch.

Louis_Trapani’s picture

Thank you, Jamie! I was about to disable the module because for months it has not been displaying and nothing I did remedied it. I didn't think to delete the language setting in the module. I did so, and now finally it is displaying again. Thanks again!

gvso’s picture

Issue summary: View changes
Status: Active » Closed (fixed)

This bug was fixed in the 7.x branch, and we are not fixing this issue for the 6.x branch as Drupal 6 has reached end of life