Add Attribution for FeedWordPress

Project Tip Jar

Your generous gifts make ongoing support and development for Add Attribution for FeedWordPress possible.

$0.00 donated in the past 12 months.

  • Author: Charles Johnson
  • License: GPL
  • Compatibility: WordPress 3.0 or better, with FeedWordPress 2009.0713 or later.
  • Status: Supported and mature. Bug fixes released as necessary.

Download

Add Attribution is an add-on module for the FeedWordPress aggregator, which provides a convenient interface for adding attribution information to syndicated posts without editing your WordPress theme. Boilerplate text can be appended to post titles, post content, or post excerpts, using convenient shortcodes to provide information about the source of each particular post. You can use the interface to set up default rules for all syndicated posts, or to set up rules for individual feeds.

Advertisement

Released: FeedWordPress 2012.1218. WordPress 3.5 compatibility, PHP 5.4 compatibility, bug fixes, diagnostics improvements, and a great deal more.

It’s been a long time, much too long, since my last official release announcement. But I’m happy to announce that today I have released FeedWordPress v. 2012.1218, now available for download from the WordPress Plugins Repository or from Github.

This announcement is actually doing double duty as an announcement for two releases. The first release, FeedWordPress version 2012.1212, which came out last Wednesday, was an important compatibility release to ensure compatibility with WordPress 3.5 and PHP 5.4; as well as a roll-up of the many changes and improvements in FeedWordPress, which have been documented here, but which never got into the WordPress plugins repository since the previous official public release in 2011. Today’s release, FeedWordPress 2012.1218, is an incremental update improving on 2012.1212 by rolling in some bug fixes in response to issues reported by users after the 2012.1212 upgrade.

There are many more changes in the big release than I’ll try to document here, but we can hit up some of the highlights:

FeedWordPress 2012.1212 changes

  • WORDPRESS 3.5 COMPATIBILITY: This release has been tested for compatibility with new releases of WordPress, up to version 3.5, and any documented compatibility issues have been cleared — in particular, if you were seeing error pages stating that you don’t have permission to access the FeedWordPress Syndication page within the WordPress admin interface, then upgrading to this release should fix the problem.

    As always, if you encounter any compatibility problems after upgrading your version of WordPress and your version of FeedWordPress to the most recent versions, please contact me with as detailed a description as possible of the issue you are encountering, the circumstances you’re encountering it under, what you expect to see happening, and what is happening instead.

  • PHP 5.4 COMPATIBILITY: This release has been audited to fix potential problems with deprecation notices or fatal errors under recent versions of PHP. In particular, all uses of run-time pass-by-reference have been eliminated from the code; if you were seeing a fatal error reading “Call-time pass-by-reference has been removed …” then upgrading to this release should fix the problem.

  • CUSTOMIZATION FRAMEWORK: A great deal of work has been done to make the underlying framework more flexible, so that PHP add-ons can be written to adapt FeedWordPress to handle custom XML vocabularies, expiration of posts under specified conditions, and other custom behavior.

  • BUGFIX: MANUALLY EDITED POST SLUGS NOT OVERWRITTEN. Thanks to a report by Chris Fritz, I’ve identified some code that causes post slugs for the posts generated by FWP to be rewritten with every update, even if the user has manually updated the slug from within the WordPress editing interface. This has been fixed: FWP will continue to generate new slugs for syndicated posts, but when syndicated posts are updated, they will retain the slug that they had at the time of the update; any manual changes to the post slug should be preserved.

  • USER-AGENT STRING: FeedWordPress now sends a distinctive User-Agent string identifying itself, and noting that it is a feed aggregator.

  • MISCELLANEOUS PERFORMANCE IMPROVEMENTS: A number of changes have been made to try to reduce the intensity and expense in terms of both database performance and web server memory consumption.

  • DIAGNOSTICS IMPROVEMENTS: A number of new and improved diagnostics have been added which should aid in understanding and troubleshooting issues that may arise.

Here are the specific incremental changes and bugfixes made in today’s release, 2012.1218.

