davouch

Thanks a lot for all your clarification efforts, @jeremy. It sounds like there is no way for you guys to handle this the way we would want it to work and that this is all Facebook’s fault ??

So far, I consider this case to be closed.

Hi Jeremy,
first of all thank you for your kind reply and patient approach.

If I understand correctly, the naming bottleneck is the facebook application or what the facebook API allows or rather does not allow. Now, in theory, would there be any way to hook this around? Let’s say, the Jetpack in defaut mode would work through the general “WordPress” Facebook app, while if anyone would want to there would be an open guide how to set up an individual connection application. The Jetpack plugin would just have to allow this (e.g. via dashboard?) and some setup-guide for FB app would have to be written down.

Or am I missing something?

+1 here. I totally second to what Dan had said here. I host my WP blog on my own hosting, and don’t want to confuse my readers with wp.com link which most of them probably never heard of… (I know it might sound unlikely, but that’s my world ?? )

It’s been 4 months now, do you have any news on this, Jeremy? Or anyone else?
Thanks.

Edit: The text changed to WordPress w/out the .com, but it still links to wordpressdotcom profile @facebook. IMO it’s still too confusing and/or agressive ad.
I assume, there are no plans to do any further step to let us avoid this completely, right?

It’s a trunk version issue:
https://core.trac.www.ads-software.com/ticket/23262

Bingo!
After reverting back to the official release WP 3.5.1, the front page add media link works properly. (the WP 3.5 works too)

Thanks for your help.

Updated to
3.6-alpha-23386
with no change. Error remains, ‘add media’ link doesn’t respond.

One more error kicks in after a while:
JQMIGRATE: jQuery.browser is deprecated jquery-migrate.js:29

Thanks, @invot, for landing here. I’m not sure, if you’ve noticed that in my initial post, but I’m running this thing on a localhost (for more specs see above).

To your suggestion, I’ve tried that already, even before posting the whole thing here. However, when I’ve tried that with their minified version, the console snapped back, it’s unable to get the 1.4.1 version, which seemed weired, so I reverted back to original file shipped with wp.

Now trying it again with the non-minified, the error changed to this:

Uncaught TypeError: Cannot call method 'on' of undefined media-views.min.js:1
f.controller.State.Backbone.Model.extend._updateMenu media-views.min.js:1
w backbone.min.js:8
g.Events.trigger backbone.min.js:10
f.extend.set backbone.min.js:13
g.Model backbone.min.js:12
f.controller.State.Backbone.Model.extend.constructor media-views.min.js:1
d backbone.min.js:41
f.view.MediaFrame.Post.f.view.MediaFrame.Select.extend.createStates media-views.min.js:1
f.view.MediaFrame.Select.f.view.MediaFrame.extend.initialize media-views.min.js:1
f.view.MediaFrame.Post.f.view.MediaFrame.Select.extend.initialize media-views.min.js:1
g.View backbone.min.js:36
f.View.Backbone.View.extend.constructor media-views.min.js:1
d backbone.min.js:41
d backbone.min.js:41
d backbone.min.js:41
d backbone.min.js:41
wp.media media-models.min.js:1
wp.media.editor.add media-editor.min.js:1
wp.media.editor.open media-editor.min.js:1
(anonymous function) media-editor.min.js:1
jQuery.event.dispatch jquery.js:3045
elemData.handle

Also there’s been this line in java console since the very beginning:
JQMIGRATE: jQuery.fn.live() is deprecated jquery-migrate.js:29

Plus one here with:
User ID and Access Token found!
Application Access Token not found. Try re-saving this page.

My setup:
WP 3.3.1 + SFC 1.3
OpenSSL 0.9.8g 19 Oct 2007

deprecate offline_access = disabled

Any clues what might be going on here?

Otherwise it is hard not to be just grateful for this plugin, it is an awesome piece of work, Otto!

Glad it helped, even it was too late. I was very close to reinstalling Firefox too. ??

Hi spleteh,
you could get what you want with get_post_meta or get_post_custom_values
.