Support » Plugins » [Plugin: Wordbooker] Bug – Invalid Markup

  • Not sure if this is unique to 3.0 or I just never noticed, but Wordbooker emits invalid markup on the new Twenty Ten theme. Need to be more selective to keep FB junk from being emitted on public pages. Assuming all of the Facebook Connect stuff only needs to be output on the options page then you’d have something like this:

    if ( isset($_GET['page']) && $_GET['page'] == "wordbooker" ) {
    add_action('wp_head', 'wordbooker_header');
    add_action('wp_footer', 'wordbooker_footer');
    add_filter('language_attributes', 'wordbooker_schema');

Viewing 3 replies - 1 through 3 (of 3 total)
  • I’ve never noticed it throwing “FB junk” out on public pages. Can you be more specific than “junk”?

    As I’ve been concentrating on Oauth changes I’ve not looked much at 3.0 yet and I’ve not looked at 2010 at all.

    FB uses W3C invalid markup for the XHTML tags – there are some changes that can be made to the doc-type – but I imagine 2010 uses the wrong doc-type.

    Anyway I see you’ve deactivated wordbooker on your blog.

    The latest patch set which will be released as 1.8.5 later today supresses the inclusion of the FB share/like code unless you have chosen to turn those options on.

    Deactivated because I’m moving away from Facebook. Was using Wordbooker to try and get people who don’t normally subscribe to blogs to follow posts out of their news feed, but no result. Plugin works great so keep up the good work.

    The rest of the unwanted output was down in the footer:

    <div id="fb-root"></div>
          window.fbAsyncInit = function() {
             appId  : '254577506873',
              status : true, // check login status
              cookie : true, // enable cookies to allow the server to access the session
              xfbml  : true  // parse XFBML
          (function() {
            var e = document.createElement('script');
            e.src = document.location.protocol + '//';
            e.async = true;
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Plugin: Wordbooker] Bug – Invalid Markup’ is closed to new replies.