FeedWordPress 2012.1218 changes

  • WORDPRESS VISUAL EDITOR FIXED. There was an unlisted change in the 2012.1212 release which had the effect of disabling the WordPress Visual Editor for all posts syndicated by FeedWordPress. Many users reported this as a bug. It was actually a deliberate decision — a crappy way to try to deal with a crappy situation. (Many users had previously reported a “bug” in which all the paragraph or line breaks seemed to be stripped out of their syndicated posts; the issue turned out to be that the Visual Editor was stripping out

    and <br/> tags on the assumption that the resulting post would be sent through standard WordPress formatting filters. But under default settings, posts syndicated by FWP deliberately bypass WordPress formatting filters.) In any case, this version adopts a more flexible compromise. If FeedWordPress is set up to bypass WordPress formatting filters (as it is by default), then the Visual Editor will be disabled for syndicated posts (since using it would produce incorrect results). If on the other hand FeedWordPress is set up to expose syndicated posts to WordPress formatting filters (as it usually is for those using the Visual Editor to manually edit posts), then the Visual Editor tab will be re-enabled for syndicated posts.

  • BUG FIX: PERMALINKS REWRITTEN FOR CUSTOM POST TYPES AS WELL AS NORMAL WORDPRESS POSTS. If you had WordPress set up to syndicate incoming posts to a custom post type (under Syndication > Posts & Links), and asked FeedWordPress to make “permalinks point to the original site”, then previous versions of FeedWordPress would fail to do the rewriting — permalinks would only be rewritten to point to the original source for normal WordPress posts, not for custom post types. In 2012.1218 this bug has been fixed: all post types will now have permalinks rewritten unless you request for permalinks to point to the local copy on your aggregator site.

  • BUG FIX: ELIMINATES “PHP Fatal error: Call to a member function setting() on a non-object….” Some changes to the in-memory caching of information about feed subscriptions in 2012.1212 could result in a fatal PHP error in cases where you have de-activated one of your subscriptions, but posts from that subscription were still in the archive. This would normally show up through half-completed feeds or half-completed pages that suddenly broke off in the middle, and displayed or logged an error message like: “PHP Fatal error: Call to a member function setting() on a non-object in {…}/wp-content/plugins/feedwordpress/feedwordpress.php on line 615″. This bug has been eliminated, so affected feeds and pages should now render correctly, and the error message should no longer appear.

  • BUG FIX: CATEGORY BOXES IN SYNDICATION > CATEGORIES & TAGS. Some minor bugs in the appearance and animation of category checkboxes (for example, the checkbox used to select categories for syndicated posts on the Syndication > Categories & Tags settings page) have been fixed.

As always…

If you notice any problems, have any questions, need any help, or just want to say “Hi,” don’t hesitate to drop me a line via e-mail or through the comment form. If you have a specific problem that you need help with, please try to describe the circumstances and the problem you are seeing in as much detail as possible — what you expected to happen, what you see happening instead, what you are doing (if anything) when the error comes up. If the problem has to do with one or more particular feeds, it helps a lot to include the URL(s) of the feed or feeds that you’re seeing the problem with. If the problem has to do with an error message appearing that you do not understand, a screenshot of the error message would help a lot.

Now get on out there and check out the new release! Download and enjoy!

At GitHub, radgeek pushed to master at radgeek/FWP—Add-Attribution

Recent code updates from Rad Geek at github.com:

Check out the details at GitHub.com ...

FeedWordPress 2011.1019. HTTP Authentication support improved, bug causing HTTP transport error for some users squashed

Today I put out an incremental release, FeedWordPress v. 2011.1019, which is now available for download.

This release was intended mainly to provide a quick fix for a problem that some users encountered after installing yesterday’s release, 2011.1018. Users whose web hosting environments have the curl module for PHP installed got an important new feature — the ability to set usernames and passwords on feeds to use with HTTP Basic or HTTP Digest authentication. Users who didn’t have the curl module unfortunately got a bug, which caused error messages like “WP HTTP Error: There are no HTTP transports available which can complete the requested request.” to pop up. If you’ve been seeing an error message like that, this release should hopefully fix your problem.

