C. Johnson

@lletuga: The quick hack to resolve the immediate issue would be to go to your FeedWordPress plugin directory, open up admin-ui.php in an editor and change the following line (line 3 of the file in the most recent versions of FWP):

protected $context;

To read as follows:

public $context;

Note that I can only promise that this should resolve the fatal error you are seeing, posted above. The add-on may of course suffer from other compatibility problems that show up only once the fatal error is cleared out of the way.

Hey @alexandroskrassakis

Sorry to hear that you’ve run into this problem with the FeedWordPress Advanced Filters add-on. The developer of that add-on, as you’ve noticed, hasn’t updated it in a long time. If you want to make use of it, there is a pretty quick hack I can suggest that you could make to the FeedWordPress code that would solve the immediate problem and get the add-on working with your hacked version of the most recent release; but of course I can’t guarantee that there aren’t other, deeper compatibility issues (I’ve had a number of users report problems with Advanced Filters over the last year). Depending on what you want to do with Advanced Filters, it’s quite possible that there is another add-on available that will allow you to do the same thing with some more actively updated or at least more forward-compatible code. What is it that you are doing / were doing / want to do with Advanced Filters? Let me know and maybe I can make some recommendations.

O.K., thanks. If you’re seeing this problem when performing updates using cron jobs, it may take a bit more troubleshooting to figure out the exact nature of the problem. The next thing to check would be to see whether or not the guid field associated with these duplicate posts is the same or whether there is a different value for each of the dupes. Here’s how:

1. Log in to your FeedWordPress installation where you’re having the problem.

2. Go to Syndication > Diagnostics in the WordPress admin interface.

3. Find the setting labeled “Advanced Diagnostics.” There should be a series of checkboxes. Check the one labeled “providing meta-data about syndicated posts in the Edit Posts interface.”

4. Mash the blue Save Changes button

5. Next, go to Posts > All Posts and find one of the pairs of duplicate posts.

6. Bring up the first one of the duplicate posts in the Edit Post interface, and scroll down to find the panel labeled “Post GUID and Meta Data”

7. Copy the contents of that panel and paste it in a text box where you can compare it against the second set of data (see below).

8. Repeat the process with the second one of the duplicate posts, copying and pasting the same data from the panel.

9. Send me a copy of the two “Post GUID and Meta Data” listings for the duplicate posts, either here or via email to [email protected]

The most important fields that I’ll be looking at are the GUID field (to see whether the two duplicate posts list the same GUID or different GUIDs) and the syndication_* fields.

Secondly, in addition to checking out this data, could you let me know whether you are using any additional add-ons or filters for syndicated feeds alongside FeedWordPress? (I mean add-on modules like FWP+: SIC ‘Em, FeedWordPress Advanced Filters, or FeedWordPress Duplicate Post Filter.)

Thanks!

O.K., do you have access to your web server or PHP error log? If so you could look there for error messages just after attempting to activate the plugin. Alternatively, if you’re not sure where to look, could you contact me off-list by e-mail at [email protected] ? I can take a quick look and let you know whether there is a simple fix for the problem you’re having or whether you’re likely to need a more extended troubleshooting session.

Hey @terryhoward , thanks for the heads-up on this. Are you still having this problem? If so, could you send me (either here on the forum or via email) the URL of one of the SoundCloud RSS feeds that’s giving you this error? If I have the URL in hand I should be able to do some testing and hopefully troubleshoot the issue that you’re having.

Hi @arno-kools , to do this you will need to use an add-on together with FeedWordPress. There’s one freely available that I wrote a while back called FWP+: SIC ‘Em; take a look here: https://github.com/radgeek/FWP—SIC–Em and let me know if it does what you are looking to accomplish.

If the add-on is too limited to accomplish what you need to do, drop me a line via e-mail at [email protected] and let me know what you’re trying to get done, that the add-on module won’t allow you to do. It’s possible that what you’re trying to accomplish might be solvable in a different way; or with some additional custom code.

@gestaodigital , I’m sorry to hear you had this problem. Take a look at the most recent release of FeedWordPress, 2013.1213, and let me know it still gives you this problem. If so, drop me a line with the error message you’re getting and I’ll take a look. If the upgrade solves this problem, as I suspect it might, great.

Hi @nutricionfan , as you’ve noticed, you need an add-on to work together with FeedWordPress to get Featured Images (that is unfortunate, but at present there is no standardized way for blogs to encode data about featured images in RSS/Atom feeds, so add-ons like FWP+: SIC ‘Em have to engage in some custom behavior and guesswork to figure out what the Featured Image for a post is supposed to be).

