JoePublisher - 7:29 pm on May 13, 2011 (gmt 0)
@freejung, you are quite correct, this could have unforseen consequences that you describe, particularly if left for an extended period of time without being tackled.
@rlopes it seems to work fine for me, it redirects the affected user to the clean url and when they press the XFBML 'like' button it works as intended, in other words a 'like' is registered - (from what I have seen and understand the bug is not triggered on pressing the 'like' button it is triggered by merely landing on a page with the like button XFBML code on it). I just went and checked on a computer that I know triggers this bug on my site and it still works for me ...
@levo, this is a good suggestion, but when I instituted this 'fix' (back when researching this problem) I tested it out before going 'live' and I got 2 visitors landing on a newly created 'channel' url on my site, and the analytics I use recorded this as being seen 30 times by these 2 unique visitors ? why they were unique when they were both me testing it out, and why it should end up as 30 page views is beyond me ... it might / should work for others, but for now I am sticking with what works for me. As a side note the facebook coders themselves have doubts about it working for everyone, they introduce using channels as a possible 'help' and not a 'fix'. Give it a go though, it might work.
I think, unless facebook institutes a 'fix' within their existing SDK code (not a 'channel') which gets pulled on page load, I, personally, am slightly out of luck and will have to make the best of it. You might fare better.