The "Facebook Connect Login to !app" refuses to be placed in any of my themes blocks - I set it to any of the available regions (regions tested and working with other blocks) and upon saving the block configuration the block is placed back into the disabled section and does not appear on the site anywhere.
I have made the necessary changes to my theme, according to the README.TXT:
Top of page.tpl.php:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="http://www.facebook.com/2008/fbml">
Bottom of page.tpl.php
<!-- http://wiki.developers.facebook.com/index.php/JavaScript_Client_Library -->
<div id="FB_HiddenIFrameContainer" style="display:none; position:absolute; left:-100px; top:-100px; width:0px; height: 0px;"></div>
I have also just updated to beta2 which was just released, hoping that perhaps the problem was a bug in beta1.
I have my app setup as both a Connect and Canvas app. I can place the code into my template by hand ... and when I click the connect button I am prompted to connect through the FB Popup ... and it would appear that my user shows up in the User List (unsure whether this occured because of running cron or not but the user did not appear 'at first' and now does as I'm writing this - possibly a beta2 fix as well?).
Any idea why the Login Button block would refuse to be set?
Comments
Comment #1
Dave Cohen commentedThe problem people tend to have with that block is they configure it with the Filtered HTML input format, which will strip all the XFBML tags out. So be sure to choose unfiltered html or php or some filter which will leave that markup intact.
As for not being assigned to a region... never heard of such a thing! Weird, but not something that can be fixed in these modules. The problem (and fix) is somewhere else.
Comment #2
Dave Cohen commentedDo you actually see '!app' on the admin pages? If so, you need to create a Facebook Application node. You should see the node title and not '!app'.
Comment #3
coworksbe commentedThe block not being able to be saved in the region could be because of the use of spaces in the app name. (as the block is called login_APPNAME)
Comment #4
Dave Cohen commentedThe app has both a name and a "label" the block should be using the label. Only adminstrators see the label, so give it something with no spaces or other funky characters.
The code should validate for this but at the moment does not.
Comment #5
brisath commentedSame problem here. I chose "php" and "full html" for the input method, but moving the block into a region on my theme is rejected each time.
Comment #6
Dave Cohen commentedtry some other block. I can't imagine the problem is caused by Drupal for Facebook.
Comment #7
brisath commentedI've tried moving it to different blocks too, but that doesn't work. The other Drupal for FB blocks move fine, but this one does not. I'll report back if I have any success otherwise.
Comment #8
nattsI had this problem, but kcoworks' suggestion of removing space characters from the label name of the application worked.
Comment #9
gstout commentedDefinitely a problem with this module Dave. Per above suggestions I renamed my app from "gregstout.com" to "gregstoutcom" and was finally able to place the login block. Prior to that on save it would simple return to the disable section of blocks.
Really excited for the beta! Thanks for all your great work.
Comment #10
Dave Cohen commentedOh thanks for that clue. That explains it.
The 'label' field should be letters and numbers only. No spaces or anything else. The description says that, but its not enforced by validation. At least not yet.
Comment #11
Dave Cohen commentedNow I see that the solution was pointed out earlier in the thread. Thanks all.
Finally, I did something about it. From now on, the code will validate the application label. If you have this problem, manually edit your apps and change the labels.