I can offer some help with using FeedWordPress together with FWP+: SIC ‘Em, if that’s something you’re still interested in trying. The most sure-fire way to make sure that SicEm gets the images it is supposed to get depends a little bit on your circumstances: it sounds like you are syndicating posts from other websites that you don’t have direct control over? If so, that makes things a bit harder, but if you could let me know some more details about how things did or didn’t work out while using FWP+: SIC ‘Em, I can hopefully help you troubleshoot a bit. (In particular: did you succeed in getting any posts to show up with Featured Images? If so, did some posts show up with Featured Images and others not, or was the problem that the wrong image sometimes was used for a Featured Image? Did you notice whether posts that showed up without the correct Featured Image all came from one or more specific feeds, or did the problem spread out randomly across several feeds? (I.e., if one post from a feed got the correct or incorrect Featured Image, did other posts from the same feed also tend to get the correct or incorrect Featured Images? Or was it more random than that?) Let me know what you’re seeing and hopefully I can help out a bit.

@thiantpro , I’m sorry to hear you’re having this problem. Let me see what I can do to help. The first thing to do in trying to troubleshoot a problem with multiple duplicate posts is to take a look at the update method that you are using. If you go to **Syndication > Feeds & Updates** and you scroll down to the “Update Scheduling” panel, there should be a setting at the top of that panel labeled “Updates,” with a drop-down box beside it which reads either: “cron job or manual updates,” “automatically check for updates after pages load,” or “automatically check for updates before pages load.” Could you tell me which of those three settings you currently have?

@george09 and @ertiti , same question. Let me know what you’ve got there and, depending on the answer, I’ll either have some advice or have a second diagnostic step for you to take to investigate the situation.

• This reply was modified 8 years, 3 months ago by C. Johnson.

I’m sorry to hear you’re having this problem, @yoshuahaxo . When you try to activate the plugin, does WordPress give you the text of the PHP fatal error that occurs? If so, could you copy and paste the error message that you are getting, either in a post on this forum or via e-mail to [email protected] ? If I can take a closer look at what’s going on I might be able to help you troubleshoot the problem.

Thanks for the heads up. This issue should be resolved in the most recent release of FWP, 2016.1213. Grab the latest update and give it a look, see if it eliminates this PHP warning for you.

Thanks for the heads-up and for the error message text, y’all.

I just pushed out a quick patch, as version 2016.1213 of FeedWordPress. It’s available on Github, and it’s also available through the WordPress plugins repository.

The tl;dr is that you should now be able to use FeedWordPress without trouble in versions of WordPress either before 4.7 or after 4.7, so if you were having problems with the 4.7-related warnings described earlier in this thread, or problems with the breakage from pre-4.7 versions of WordPress, as described later in this thread, this release should fix that.

The problem is, basically, that between WP 4.6.1 and WP 4.7, the WordPress dev team decided to reorganize how they store the code modules that implement SimplePie and a number of auxiliary classes related to using SimplePie within the WordPress environment. FeedWordPress depends on SimplePie to fetch and parse feeds. So if FeedWordPress attempts to load in the needed modules using the old pre-WP 4.7 scheme, in 4.7 you’ll get a snippy PHP warning from WordPress about loading deprecated modules. OTOH, if it attempts to load in the needed modules using the new post-4.7 scheme, then in versions of WordPress before 4.7 you’ll get a fatal error, because the needed code is in a different file. In any case: in the interest of balancing both backward- and forward-compatibility, the latest release now runs through the classes that it needs to load, and tests whether or not the 4.7-and-later modules for those classes exist. If so, it loads them up. If not, it falls back on loading the now-deprecated module that versions prior to 4.7 have. In either case, it should more or less smoothly load up the code it needs to load up without pitching a fit in either version.

If you have any questions, let me know. If you are still having compatibility problems with the latest release, let me know — but if the problem you’re seeing is different from the problems described in this thread, please consider opening a separate thread on the forum here or contacting me via email. If after a couple of days of folks checking it out, this release seems to have fixed all of the problems described in the thread here, I’ll go ahead and mark this issue as closed.

Thanks all for the heads-up on these compatibility issues.

@roflkrueger could you drop me a line either here or via email with some details on the breakage that you see with 4.6.1? Are you getting a PHP fatal error, or some other problem? If the former, what’s the text of the error? If the latter, what are you seeing on your end? I’m out of the office right now but should be able to check this out in more detail when I get back to my laptop, so any details you can give me on the situation will be helpful.

Hey all, so, I’m working on a fix for the problem this weekend. I need to do some testing and will then push all needed fixes out with a new official release on the WordPress plugins repository.

It looks like the issue is that WP 4.7 introduced a new call to the http_api_curl hook, which FeedWordPress attaches itself to in order to implemenet some advanced options for HTTP authentication when retrieving feeds. That’d be fine but the handling of referencing parameters is incosnistent between the two calls to that hook, so in one case the relevant method in one of FeedWordPress’s classses is being called without the parameter being referenced as it expected it to be. So I made a small tweak very similar to @garymarkfuller and confirmed that it seemed to solve the issue on at least one site that was having this issue in the wild. While I was there I also removed a deprecated-file warning that also came along with the WP 4.7 upgrade. If you feel comfortable grabbing a development version from Github and testing it out, the fixes appear on the master branch at https://github.com/radgeek/feedwordpress/

If you install the development version and successfully install it, let me know if it solves the problem for you. The fix makes a minor change that affects a function that FWP uses to set HTTP authentication options; so if you use HTTP Authentication (especially if you use HTTP Digest Authentication) to retrieve any of those feeds, you should make sure to double-check those feeds and confirm that FWP can still successfully fetch them without any negative side-effects. If you happen to have a set-up that allows you easily to test this with feeds you retrieve using HTTP Authentication, please feel free to get in touch with me here or via e-mail at <[email protected]> to let me know what you’re seeing; it’d be very helpful in allowing me to confirm that the fix works as expected.

HOWEVER, if as @cogdog suggests there are negative side-effects for other related add-ons like SIC ‘Em or Add Attribution, you may want to be cautious about proceeding with the test if you use either of those problems. I’ll be testing the other add-ons this weekend also and hopefully we can get these issues ironed out soon.

@cogdog , could you send me the text of the fatal errors you’re seeing from the other plugins, either here or via e-mail? I’ll be able to take a look at these later this afternoon.

• This reply was modified 8 years, 3 months ago by C. Johnson.

Hey there,

Thanks for writing, I’m sorry to hear you have this problem.

I have some thoughts on probable causes and feasible solutions but I want to do a bit of testing on my development servers before I suggest anything very confidently. Would it be possible for you to provide me with the URL(s) for one or more of the feed(s) where you encountered this problem?

Thanks,
-C