The URL that appears in the status bar at the bottom left in FireFox when you hover on the add media button also shows as embedded to the add media button when you examine the code in FireBug.
How can that embedded action-URL be irrelevant? In other words, instead of being linked to trigger the media uploader popup, the button is linked to trigger the creation of a new page. However, clicking it does not refresh the page to a new/blank page editor, it just does nothing.
The site is a fully operational site for an international company (albeit currently undergoing massive editing and new-content creation). If I was to disable it or drop it to a default theme, the Managing Director would have my head on a platter. Currently I have 3 content writers on-site twiddling thumbs waiting for this to be fixed, and they've been doing that since last Thursday when JetPack was upgraded.
At present I'm thinking of killing JetPack and reinstalling the previous version until this gets sorted out, or even of ditching Jetpack completely and rolling back to WP-Stats + WordBooker + WP-to-Twitter (the three plugins I wanted JetPack to replace).
However, the site's url is in a post above if you want to inspect it and advise me exactly what is wrong, or check on the JetPack servers for anything that's gone screwy in the account.
I'm sorry to say that the old fairy tale about the emperor's new clothes keeps coming to mind - in the dozens of fault-report threads since 2.1.1 was released, the JetPack support team have blamed everything but JetPack and now seem to be successful in persuading many users that everything but JetPack is at fault, even though everything worked fine <u>before</u> this JetPack upgrade. Can no-one else see that it is JetPack that has broken so many other plugins and themes, and not the other way around? ... Hey look - JetPack has no clothes on. ;)