Marcel Brown

Thanks, Ollie!

FYI, I downgraded to version 7.3.4 and the problem does not exist with this version.

• This reply was modified 2 years, 11 months ago by Marcel Brown.

I agree about the InnoDB converter. That’s all I use the plugin for! Thanks!

I went ahead and deleted the existing scheduled import and re-added it without the embed option enabled. The podcast is set to upload a new episode on Monday. I’ll see if my original issue is resolved. If not, I’ll post it as a new support issue.

I am working with a podcast hosted on Simplecast.

Thanks!

I can confirm the updated version no longer throws the error and it appears editing users works correctly now.

And I can confirm that downgrading to version 1.5.2 does not cause this issue.

Just wanted to post that I am also seeing this problem. PHP 5.5.38

It seems to be generating that error message on all the sites I’m running on this server, but only one (so far) gives me the white screen problem when trying to update a user’s password.

Thanks for the quick response! I actually did try that change before I posted my question. But when I tried pulling up the page I had named “Testimonials” it looked like WordPress simply redirected my request to the home page. So I figured there had to be more to it.

I checked and the hosting for this site was using PHP 5.2. I had to edit the .htaccess file to use a newer PHP version and the problem is resolved. However, I would think that the plugin author would probably want to code a fallback for PHP 5.2 regardless.

Since I use HostGator, the following is all I had to add to my .htaccess file, which was easy to do with the WordPress SEO Plugin by Yoast.

# Use PHP 5.4
AddType application/x-httpd-php54 .php

I blogged about this little project here. I mention FeedPress in it extensively.

https://solotechpros.com/2013/08/02/automate-recycling-wordpress-posts-on-a-yearly-basis/

I wouldn’t mind someone looking over my code and advising me on a better way to do it so I can learn. Thanks!

I figured out a way to do this with a combination of SQL statements and some PHP code. I’ll post the details soon. Thanks!

Update: I also added this mysql command

INSERT INTO wp_postmeta (post_id,meta_key,meta_value) SELECT id,'_pingme','1' FROM wp_posts WHERE MONTH( post_date ) = MONTH( CURDATE( ) ) AND DAYOFMONTH( post_date ) = DAYOFMONTH( CURDATE( ) ) AND post_status = 'publish'

From what I understand, the next time a page is loaded, the rows added by this command which include the _pingme field will trigger a ping. Am I correct?

I know something is set up wrong, that’s what I want to find out how to troubleshoot.

Forget about which feed is being used. None work, not even the WordPress development blog, which is installed by default on the wp-admin dashboard.

The problem occurs even with a brand-new fresh install of WordPress using the built-in RSS widget. That’s why I think it’s an underlying server issue.

What I need to know is where I can look to find errors or any information that I can use to start troubleshooting.

https://www.empowering.com. Lower right section under “Tech Articles”. You’re just going to see the “feed is probably down” error.

What I’m mostly interested in is where to begin troubleshooting. Since I’m not clear where to even begin to look for logs or error codes, I’m not sure how to proceed. I’m not necessarily looking for the answer, but just where to find more information so that I can know how to troubleshoot this.

Thanks!