C. Johnson

Hey all, the issue seems to be due to an updated version of the SimplePie module which is included in WordPress. (The story is, WordPress upgraded the included version of SimplePie to version 1.8.0, which was released last year; the new version introduces some changes to the type declarations in the code which take advantage of object-oriented features in more recent releases of PHP; these changes are no doubt a good idea in the long run, but they unfortunately break backward compatibility with code that extends some of the SimplePie classes to customize its functionality, as WordPress and FeedWordPress both do.)

Anyway, the good news is, there is a relatively quick fix to the immediate issue; I have put out a point release this morning (2024.1119) that includes a patch to fix this error. The recommended course of action is to upgrade FWP to this version. Give it a download, take a look, and let me know if it rids you of your troubles, or if there’s anything that comes up or anything you need to check in on.

Thank you for the heads-up about this issue, and I am sorry for the problem. You can update now, either from Github or from the Plugin Repository as you prefer; the bug fix releases (2022.0208) should hopefully resolve the problem. Let me know if it works for you.

Thank you for the heads-up, and I am sorry for this issue. You should be able to resolve it by upgrading to the most recent version of FWP, released today (2022.0123). Please let me know if this works for you, or if you run into any issues with the upgrade.

Hi @ofredon , I’m sorry it’s taken me a while to get back to you. Are you still having this issue, or has it resolved itself?

I don’t know for sure, but from the XML error message that you provide here (“No memory at line 21531, column 1”), it sounds like you might be running up against memory constraints from PHP, or your web server, when FeedWordPress tries to parse the feed. If this is the case, then the likely solutions will probably have to do with changing system configuration settings within your web hosting environment (which will depend a lot on how you get your hosting), evaluating other possible hosting solutions, or alternatively, working around the problem by finding a way to access the same XML content in smaller parts.

Does this error message occur consistently (i.e., the same way, all the time) when you are trying to update posts from one feed in particular? If so, is the www.website.com URL that you pasted above the exact URL of the feed that always produces this problem for you?

Hi @rahimhussainali , taking a look at the error messages you are seeing, it appears likely to me that the issue you’re encountering is not produced by the code in FeedWordPress, or related to FeedWordPress’s functionality. The error messages indicate that the problem is occurring in files in the WordPress Core code:

[...] /home2/eisport/public_html/eis/wp-includes/formatting.php on line 4358

For what it’s worth, FeedWordPress eliminated all references to the legacy get_magic_quotes_gpc() function (which dates back to PHP 3.x) last year, in version 2020.0818.

It’s possible that you’re running into this issue because of the version of WordPress you are running; are you able to update to the most recent release of WordPress? If so, I’d encourage doing so and seeing if it resolves your issue.

In any case, since this issue seems highly probable to be unrelated to the FeedWordPress plugin, I’m marking it as “Resolved” for the time being. If you have more information that strongly indicates that this problem is FWP (for example, it persists after you upgrade WordPress versions to the most recent release, it appears consistently when the FeedWordPress plugin is activated and disappears consistently when FeedWordPress is deactivated, or something along those lines), please don’t hesitate to let me know, and I’d be glad to open up this thread again.

Hi @juelybean , a couple of notes on your issue:

(1) On the one hand, if you download and install the update to the most recent version of FeedWordPress (v. 2021.0713, released yesterday on the 13th), I can say that this update resolves some outstanding issues with notices resulting from the use of the count() function. So it might be useful for your purposes, if nothing else for the sake of eliminating possible causes. HOWEVER, see below.

(2) ON THE OTHER HAND, from the contents of the PHP Warning that you quote above, it appears that the problem here is related to code within your WordPress Theme, (cindy-j), rather than being related to the FeedWordPress plugin. The line that you quote above is not from the FWP code and does not seem to be closely related to FeedWordPress functionality.

As a general matter, if you are able to, and feel comfortable with, editing the code in your theme in order to address this issue, it might be relatively easy to address the immediate issue that is causing the warning.

