philbee

Mh. Just re-checked wordpress.com/sites/, and apparently centralized site management seems to be turned on for my site, despite my being utterly unable to find any hint of this in my site’s dashboard.

So far, I must say this is not quite what I had hoped for. I can’t find a single plugin that shows any entry for auto-updating in the plugins list. I guess there must be an equally hidden magic button somewhere, somehow.

Clicking on the “update plugin” on wordpress.com/sites/ button switches me over to my sites dashboard. That’s a far cry from what my.bruteprotect used to offer – which was much more close to being able to stand in for managewp.com’s centralized update management, if I remember correctly.

Interestingly, linking the image to something other than the post itself works when one sets “Image Link: Link Image to Post” and then enters the URL in the Link ( Defaults to Permalink ): field below.
The same does not work, however, for the Link Title to Post – there the link is always set to the post, not to any URL entered in the title links “Link (Defaults to Permalink):” field.

I just noticed this rather unexpected behaviour as well: translated pages appear twice in WordPress backend. This is rather confusing and would quickly get very unpleasant with many pages and languages.

Is that by design?

Sounds intriguing.
Do you have a roadmap as to when this next release could happen?

Thanks.

Hi Richard

sorry – I completely forgot about correctly marking it “resolved”.
Done.

Thanks, Phil

Thanks a lot Richard for taking time to answer here!
Interestingly, when I tested just a few minutes ago (same server, same everything), it worked beautifully, both on Facebook and on G+.
My guess is that when I get around to have Twitter say OK* to my site, I’ll also have pretty Twitter cards, thanks to the awesomeness of Jetpack. You guys must make life for some plugin developpers really miserable, you know that? ??

* Interestingly, using one of the specialized Twitter cards WP plugins, I was able to get a Card-enabled Tweet from my non-twitter-authorized testing site, so there must be a way around this requirement.

Thanks a lot wizzud for your detailed explanation – much appreciated indeed!
I’m currently building a client site using CMW – do you think v.3 might be ready for production (within about 2 weeks)?