DowntownRob

Andy, change the line in the public static function approved($user_id) function to this:

$opts[‘approval-email’][‘body’] = str_replace(array(‘%%firstname%%’, ‘%%lastname%%’, ‘%%fullname%%’), array($user->first_name, $user->last_name, $user->first_name.’ ‘.$user->last_name), $opts[‘approval-email’][‘body’]);

It was clearly a copy/paste from the new_user function, using the wrong email options.

Oh actually, that’s wrong too, it should be the line in the public static function approved($user_id) function, changed to this:

$opts[‘approval-email’][‘body’] = str_replace(array(‘%%firstname%%’, ‘%%lastname%%’, ‘%%fullname%%’), array($user->first_name, $user->last_name, $user->first_name.’ ‘.$user->last_name), $opts[‘approval-email’][‘body’]);

It was clearly a copy/paste from the new_user function.

Sorry, just saw your reply. It looks ok to me now, it was probably a cache issue.

I viewed your feed, it looks like the text is next to the image as desired. Perhaps it took a while, or there were multiple caches (server cache, CDN cache, browser cache, etc).

Use the contact form in the options page to send me a link to the Blogger page? If Blogger is pulling the feed in via RSS, it should include the images, otherwise it’s purposely removing or ignoring the IMG SRC HTML code that is included.

Ah that’s a great idea… I’ll look into adding it.

Yes, I deactivated the Shortcodes module, and it still happened.

Sure, I’d love to nail down the cause and help fix it.

I’ve deleted the folder, then reinstalled Jetpack, and connected it to WordPress.com.

The post with the post format of audio with an MP3 works fine still:
https://nickmarlbroughauthor.com/i-dare/

The page with an MP3 file embedded now no longer works:
https://nickmarlbroughauthor.com/audio-test/

Here’s the error log output

root@vps1 logs]# tail /hsphere/local/home/wwwuse0/logs/nickmarlbroughauthor.com/error_log
[Mon Jan 13 12:37:12 2014] [error] [client 192.80.3.219] (104)Connection reset by peer: FastCGI: comm with server “/hsphere/shared/php53/bin/php” aborted: read failed, referer: https://nickmarlbroughauthor.com/wp-admin/edit.php?post_type=page
[Mon Jan 13 12:37:12 2014] [error] [client 192.80.3.219] FastCGI: incomplete headers (0 bytes) received from server “/hsphere/shared/php53/bin/php”, referer: https://nickmarlbroughauthor.com/wp-admin/edit.php?post_type=page

If visited using an incognito window:

[Mon Jan 13 12:40:26 2014] [error] [client 192.80.3.219] (104)Connection reset by peer: FastCGI: comm with server “/hsphere/shared/php53/bin/php” aborted: read failed
[Mon Jan 13 12:40:26 2014] [error] [client 192.80.3.219] FastCGI: incomplete headers (0 bytes) received from server “/hsphere/shared/php53/bin/php”

That’s all I see.

If I deactivate Jetpack’s shortcodes completely, it still happens. If I deactivate the plugin, it works again.

Ah, if I switch to FastCGI on PHP 5.2, it works ok. If using FastCGI on PHP v5.3, it errors out. It’s only a problem on v5.3.

Yeah this was a fresh installation. I’ve deleted the folder too, and reinstalled, still happens. I’ve deactivated it now.

FYI, my son’s very basic site had an MP3 audio file from the media library on a page in WordPress v3.8 using the TwentyThirteen theme, using the [audio] shortcode, with no Jetpack installed, and it was working fine. I installed and activated Jetpack today to add it’s stats, and instantly, that audio page serves up a 500 Int Server Error. The other pages work fine. I deactivated the Short Code module in Jetpack, still errors. I deactivate Jetpack, error goes away.

So, it’s still occuring, and it’s a minimal install.

Hi Juan,

Hmm, is there a featured image set for each post? The plugin simply grabs the featured image if it’s set per post, and outputs HTML to include it, with some CSS to position it before the normal RSS content.

If one is not set (some themes use custom fields, some posts have the image in the content/body – those do not work as Featured Images) then it outputs nothing before the content.

I have the same problem… is it as simple as installing a ReCaptcha plugin? Does the form need any integration or does it just work?

Perhaps the author can enable a captcha option of some sort, or tap into using Akismet filtering?

Hi there,

Hmm, the CSS in the feed code includes a 5 pixel margin as spacing, perhaps the CSS isn’t being used or displayed properly? It might depend on the RSS reader perhaps.

Would offering a padding option help, or make no difference?

To test, simply edit the plugin code below, and increase the 5px to 10px or 20px:

function firss_eval_css($featured_images_in_rss_css) {
switch ($featured_images_in_rss_css) {
case “left-above”:
$featured_images_in_rss_css_code = ‘display: block; margin-bottom: 5px;’;
break;
case “centered-above”:
$featured_images_in_rss_css_code = ‘display: block; margin: auto; margin-bottom: 5px;’;
break;
case “left-wrap”:
$featured_images_in_rss_css_code = ‘float: left; margin-right: 5px;’;
break;
case “right-wrap”:
$featured_images_in_rss_css_code = ‘float: right; margin-left: 5px;’;
break;
default:
$featured_images_in_rss_css_code = ‘display: block; margin-bottom: 5px;’;
break;
}
return $featured_images_in_rss_css_code;
}

Hi Oliver,

It seems the plugin is still working, I see the images in the Description, but the Thumbnail size is set to width and height of 1 pixel? Fix the size issue, and they should display.

<img width=”1″ height=”1″ src=”https://www.starsandcatz.com.au/wp-content/uploads/classical-music-recital-1385520984-1739143066.jpeg&#8221; class=”attachment-thumbnail wp-post-image” alt=”classical-music-recital-1385520984-1739143066.jpeg” style=”display: block; margin-bottom: 5px;” />  Today’s News & Buzz   Alice Herz-Sommer at 110 – https://www.therestisnoise.com

Thanks for the thanks… unfortunately that’s a rather unique use case, and the plugin is doing very basic output of the featured image right before the normal RSS output generated by WordPress. You could customize the plugin code, to add <featuredimage> before the featured image output, and </featuredimage> after but before the RSS content… but it’s still within the content:encoded blocks, so parse it differently perhaps?