zamba

More information:

After extensive testing with the guys at Buffer and on my own, I found out that if you are buffering to several destinations, e.g. Facebook, Twitter, LinkedIn and Google+, a failure of one of those destinations will cause all to fail.

In my case, this was the Twitter account. The reason for this is that I was using the url,title,excerpt setting for my updates/posting. Although previously this caused no problems, it now does. Using only url, title, allows me to post to Twitter. So If I post/update in two stages, this causes no issues.

Not a very satisfactory conclusion, but a solution of sorts.

Best wishes,

Tony

More information: It appears that the plugin WP to Buffer works with the Travelsignposts sub-blog Germany when the latter posts direct to Buffer, but does not work when the post update is from the main Travelsignposts multisite blog. This is also true of the separate Travelsignposts China multisite blog, even though in that case only the main blog currently exists.

For the past few years there has been no problem with posting/updating from the main multisite blogs, only recently.

I have now deleted the main Travelsignposts app on Buffer and created a new one, Travelsignposts Social 3. Unfortunately this also fails to work. I have reloaded a fresh copy of the plugin to make sure there was no corruption there, and of course the German sub-blog uses the same plugin files (although a different app and access code at Buffer).

So it would appear that something has happened that causes the connection between the plugin on the main site blog to fail, but the connection with a sub-blog under the same main blog to continue to work!

I’m not privy to the way the Buffer app interacts with the plugin and main multisite blog, but this sort of smacks of a permission issue to me, how about you? Any ideas?

I’m aware I can revoke access for an app on the Buffer site, but thought that disconnecting it from the plugin, deleting it and creating a new app with a new access code would constitute a fresh start.

Thanks for any suggestions!

Tony

Sorry, Steve, I completely forgot about pastebin, and I didn’t think the log counted as code. Will do better in future!
Still haven’t solved problem at this time.

Nothing is perfect! I would actually like to retain the copyright information in the image, don’t mind losing the rest, but I can’t see how you’d do that…

Thanks,

Tony

Our posts crossed, glad I guessed right!

Cheers,

Tony Page

After reading through the code more carefully (I have limited skills in this area!) I pasted in the code you suggested before the above code:

// Break image data into url, width, and height.
	list( $img_url, $img_width, $img_height ) = $img;

	if ( 0 == $img_width ) {
	return false;
}

	// Get the image meta data.
	$img_meta = wp_get_attachment_metadata( $id );

and all appears to have worked correctly.

Many thanks for your quick response, and many thanks too for your excellent work in this field; with an image heavy site the work you are doing is very important to us, and we’re following it closely!

Thanks for the update, impressively responsive!
The code I have at 156 is

// Get the image meta data.
	$img_meta = wp_get_attachment_metadata( $id );

Should you suggested update go before or after this?

I have to admit that I pasted your code in at 173, replacing this

// Calculate the image aspect ratio.
	$img_ratio = $img_height / $img_width;

and the fix appeared to have worked!

Sorry for the delay in replying, I’m in Sydney, Australia, so there’s a bit of a time difference!

Note: this warning does not appear anywhere else on the site AFAICS, and the page appears as normal apart from the warning itself. None of the sub-blogs in the folders exhibit any similar behaviour (the site is a single domain sub-folder multisite setup).

Line 173 is:

// Calculate the image aspect ratio.
	$img_ratio = $img_height / $img_width;

Just want to get rid of that warning!

Thanks for this update. My 27 blog multisite disappeared on updating to version 1.93. On amending the above code (actually line 358) everything appears back to normal on network activation.

Anyway, an excuse to have a fortifying scotch to settle my nerves first thing in the morning here in Australia…

Cheers,

Tony Page

I’m also experiencing this on a multisite single domain install. Also rolling bacl to 5.2.7.

As have I. Already posted on the Yoast announcement page but no answer there so far.

Well, this is still going on for me. Anyone else solved it?

I’ve had no trouble with this simple plug-in over several years, using it for adsense insertion, but a recent plug-in that works fine otherwise (and apparently causes no problems for others) viz. Pin Button Attraction (excellent Pinterest options, BTW) causes the inserted file to disappear from the body of the post.
As this plugin hasn’t been altered in 6 years, this may presage wider problems in the future, so it’s probably wise to be looking for alternatives, as I am.

I’ve now tested the latest version on WP 3.5 and have no problem in commenting. This was on a test blog with all the plugins of the main blog and on the same server. So at first site this would appear to be connected with the 3.5/2.7.6.1 upgrades.

As I’m not yet ready to upgrade the main site I’ll wait to move to the latest version of SI Captcha until we’re happy 3.5 hasn’t any nasty surprises for us!

Thanks for your help, guys, and if I run into any more issues I’ll come back to the forum.

Hi Mike,
I’m going to test the new versions on a separate mirror set-up (structure only, the live site is too big to mirror content)to check whether upgrading to 3.5 makes any difference with the new SI Captcha version.
@sergei, I do have a temp directory in my current 2.7.4 captcha directory, but it’s 755. I’ll try your solution when testing, although it may compromise security a little.
Merry Christmas to all!