This is probably caused by a PHP error with either your theme or with a plugin, not necessarily related to SSP. When I look at the HTML code for your page that page is truncating at the start of the post content.
Look on your webhost for a file called error_log this will tell you if there’s any PHP errors and where they are occuring. If there are errors please paste them into a Pastebin and share the link back here for us: http://pastebin.com
Also, try disabling all your plugins and running just the SSP plugin with your current theme. IF you still have issues, try setting your theme back to Twenty Twelve or Twenty Thirteen to see if you still have the problem.
I’m guessing it’s a bug arising from your theme or another plugin you have installed.
Hope that helps.
I can’t imagine what you’re saying to be true since the only posts that are effected are the podcast posts, not my regular blog posts, but I did what you suggested.
I shut down all the plugins and it had no effect. Also tried a new theme and that didn’t solve it either. So, I found the error log file, and here’s the link to the Pastebin.
http://pastebin.com/4EccynhJ
Thanks.
Sidenote, my entire podcast is down right now, not publishing to iTunes at all.
Might be a theme issue conflicting with SSP, since the error is pointing to SSP. Have you tried switching to the default 2012 theme to see if it’s an theme conflict?
Did that too, still didn’t have any effect.
Another side note. Libsyn.com seems to be having major issues today, and since all my files are loaded there, maybe the connectivity between the files and the plugin is causing an error? I’m so not tech enough to make that judgement, but it’s the only other outside influence I can think of.
Actually I think Libsyn is the problem. I just did a test post and instead of pointing to a file, I loaded one up directly to my server and it seems to be working.
http://www.freshrag.com/podcast/testing-a-theory/
Libsyn is the likely suspect, but we’ll see as soon as they ramp back up.
Yes that may be the problem. If the files are unavailable from Libsyn then it might cause this problem.
The code referenced in the error_log is using wp_remote_head:
public function get_file_size( $file = false ) {
if( $file ) {
$data = wp_remote_head( $file );
if( isset( $data['headers']['content-length'] ) ) {
$raw = $data['headers']['content-length'];
$formatted = $this->format_bytes( $raw );
$size = array(
'raw' => $raw,
'formatted' => $formatted
);
return $size;
}
}
return false;
}
So wp_remote_head is returning WP_Error and that gets input into the above function and the function calls foul and outputs the following errors:
[16-Oct-2013 16:45:23] PHP Fatal error: Cannot use object of type WP_Error as array in /home1/magaziq1/public_html/freshrag/wp-content/plugins/seriously-simple-podcasting/classes/class-seriously-simple-podcasting.php on line 535
It would be good for the above function to have a is_wp_error check to help better respond to this error.
http://codex.wordpress.org/Function_Reference/is_wp_error
Maybe something basic like: http://pastebin.com/NdAe5Rvh
Ok, well Libsyn is back up and running, but the site is still having problems. Any other thoughts?
So whenever LibSyn goes down it causes SSP to mess up and not fully render your podcast pages.
What you can do is add a check to make sure LibSyn is not down, if it is you can have SSP show an error message and continue to load your page.
Yeah, I just had a developer buddy of mine take a look. He found the code in the plugin that was messing up because of the Libsyn shut down.
Hugh – I figured you might want to see this for future reference, even though this was an extenuating circumstance.
This was the code my friend worked with.
public function get_file_size( $file = false ) {
if( $file ) {
$data = wp_remote_head( $file );
if( isset( $data['headers']['content-length'] ) ) {
$raw = $data['headers']['content-length'];
$formatted = $this->format_bytes( $raw );
$size = array(
'raw' => $raw,
'formatted' => $formatted
);
return $size;
}
}
return false;
}
He said the “if( isset” line was looking the raw file and when it couldn’t find it repeatedly, it gave up.
I’m sure you probably know this already, but I figured I’d share just in case.
Thanks for your help BmGhDZ9k