Usually warnings like these result from code that was written under earlier versions of PHP (in which coders were able to use the count() function not only on arrays and array-like structures, but also to detect NULL values, single-item scalar values, etc.) but are now being run under newer versions of PHP (in which count() is more narrowly limited to arrays and array-like lists, and where the older conventions have been eliminated in favor of other conventions like using is_null() and similar type-detection functions). Certainly, this is what caused issues in the case of code that I wrote for FeedWordPress (which was originally written a very long time ago, and has gone through several versions of PHP).

Depending on the code that is above or below the if structure that you quote — in particular, depending on where the $custom_sidebars_number variable comes from and how it is used when it has a valid value — this issue should be fixable by putting one or two simple test functions in front of the call to count($custom_sidebars_number). You might be able to do this by hand, or, if the theme was developed by a third-party developer, you might be able to get the developer to do it for you. If you want, please feel free to drop me an e-mail at <[email protected]> with some more details about the theme you’re using and with, say, the 5 lines before line 352 and the 5 lines after it, and we can probably work it out from there. Just let me know!

Since this issue seems very probable to be unrelated to FeedWordPress, I am for the time being marking the issue as “Resolved,” but if you have more information that indicates it is in fact directly related to the plugin, please let me know and I’d be happy to open it back up again here.

Thanks for the catch on this. I will make a fix for this line. I’d be interested to know if you have the URL for a feed that gives you this warning? (If not, no worries — I realize it’s been a while. But if you do have the URL, then that would be useful because it gives me a test case for a condition that I’d like to remember to test for.)

Thanks! I will reply again and close this thread out once the change is applied.

Sorry if I’m covering stuff you already know, but just to make sure:

The default behavior is not to delete posts when they fall off the feed, but to retain them. Under Syndication –> Feeds & Uploads –> Advanced Settings –> Feed Update Type, there is a setting to control whether FeedWordPress treats the feed as *Incremental* (i.e., retains posts whether or not they still appear on the RSS feed), or as *Complete* (i.e., retires posts once they no longer appear on the RSS feed).

Do you currently (a) have this set to Incremental? If so, then the solution should be to switch it to Complete and Save changes.

Or do you currently (b) have it set to Complete, but are finding that the setting no longer works as expected? If so, let me know, and I’ll take a look to see if I can figure out what’s going wrong.

Thanks for posting your question. I want to make sure I understand the question correctly, so let me see if I understand what you are asking.

It sounds like you are syndicating posts from a news source, and it sounds like you want to constrain the word count of the *titles* of those posts, so that if a title goes over a certain length, it will be trimmed to match the desired word count. Is that an accurate summary of what you want to do? If so, let me know — I can try to give some advice on how to do this. It will take a little bit of programming, but it is not very hard.

If that is not what you want to do, then I apologize for misunderstanding your question. Could you tell me a bit more about what you are trying to change about syndicated posts, and how you are trying to change it?

Thanks!
-C

Thanks! I merged in @oppiansteve’s pull request and it is incorporated into the most recent release (2020.0818) of FeedWordPress. Should now be resolved?

Thanks for the report. I believe that this issue should be fixed by one of the changes introduced in the most recent version of FeedWordPress (release 2020.0818). Let me know if you are still seeing any of these notices or if the upgrade resolves the issue for you.

Thanks for flagging this issue! It should be resolved by installing the most recent release of FeedWordPress (2020.0818). Hope this helps! Let me know how it works for you.

Hi all, sorry about this problem. The good news is, the issue should be resolved by installing the most recent release of FeedWordPress (2020.0818). Hope this helps! Let me know how it works for you.

Sorry about that! Should be back up now.

Hi all, sorry you ran into this problem.

The cause was that the most recent release of WordPress 5.5 includes an upgrade to the SimplePie feed parsing library (from 1.3.1 to 1.5.5). On the whole this is a good thing, but here it had the unfortunate side effect of introducing small but important changes in a couple of classes that FeedWordPress adapts and extends. Hence the ugly warning notices.

The good news is, that this issue should be resolved by installing the most recent release of FeedWordPress (2020.0818). Hope this helps! Let me know how it works for you.