While I had my hands in the code, I went ahead and did some general work to improve the interface and better generalize the HTTP authentication feature for users who do not have the curl module installed. (Most web hosts install it, but not all.) You should hopefully now find the process of adding an authenticated feed much more natural: just put the URL into the Subscribe box and tell FeedWordPress to check it out; when FWP detects that the feed requests login credentials, it will come back and suggest that you enter a username and password before subscribing. When you enter the credentials and re-check the feed, FeedWordPress will allow you to subscribe and immediately set up those credentials for future feed updates. I hope it should all be fairly straightforward, but if you have any questions, don’t hesitate to ask.

Here’s the official changelog for this release:

  • BUGFIX: “THERE ARE NO HTTP TRANSPORTS AVAILABLE” ERROR FIXED: The initial
    support for HTTP Basic and Digest authentication in version 2011.1018
    contained a bug that could cause HTTP requests for feeds or for other
    WordPress resources to break down if you do not have the PHP curl module
    installed. This bug has been fixed, and these errors should no longer
    appear.

  • IMPROVED HTTP AUTHENTICATION SUPPORT: In addition, the HTTP Authentication
    support in FeedWordPress has been extended, to ensure that Basic
    authentication is available in many web host configurations, and to allow
    you to add a username and password for a feed immediately when you
    subscribe to it.

As always, if you notice any problems, have any questions, need any help, or just want to say “Hi,” don’t hesitate to drop me a line via e-mail or through the comment form.

Please remember that your ongoing gifts to the project tip jar, besides being immensely kind, and very much appreciated, are also what make it possible for me to take out the time for ongoing development, timely fixes, and support for the FeedWordPress project.

Now get on out there and check out the new release.

Add Attribution 2010.0207 includes a compatibility fix for more peaceful coexistence with other FeedWordPress add-on modules

Version 2010.0207 of Add Attribution for FeedWordPress is now available for download.

This is a small compatibility release. It does not add any new features over those offered by version 2009.0730. (Like I said, Supported and mature.) But it does include a small but important change to the order of execution that Add Attribution requests, which will help it play nicer with other filters designed to work with FeedWordPress. (In particular, this update is necessary in order to avoid potential conflicts with the newly-released FWP+: Limit size of posts add-on module. If you want to use both Add Attribution and Limit Size Of Posts together, you’ll need this update in order to ensure harmonious coexistence.)

Download and enjoy! As always, you have any issues with the release, or if there is anything that you would like to see included in a future release, please use the comments form or drop me a line to let me know about it.

Add Attribution 2009.0730 fixes a couple bugs, and adds an [original-url] shortcode

Version 2009.0730 of Add Attribution for FeedWordPress is now available for download.

This release adds one significant new feature — the [original-url] shortcode — and also fixes a small group (swarm? nest? hive?) of bugs originally reported by Ato which have to do irregularities in the way that WordPress parses dashes in shortcode names. Changes:

  • Feature: If you want your attribution boilerplate to contain a link back to the original post that this post is a syndicated copy of, you can now do so using the [original-url] shortcode.

  • Bugfix: Due to problems in the way that WordPress parses shortcodes with dashes in their names, the [source-name] and [source-url] shortcodes in previous versions might erroneously display the same link that was supposed to be displayed by [source], and [author-name] might erroneously display the same link that was supposed to be displayed by [author]. This problem has now been fixed, and each shortcode should display its proper contents.

  • Documentation: Shortcodes are now more thoroughly documented; the helper box in the Attribution Boilerplate section now contains a full list and short description of all available shortcodes.

  • Interface and bugfixes: Some miscellaneous AJAX changes, styling improvements, and minor bug fixes.

Download and enjoy! As always, you have any issues with the release, or if there is anything that you would like to see included in a future release, please use the comments form or drop me a line to let me know about it.