title: Facebook LIke update through Ajax - not simple issue
body: <p>I have created a video page that loads videos dynamically using a database while the files are stored on the server. A video is preloaded on the page and that data can be Liked and posted to Facebook with no issue. When a new thumbnail is clicked, I'd like the Facebook Like information to change to the new video content (title, url, and image).
  I've looked for a solution and there are many similar ones but their simple solution of adding <code>FB.XFBML.parse();</code> isn't working for me.
  I update my meta tags when the Ajax call comes back successfully using:</p>
  
  <pre><code>$("meta[property=og\\:title]").attr('content', videoTitle); 
  $("meta[property=og\\:url]").attr('content', "www.mySiteURL.com/index.php?videoID="+videoID);
  $("meta[property=og\\:image]").attr('content', "www.mySiteURL.com/images/video/"+videoImageName);
  </code></pre>
  
  <p>But when I run the parse code right after these are set, I see the button refresh but it sill has the same content.
  I can see that the meta tags actually update using Firebug.  It's just that the FB button doesn't properly re-scrape the page info to send to FB. I have the namespace set in my html tag and I have the other og:metas set up as well, but these are the three that I need to be re-scraped.</p>
  
  <p>I saw in one post that someone used something similar to <code>ajax.complete(function(){FB.XFBML.parse();});</code> directly on the main page, I don't remember the exact code, but the idea was the same, and it still didn't work.  I figured just running it within my ajax function, on success, would be sufficient.</p>
  
  <p>Am I missing anything?</p>
  
  <p>Any help would be greatly appreciated!</p>
  
  <p>Thanks.</p>
  
  <p>Edit:
  I should add that each video has its own direct URL that is inserted into the og:url since they are all loaded through ajax. 
  The Facebook Linter/Object Debugger shows me all of the correct data for each video when I use one of these unique URLs, it's just a scraping issue - at least, with my limited knowledge on this, that's what it seems to be to me.</p>