text:
FeedWordPress is an Atom/RSS aggregator for WordPress. It syndicates content from feeds that you choose into your WordPress weblog; the content it syn
FeedWordPress is an Atom/RSS aggregator for WordPress. It syndicates content from feeds that you choose into your WordPress weblog; the content it syndicates appears as a series of special posts in your WordPress posts database. If you syndicate several feeds then you can use WordPress's posts database and templating engine as the back-end of an aggregation ("planet") website. It was developed, originally, because I needed a more flexible replacement for Planet to use at Feminist Blogs, an aggregator site that I used to administer.
FeedWordPress is designed with flexibility, ease of use, and ease of configuration in mind. You'll need a working installation of WordPress (version 3.0 or later), and also FTP or SFTP access to your web host. The ability to create cron jobs on your web host is helpful but not required. You don't need to tweak any plain-text configuration files and you don't need shell access to your web host to make it work. (Although, I should point out, web hosts that don't offer shell access are bad web hosts.)
|Charles Johnson
|aggregation, atom, feed, rss, syndication
To use FeedWordPress, you will need:
an installed and configured copy of [WordPress][] or [WordPress MU][] (version 3.0 or later).
FTP, SFTP or shell access to your web host
New Installations
Download the FeedWordPress installation package and extract the files on your computer.
Create a new directory named
feedwordpressin the
wp-content/pluginsdirectory of your WordPress installation. Use an FTP or SFTP client to upload the contents of your FeedWordPress archive to the new directory that you just created on your web host.
Log in to the WordPress Dashboard and activate the FeedWordPress plugin.
Once the plugin is activated, a new Syndication section should appear in your WordPress admin menu. Click here to add new syndicated feeds, set up configuration options, and determine how FeedWordPress will check for updates. For help, see the FeedWordPress Quick Start page.
To upgrade an existing installation of FeedWordPress to the most recent release:
Download the FeedWordPress installation package and extract the files on your computer.
Upload the new PHP files to
wp-content/plugins/feedwordpress, overwriting any existing FeedWordPress files that are there.
Log in to your WordPress administrative interface immediately in order to see whether there are any further tasks that you need to perform to complete the upgrade.
Enjoy your newer and hotter installation of FeedWordPress
WORDPRSS BACKWARD COMPATIBILITY FOR VERSIONS [4.5, 4.7]: This change fixes a fatal PHP error (on some web server configurations you'd see the message "Fatal error: require_once(): Failed opening required '[...]/wp-includes/class-wp-feed-cache.php'" on others, you might just see an HTTP 500 Internal Server Error or a blank page) when using FeedWordPress with versions of WordPress before 4.7. A change that I introduced to avoid a code module that had been deprecated in version 4.7 ended up relying on code modules that were only introduced as of version 4.7; so now, instead, FeedWordPress attempts to detect which modules the current version of the WordPress core makes available, and load the right modules depending on your WordPress version.
In theory, up to this point, FeedWordPress supported any version of WordPress from version 3.0 onward. In practice, version 3.0 was released over 6 years ago, and I can realistically commit only to testing out new releases of FeedWordPress with a few prior versions of WordPress; so I've updated the "Requires at least" field to version 4.5, the first major release issued in 2016. If you've really got to use FeedWordPress with older versions of WordPress, it will probably still work with any moderately modern release of WordPress, but I won't promise to keep it working with releases of WordPress that are more than about a year old.
WORDPRESS COMPATIBILITY: Tested with new versions of WordPress up to 4.7.
PHP WARNINGS UNDER WP 4.7: Eliminated cause of a PHP warning under WP 4.7 "Parameter 1 to FeedWordPressHTTPAuthenticator::set_auth_options expected to be reference" Warnings were due to a change in how http_api_curl hook is sometimes called in WP 4.7; so I changed the signature of the event handling method to avoid the notice. Props to @cogdog, @froomkin, @gwynethllewelyn et al. for flagging the issue and @garymarkfuller for suggesting a preliminary fix to the issue that was fairly similar to the solution I ended up adopting.
PHP 7 and PHP Strict Standards compatibility changes: @alexiskulash @daidais and @zoul0813 all sent pull requests through Github to fix some issues from a very old code base that has made its way from PHP 3.x through 5.x to the roll-out of PHP 7. Class methods should now fare better under modern versions of PHP and generate fewer "Deprecated" notices.
IMPROVEMENTS TO SCHEDULED AND AUTOMATIC UPDATES: use wp_loaded hook to check for magic URL parameters and to execute updates, to do pageload-based automatic updates, etc. Ensures that anything plugins or themes need to do in init to set up custom post types, taxonomies, etc. will be done before the update_feedwordpress updates are attempted. If you saw posts not getting put into the correct custom post type or custom taxonomies or similar problems when performing scheduled updates, but the problem seemed to go away when you manually performed updates through the wp-admin interface, then you might be able to solve those problems with this update.
WORDPRESS COMPATIBILITY: Tested with new versions of WordPress up to 4.5.
FILTERS AND ADD-ONS: Allow filters and add-ons to filter terms and taxonomy (categories, tags, custom taxonomies, etc.) more thoroughly and more fine-grainedly using syndicated_post_terms_match, syndicated_post_terms_match_{taxonomy}, syndicated_post_terms_unfamiliar, syndicated_post_terms_mapping, syndicated_item_feed_terms, and syndicated_item_preset_terms filters.
FILTERS AND ADD-ONS: Globals $fwp_channel and $fwp_feedmeta REMOVED. These global variables, originally introduced to allow filters access to information about the source feed in
syndicated_itemfilters were deprecated 6+ years ago. If you have any filters or add-ons which still depend on these global variables, you've been using obsolete techniques and you should see about fixing them to access data about the source feed using the SyndicatedPost::link element instead. For documentation, see the FeedWordPress documentation wiki at http://feedwordpress.radgeek.com/wiki/syndicatedpost and http://feedwordpress.radgeek.com/wiki/syndicatedlink.
BUGFIX: Syndication > Diagnostics HTTP diagnostic test widget was broken due to a dumb error on my part. Now fixed.
SMALL CODING CHANGES: Lots of small changes to code organization, incorporation of some PHP 5.x coding conventions, etc.
IMPORTANT SECURITY UPDATE: This version includes two important fixes for potential security vulnerabilities reported to me through support channels.
The first is a common problem across several plugins due to an ambiguity in the WordPress documentation and a change in the behavior of WordPress's built-in add_query_arg() and remove_query_arg() functions which could, under certain low-probability conditions, allow for potential XSS attack vectors. This fixes issue # 39 reported at https://github.com/radgeek/feedwordpress/issues/39 Thanks to github.com/quassy
The second is a security vulnerability fixes a security vulnerability that was reported to me privately (thanks to Adrián M. F.) which, under other low-probability conditions, could allow for SQL insertion attacks by a malicious user with access to login credentials, which would compromise data security.
It is IMPORTANT and worth your while to upgrade FeedWordPress as soon as possible in order to eliminate these vulnerabilities. If you have any questions or if there is something blocking you from making the upgrade which you need my help with, don't hesitate to get in touch.
ADMIN UI BUGFIX: "Update Now" button in feeds setting pages should now work once again instead of causing a PHP fatal error. See https://github.com/radgeek/feedwordpress/issues/46
SEVERAL OTHER SMALL BUG FIXES. See https://github.com/radgeek/feedwordpress/issues/32 https://github.com/radgeek/feedwordpress/issues/30 https://github.com/radgeek/feedwordpress/issues/29 etc.
FILTERS AND ADD-ONS: A number of new hooks for filters and add-ons to further customize the behavior of FWP have been added.
COMPATIBILITY/BUGFIX: Many users saw odd characters, especially "n," appearing in posts in versions of WordPress from 3.6 on, due to a change in when the API expects HTML data for posts to be slashed and when it does not. This has been fixed, so that the junk characters should no longer appear, regardless of your version of WordPress.
BUGFIX: A bug preventing FWP from saving categories assigned under Syndication > Categories & Tags has been fixed.
BUGFIX: Post-editing related metaboxes should now show up when you edit items of any post type, including custom types, not only normal WordPress posts.
BUGFIX: A bug in the admin UI that caused the "Alternative Feeds" / "Find Feeds" box to throw a permissions error has been fixed.
BUGFIX: A bug preventing proper mapping of categories and other terms in 2013.0504 has been fixed.
BUGFIX: A number of small fixes contributed through Github by Flynsarmy should eliminate PHP warnings for many users on several methods that are called as static methods within FeedWordPress.
BUGFIX: PHP 5.4 compatibility -- includes some more extensive fixes to compatibility issues with PHP 5.4's handling of global variables
DIAGNOSTICS: New diagnostics settings added to help track behavior of terms (categories, post tags, etc.) for syndicated posts.
- MODULE REORGANIZATION: Should ensure that all needed submodules will be properly included regardless of whether you are installing from github, from SVN, or from the WordPress plugins page. If you've been getting fatal errors about required modules not being found, this release should hopefully resolve the issue.
BUGFIX: Works properly again with WordPress installations that use a MySQL table name prefix other than the default
BUGFIX: Includes a couple of significant PHP 5.4 compatibility fixes. Now that PHP 5.4 is more widely deployed, Diagnostics will now also show PHP version and some other potentially useful troubleshooting information.
ADMIN UI: Better indicates your options when deleting a syndicated post so as to let you know whether it will be Trashed (and thus not resyndicated) or Erased (and thus potentially resyndicated)
ADMIN UI: Adds an AJAXy Test Expression button to allow live testing of sample results from expressions in Custom Post Settings.
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
<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 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.
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.
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.
HTTP BASIC AND DIGEST AUTHENTICATION SUPPORT: FeedWordPress now offers improved support for syndicating feeds that make use of HTTP Basic or HTTP Digest authentication methods. In order to set up authentication on one of your feeds, just go to its Settings > Feed page, and click on the "Uses Username/Password" link underneath the Feed URL. Enter the username and password for accessing the feed, then select the authentication method. (If you're not sure which method your feed provider uses, try Basic first.) Save Changes, and syndicate away.
NOTE: HTTP Digest support requires the curl module for PHP. If you are not sure whether this module has been installed, contact your web hosting provider to check.
WP 3.3 (BETA) COMPATIBILITY: This version fixes an init-sequence bug that could cause intrusive warning messages or fatal errors in WP 3.3 beta versions.
BUGFIX: FIXES LONG DELAYS IN UPDATES SCHEDULES IN LARGE INSTALLATIONS. A performance feature introduced in version 2011.0721 had some flaws in its implementation, which tended to create serious delays (on the order of several hours) in FeedWordPress's attempts to schedule updates for feeds, when users had a very large number of feeds (several dozen or more) in their FeedWordPress installation. This feature has been reconfigured to adjust dynamically to the number of feeds in Syndicated Sources and the frequency with which they are updated. If you've seen a lot of ready-to-update feeds piling up, several hours after they were supposed to get updated, then this upgrade should better ensure that your feeds get updated in a timely fashion.
BUGFIX: syndicated_item_guid FILTERS FIXED. Previous versions of FeedWordPress theoretically allowed for filters on the syndicated_item_guid hook, which was intended to filter the globally-unique identifier element (rss:guid or atom:id) -- useful if you need to convince FeedWordPress to use different guids, or to recognize two or more incoming posts as versions of the same post rather than as distinct items. However, while the hook affected the guid stored in the WordPress database, it did not affect the guid used to check whether an incoming feed item had already been syndicated or was a new item -- which greatly limited the practical usefulness of the filter. This bug has been fixed: syndicated_item_guid filters should now properly control not only the final database record, but also the initial uniqueness test applied to posts.
BUGFIX: SERIOUS BUG CAUSING RARE UNEXPECTED DELETION OF PAGES AND OTHER CONTENT. A bug in the guid-checking code for some rare kinds of guids could cause content in the wp_posts table to seemingly disappear at random after FeedWordPress updates.This most frequently but not exclusively affected static pages. What actually happened is that in these rare cases the existing static page was mistaken for an older version of the new incoming syndicated post, which was then stored as a new revision of the original page. The bug that caused these mistaken identities has been fixed.
BUGFIX: UNWANTED AUTOMATIC PAGE-LOAD-BASED UPDATES NO LONGER A NUISANCE. Some users encountered a bug in which FeedWordPress would adopt an automatic page-load-based update method, even if they had requested that it not do so, and that it use a manual or cron job update method instead. The bug causing this has been fixed, and page-load-based updates should no longer trigger unless explicitly turned on.
WP 3.2 USER INTERFACE COMPATIBILITY: POST TAGS BOX NOW WORKS AGAIN. The release of WordPress 3.2 caused a breakage in the tags box which prevented you from adding or removing tags under Syndication --> Categories & Tags. (The breakage was the result of an incompatibility introduced by the new release of jQuery.) This breakage has now been fixed, and the tags box should work correctly again.
FEED UPDATE SCHEDULING IMPROVEMENTS: UI. The Syndicated Sources table now provides considerably more data to understand update scheduling, when specific scheduling decisions are made because of, e.g., requests from the feed producer.
FEED UPDATE SCHEDULING IMPROVEMENTS: ENFORCEABLE "MINIMUM INTERVAL" SETTING TO SPACE OUT UPDATES. Some feeds request specific update schedules, using standard elements such as sy:updateFrequency and rss:ttl. Normally, FeedWordPress respects any scheduling requests that a feed makes -- if it requests a longer gap between polls than what FWP would normally adopt, then FWP slows down to meet the request. If it indicates a shorter gap than what FWP would normally adopt, FWP speeds up and checks that feed for updates more often than it normally would. Now, there should not be any way for user settings to override an explicit slow-down request from the feed producer -- if producers indicate a particular update schedule, then polling the feed more frequently than they request is considered abusive behavior. But there's no reason why users should not be able -- if they so desire -- to override speed-up requests, and poll a feed less frequently than the indicated update schedule, if the FWP user wants to space update checkins over a longer interval of time. Before, they could not do this: FWP always sped up to meet the indicated update schedule. Now, they can do this, by using the new "Minimum Interval" setting in Syndication --> Feeds & Updates..
WP 3.2 COMPATIBILITY: ELIMINATES FATAL ERROR "Call to undefined method WP_SimplePie_File::WP_SimplePie_File() in [...]/wp-content/plugins/feedwordpress/feedwordpress.php on line 1841." The latest release of WordPress, version 3.2, has shifted the minimum requirements up to PHP 5.2, and in line with the shift to PHP5 they have rewritten a number of code segments that made use of now-obsolete PHP4 idioms. Unfortunately, this caused a fatal error whenever FeedWordPress attempted to make use of the cache, since FWP's caching plugin was written to match the older idiom. FeedWordPress has been updated to follow the new, PHP5 idiom when possible, thus eliminating the fatal error.
PERFORMANCE: The handling of queries to determine whether posts had been previously syndicated produced some very slow queries (usually, but not always, involving a scan over the MD5(post_guid) column of the table). The code that prepares MySQL queries for previously-syndicated checks has been revised to eliminate the MD5(post_guid) scan entirely, and to significantly improve performance by eliminating other unnecessary clauses.
BUGFIX: NO LONGER DESTROYS STICKY POSTS. Previous versions could destroy (or, more precisely, replace the content of) sticky posts due to some queries mashed together in unexpected ways by WordPress. Version 2011.0706 accounts for and eliminates the problem; your sticky posts should be safe once again.
BUGFIX: GUIDS CONTAINING MYSQL-ESCAPED CHARACTERS NO LONGER CAUSE DUPLICATE POSTS TO APPEAR. One remaining source of duplicate post issues in 2011.0602 was guids that contained characters that needed to be escaped for MySQL, such as single quotes and double quotes. The work-around for handling filtered URIs has now been corrected to ensure that these do not cause duplicate posts.
WP 3.1.3 COMPAT / BUGFIX: WHITESPACE IN GUIDS NO LONGER PRODUCES DUPLICATE POSTS. The work-around for handling filtered URIs in guid elements has now been extended to handle URIs that were filtered because of leading or trailing whitespace, in addition to URIs that were filtered because of unapproved schemes.
WP 3.1.3 COMPAT / BUGFIX: RELATIVE URLS IN GUIDS NO LONGER PRODUCE DUPLICATE POSTS. The work-around for handling filtered URIs in guid elements has now been extended to handle URIs that were altered without being filtered out entirely (most commonly because a scheme was added to a relative URL).
BUGFIX: UPDATES TO POST NO LONGER CAUSE DUPLICATE DRAFT VERSION TO APPEAR. Under certain conditions in 2011.0531, an update to an existing post would not be properly applied to the post itself, but rather would appear as a duplicate post with Draft status. This bug has been eliminated, and updates will now be properly inserted as revisions to the existing post.
WORDPRESS 3.1.3 COMPATIBILITY: DUPLICATE POSTS ISSUE FIXED. Due to internal changes in the way that WordPress handles post guids in the most recent release (3.1.3), many users experienced problems with many duplicate posts appearing in rapid succession. (Specifically, this would happen with any posts using tag: URL guids -- such as all the posts coming from Blogger feeds or feeds from other Google services.) This compatibility release of FeedWordPress eliminates the issue by working around the new restrictions on tag: URLs.
NEW AND IMPROVED DIAGNOSTICS: Syndication --> Diagnostics now contains some new diagnostics settings useful for debugging problems with duplicate posts (allowing you to easily view the guid of posts in the WordPress posts database and allowing you to track the SQL used to check for existing versions of a syndicated post).
DIAGNOSTICS IMPROVEMENTS; "THERE MAY BE A BUG IN FEEDWORDPRESS" CRITICAL ERROR NOTICES ELIMINATED: This version includes some major improvements to the Syndication --> Diagnostics section, which should aid in troubleshooting difficulties with items failing to be imported, posts failing to be properly inserted into the database, or updates failing to be recorded. If you have been encountering critical error / bug notices with a white screen and the message "THERE MAY BE A BUG IN FEEDWORDPRESS," followed by an extraordinarily long dump of mostly incomprehensible diagnostic information, you'll be happy to know that the condition causing these notices has been eliminated. In the few cases where errors may still crop up with database insertions, FeedWordPress will now produce a significantly more manageable and more useful diagnostic message.
BUGFIX: NEW POSTS FAILING TO APPEAR IN A CLEANLY-INSTALLED FEEDWORDPRESS SYSTEM. If you encountered a recurring problem with FeedWordPress failing to import new posts, after a clean install of FeedWordPress (i.e., not an upgrade from a previous version), this problem may have been the result of a bug with author-handling which has now been fixed in the 2011.0512 release. (If the problem does not go away with the upgrade, this version also includes significant improvements to the Diagnostics system, which will help track down what is causing it in your particular case.)
PERFORMANCE: New handling of update hashes allows FeedWordPress to avoid a certain kind of infinite loop, caused when two more more different syndicated feeds each carried a version of the same item (for example, because it appeared on two different aggregator feeds that you're syndicating). In previous versions, when this kind of loop cropped up, syndicated posts could pile up an indefinitely large number of revisions -- each revision alternating between the version from each of the two feeds where it appeared -- which would, over time, dramatically inflate the size of the database, and kill the performance of queries on the post table. This issue has been resolved: revisions of the post that have been syndicated once will not be re-syndicated over and over again.
AUTHOR LISTS: Lists of authors presented on the Author settings pages should now be easier to scan through, with author names arranged in alphabetical order.
FEED ITEM DATE PARSING: More tweaks to make date-time handling more resilient when feeds provide broken or weird values for the timestamps on syndicated items. FWP will now attempt to work around unparseable timezone values.
AUTHOR MATCHING: Now attempts to match author names against the WP login name in addition to display_name; when creating user record, also fills in some best-guess values for nickname, firstname and lastname. Also properly picks up Atom 1.0 author/uri data from feed.
COMPATIBILITY: FeedWordPress has been successfully tested for compatibility with recent releases of WordPress, up to version 3.1.2.
BUGFIX: DUPLICATE POSTS WHEN GUIDS ARE TOO LONG: When feeds included exceptionally long GUIDs, FeedWordPress could occasionally get into a situation where posts with the long GUIDs would be duplicated over and over again with each update (because FWP failed to store the full GUID, due to length constraints in the relevant database tables). Without the full GUID, FWP would not know that the post had already been syndicated once. This bug has been fixed, and should no longer produce duplicate posts.
HTTP TIMEOUT SETTING: If you are frequently running into timeout problems with one or more of the feeds you syndicate, FWP now allows you to adjust the timeout for HTTP requests using a global or feed-by-feed setting.
HTTP GET PARAMETERS: You can now temporarily or permanently add HTTP GET parameters to a subscription using an interface in Syndication --> Feeds & Updates. This is especially helpful for making quick, short-term changes to a subscription (for example, to pull in all the previous items from a web service, before settling down to pulling in only newly updated items).
DIAGNOSTICS SYSTEM: Added several new diagnostics which are useful in troubleshooting, and established a framework for add-on modules to hook in with their own diagnostic messages.
UI: Adjusted some internal coding, which should allow for settings pages and add-ons to properly display multiple category pickers on a single settings page.
PHP4 COMPATIBILITY TWEAKS: This version makes some tweaks to the handling of object references which should improve compatibility with older versions of PHP. (Although, I should note, web hosts that still force you to run under PHP 4 -- in 2011! -- are bad web hosts.)
IMPROVED PERFORMANCE: This version eliminates a major performance drag that shows up on sites with large numbers of users (due to some poor decisions about where to place a user query, which caused the user table to be scanned frequently when it did not need to be). If you experienced serious problems with CPU load or slow database performance under 2010.0905, which kicked in immediately when FWP was loaded and tended to disappear immediately if FWP was de-activated, it is likely that upgrading away from 2010.0905 to the most recent version will resolve your problem.
- BUGFIX: CATEGORIES AND TAGS CORRECTLY ASSIGNED IN AUTOMATIC UPDATES. Version 2010.0903 switched over to a new way of assigning categories and tags as part of its support for handling custom taxonomies. Unfortunately, the method that it uses is subjected to some checks of the current user's capabilities, which creates problems for posts that are being inserted into the WordPress database when there is no current user logged in (as, for example, when an update is being carried out from a cron job or automatic update). The result was that posts from cron jobs and automatic updates ended up with no Categories and no Tags being assigned. This bug has now been fixed: in 2010.0905, Tags and Categories should be correctly assigned to all posts, regardless of whether they were added from manual updates, cron jobs, or automatic updates.
WORDPRESS 3 REQUIRED: Please note that this release of FeedWordPress requires WordPress 3.0 or later. If you are currently using a 2.x branch of WordPress, you will need to upgrade to WordPress 3 before you can successfully upgrade FeedWordPress.
BUGFIX: NO MORE DISAPPEARING "SYNDICATED SOURCES" PANEL; INTERNET EXPLORER UI GLITCH APPARENTLY FIXED: Several users independently reported a problem with FWP 2010.0623 and various versions of IE. A problem with the HTML markup caused IE (but not Firefox or Chrome) to completely hide the Syndicated Sources administration panel (the main list of currently-syndicated sources, and the main location for adding new sources, under the Syndication menu item) when a user added their first syndicated feed. Maddeningly, the glitch seemed to affect some IE users and not others: I was never able to reproduce the problem for myself on my own machines. However, the markup of Syndicated Sources has undergone significant changes and corrections since 2010.0623, and two independent sources who had been having this problem confirm that they no longer encounter it with the updated version. For the time being, I am going to declare this bug squashed.
BUGFIX: MORE PROTECTION AGAINST FATAL ERRORS FROM PLUGGABLE VERSIONS OF SimplePie: FeedWordPress now takes some precautions that should help to better avoid conflicts for users who have installed pluggable versions of SimplePie for another plugin or theme. (You may not know that you have done this; but if you've been encountering fatal errors indicating that you cannot redeclare class SimplePie, or something along those lines, there is now a better chance that those fatal errors will be eliminated.
PERFORMANCE: SIGNIFICANTLY REDUCED MEMORY CONSUMPTION FOR LARGE UPDATES: FeedWordPress is still a memory-hungry little module, especially when you are dealing with very large feeds. However, users should notice a significant reduction in memory overloads, especially if they update a large number of feeds at once.
USER INTERFACE IMPROVEMENTS: Nothing is radically different, but there's been a fair amount of extra spit and polish added, including a convenient new Dashboard widget that may save you a trip to the Syndication menu, a lot of effort to make the relationship between global and feed-by-feed settings more obvious to the user and more easily controllable, to make navigation between settings pages easier, to sand off a few rough edges, and to make other improvements on the margins. I hope you'll like how it looks.
ADDING MULTIPLE FEEDS: FeedWordPress now provides a convenient mode for adding multiple feeds at once, using either a copy-and-pasted list, or else an OPML file. Go to Syndication --> Syndicated Sources and check out the two new buttons underneath the New Source input box. When you have to add a number of feeds at once, this can save you considerable time and trouble.
IMPROVED HANDLING OF AUTHORS WITH DUPLICATE E-MAIL ADDRESS AND AUTHORS WITH NAMES WRITTEN IN FOREIGN SCRIPTS: WordPress 3 is increasingly picky about what it will accept for new author accounts, and some of the conditions it imposes can cause error conditions that prevent posts from being properly syndicated, or properly attributed, if authors happen to have identical e-mail addresses, or if users are given usernames that are written in non-Western scripts. FeedWordPress now handles these much better, and systematically works to avoid clashes between syndicated authors' account names or in their e-mail addresses, which should result in significantly better results in mapping author names to WordPress user accounts.
MAPPING CATEGORIES ON SYNDICATED POSTS TO TAGS NOW BETTER SUPPORTED: In previous versions, the only way for the Categories provided by a syndicated feed to be mapped into Post Tags was to instruct FWP to create new tags, rather than new categories, for unfamiliar categories from the feed. This works fine if you want tags to be the default; but if you want only a specific set of tags, there was no way to get them without getting most or all other categories imported as tags. You can now do this by creating a tag (under Posts ==> Post Tags) before importing the post; when the syndicated category matches a pre-existing tag, the incoming post will be tagged with that tag, without creating a local Post Category.
REL-TAG MICROFORMAT SUPPORT FOR INLINE TAGS: Syndicated posts that contain inline tags, marked up using the Rel-Tag microformat http://microformats.org/wiki/rel-tag, are now tagged with the tags provided by Rel-Tag format links.
MUCH GREATER CONTROL OVER CATEGORY AND TAG MAPPING: This is partly the result of building in support for a potentially endless set of custom taxonomies (see below), but in general there has been a great deal of effort towards giving you more control over how categories and tags provided by the feed are mapped into terms on the local blog. In particular, you can now force FeedWordPress to create only categories from categories and tags provided by the feed; or to create only tags; or to search both categories and tags for a match; or you can simply force it to drop all of the categories provided by the feed and use only categories or tags that you explicitly provide. In addition, you can now also choose whether to override global categories settings with a local, feed-specific setting; or whether to add together both the global categories and the local feed-specific categories -- depending on whatever your use-case may demand.
CUSTOM POST TYPES AND TAXONOMY SUPPORTS: This is mainly for the super-geeky, but if you use other plugins or themes that make significant use of WordPress's support for custom post types and custom taxonomies, you may be pleased to find that FeedWordPress now allows you to feed incoming posts into any custom feed type that you wish, and to map categories and tags from the feed to custom taxonomies as well as to the standard Category and Tag taxonomies.
STORING NAMESPACED CUSTOM FEED ELEMENTS IN POST CUSTOM FIELDS: If you would like to use FeedWordPress's support for storing custom meta-data from feed elements in the custom fields for a post (for example, to store geolocation data or iTunes media meta-data), you'll find that it's now much easier for you to access these namespaced elements. You always could access them, but in previous versions you might have to write something ugly like $(/{http://www.w3.org/2003/01/geo/wgs84_pos#}lat) just to get at the value of a
<geo:lat>tag. Now, as long as you use the same mnemonic codes that the feed producer used, you should always be able to write a nice, simple expression like $(/geo:lat) to get the value of a tag.
CUSTOM DIRECTORY STRUCTURE SUPPORT: if you poke at it enough, WordPress is relatively flexible about where it should store admin interface code, uploaded content, plugins, and a number of other things that occupy an important place in the WordPress directory structure. Previous versions of FeedWordPress encountered serious errors or broke entirely when used with directory structures other than the default. This should now be fixed: FWP now supports custom directory structures wherever WordPress allows them to be customized, rather than depending on the default locations. Enjoy your freedom!
MANY NEW FILTERS AND API UTILITY FUNCTIONS FOR ADD-ON PROGRAMMERS: There have been too many improvements to list them all in this ChangeLog, but it means that much more power and ease for folks who are customizing FeedWordPress through PHP filters or add-on modules. Fuller documentation will be put up at the Wiki at feedwordpress.radgeek.org soon.
WORDPRESS 3.0 COMPATIBILITY / AUTHOR MAPPING INTERFACE ISSUES: I resolved a couple of outstanding issues with the author mapping interface (Syndication --> Authors), which were preventing new users from being created correctly and author mapping rules from being set up correctly. These partly had to do with new restrictions on user account creation introduced in WordPress 3.0; anyway, they should now be fixed.
MORE EFFICIENT SYNDICATED URL LOOKUPS: Several users noticed that the bug fix introduced in 2010.0528 for compatibility with post-listing plugins caused a lot more queries to the database in order to look up numerical post IDs from the URL provided to the filter. This shouldn't cause any major problems, but it is not as efficient as it could be; the code now takes advantage of a more efficient way of doing things, which usually will not require any additional database queries.
SIMPLEPIE FEED UPDATE ISSUES: If you have been having significant problems with getting feeds to update correctly, this may be the result of some bugs in the implementation of SimplePie caching that ships with WordPress (as of version 3.0). (You would most commonly experience this error if you continually saw errors such as "No feed found at <...>" in your updates.) Fortunately, SimplePie allows for a great deal of extensibility and this allows me to work around the problem; these error conditions should now be mostly eliminated when the underlying feed is valid.
UI: SHOW INACTIVE SOURCES: When you use the default unsubscribe option -- which turns off the subscription to a feed while preserving the posts from it and the syndication-related meta-data for the feed -- the unsubscribed feed can now easily be viewed in a special "Inactive" section of the Syndicated Sources page. (As a side benefit, if you've accidentally, or only temporarily, turned off the subscription to a feed, it is now much easier to restore the feed to being active, or to delete it permanently, if you prefer.
UI: FEED FINDER / SWITCH FEED INTERFACE IMPROVEMENTS: changes to styling and options for the feed finder / switch feed, which should now make it easier, in some cases, to find alternative feeds, and make interface options more clearly visible.
syndicated_item_updatedNOW PROPERLY AFFECT THE DATING OF POSTS. These filters used to affect some date-related settings, but not others -- and, most importantly, not the final date that is set for a post's publication or last-modified date in the WordPress database. Now, they do affect that, as they should. (Filters should receive, and return, a long integer, representing a Unix epoch relative timestamp.)
MAGIC URL TO CLEAR THE CACHE: Suppose that you need to clear the feed cache, for whatever reason; suppose, even, that you need to clear it on a regular basis. One way you might do this is by logging into the FeedWordPress administrative interface and going to Syndication --> Performance. Another way you might do it, now, is to simply send an HTTP request to a magic URL provided by FeedWordPress: if your blog is at example.com, the URL would be http://example.com/?clear_cache=1
CATEGORY BOX INTERFACE ELEMENT FIXED FOR WP 3.0: Stylesheet changes between WordPress 2.9.x and the WordPress 3.0 RC caused the Categories box under Syndication --> Categories & Tags to malfunction. This has been fixed.
LINK CATEGORY SELECTION BOX IN SYNDICATION ==> FEEDS FIXED FOR WP 2.8 AND 2.9: A WP 3.0 compatibility change introduced in 2010.0531 inadvertently broke the Syndicated Link Category selector under Syndication --> Feeds & Updates in WP 2.8 and WP 2.9, causing the post categories to be displayed in the selector rather than the link categories. This should now be fixed so that the selector will work correctly under both the current versions of WordPress and the 3.0 RC.
MORE PERMISSIVE HANDLING OF FEEDS WITH BAD CONTENT-TYPE HEADERS: One of the small advantages that MagpieRSS had over SimplePie is that it was more tolerant about parsing well-formed feeds that the remote web server happened to deliver with weird or incorrect HTTP Content-type headers. In feeds affected by this problem, the new SimplePie parser would simply fail to find a feed, due to its being led astray by the contents of the Content-type header. This version includes an extension to SimplePie's content-type sniffer that offers more permissive handling of the HTTP headers.
MORE FULL-TEXT "EXCERPTS" NOW PROPERLY SHORTENED. Version 2010.0528 introduced code to control for cases in which elements intended for item summaries are (ill-advisedly) used to carry the full text of posts; past versions of FeedWordPress would simply include the full text of the post in the excerpt field, but newer versions now attempt to detect this condition when it arises and to head it off, by blanking out the excerpt field and filling it with an automatically generated short, plain text excerpt from the full content. This release broadens the test conditions that indicate when an excerpt field is treated as identical to the full text of the post, and should therefore improve the handling of some feeds (such as Google Reader feeds) where the full text of each post was still appearing in the excerpt field.
syndicated_item_updatedFILTERS NOW ALLOW FILTER AUTHORS TO CHANGE POST TIMESTAMPS. You can now use the
syndicated_item_updatedfilter hooks to write filters or add-ons which directly change the post date and most-recently-updated timestamps on incoming syndicated posts. Props to niska for pointing out where the filters needed to be applied in order to change WordPress's internal timestamps for incoming posts.
PERMALINK / CUSTOM FIELDS PROBLEM RESOLVED: An issue in 2010.0528 caused some posts to be imported without the proper syndication-related meta-data being attached (thus causing permalinks to point back to the aggregator website rather than to the source website, among other problems). This problem has been resolved (and a fix has been applied which will resolve the problem for any posts affected by this problem, if the original post is recent enough to still be available on the feed).
UI: The "Back End" section has been split into two separate sections -- "Performance" (dealing with caching, database index, and other performance tweaks), and "Diagnostics" (dealing with debug mode, update logging, and a number of new diagnostic tests which I will be rolling out over the next few releases).
Several minor interface bug fixes and PHP warning notices eliminated.
SIMPLEPIE IS NOW USED TO PARSE FEEDS; NO MORE MAGPIERSS UPGRADES NEEDED: One of the biggest changes in this release is that FeedWordPress no longer depends on MagpieRSS to parse feeds, and has switched to the much more up-to-date and flexible SimplePie feed parser, which is included as a standard part of WordPress versions 2.8 and later. Using SimplePie will hopefully allow for better handling of feeds going further, and will allow me greater flexibility in determining how exactly the feed parser will operate. It also means that FeedWordPress no longer requires special upgrades to the WordPress core MagpieRSS files, and should eliminate quite a bit of complexity.
MAGPIERSS COMPATIBILITY LAYER FOR EXISTING FILTERS AND ADD-ONS: However, I have also implemented a compatibility layer to ensure that existing filters and add-ons for FeedWordPress which depended on the MagpieRSS data format should not be broken by the switch to SimplePie. Going forward, I recommend that new filters and add-ons be written to take advantage of the SimplePie object representations of items, feeds, etc., rather than the MagpieRSS arrays, but the MagpieRSS arrays will still be available and older filters should continue to work as they have in the past.
COMPATIBILITY WITH WORDPRESS 2.9.x and 3.0: This release has been tested for the existing WordPress 2.9.x branch and with the upcoming release of WordPress 3.0. Changes in the user interface JavaScript between WordPress 2.8.x and WordPress 2.9 caused the tag box interface element to break in the Syndication --> Categories & Tags settings page; changes in the API functions for adding new authors caused fatal errors under certain conditions in WordPress 3.0. These breakages have been fixed.
DROPPED LEGACY SUPPORT FOR WORDPRESS PRIOR TO 2.8: Because SimplePie is not included with versions of WordPress prior to 2.8, I have chosen to drop legacy support for WordPress versions 1.5 through 2.7. If you are using FeedWordPress with a version of WordPress before 2.8, you will have to upgrade your installation of WordPress in order to take advantage of this release.
PHP 5.3 COMPATIBILITY: A couple of compatibility issues, which were causing fatal errors amd ugly warnings for users of PHP 5.3, have been eliminated.
Features and Processing
INTERFACE REORGANIZATION: The interface restructuring, began with Version 2009.0612, has been completed. Catch-all settings pages have been eliminated entirely for pages that cover each aspect of handling a feed: Feeds & Updates, Posts & Links, Authors, Categories & Tags, and Back End handling of the database and diagnostic information. Extensive new interface hooks allow add-on modules to significantly change or extend the FeedWordPress admin interface and workflow.
STORING INFORMATION FROM THE FEED IN CUSTOM FIELDS: Many users have written to request the ability to store information from elements in the feed in a custom field on each post. (So that, for example, if post includes a
itunes:durationelement, you could store the contents in a Custom Field called
durationon the post (for a Theme to access later). The Custom Post Settings under Syndication --> Posts & Links now allow you to access any item or feed tag, using a syntax similar to a much-simplified version of XPath. See Posts & Links settings for details.
UPDATE-FREEZING ON MANUALLY EDITED POSTS: FeedWordPress now allows you to mark posts that have been manually edited, so that the changes you make will not be overwritten by later updates from the feed. If you make manual edits to a particular post, just check the "Manual editing" checkbox in order to protect your changes from being overwritten. If you want to block all posts from being updated after they are imported for the first time, a new "Updated Posts" setting in Posts & Links allows you to freeze all posts from a particular feed, or all syndicated posts.
SETTING: FEED-BY-FEED SETTINGS FOR WHERE PERMALINKS POINT TO: You've always been able to tell FeedWordPress whether permalinks for posts should point to the original source of the story or the local copy. Now you can choose different policies for different feeds, instead of one global policy for all feeds. (Of course, you can still use a global default if you prefer.)
SETTING: USER CONTROL OVER TIMING BASIS. You can now determine the schedule on which feeds are considered ready to poll for updates -- by default feeds become ready for polling after about 1 hour. You can now increase or decrease the time window under Syndication --> Feeds & Updates. (However, please pay CAREFUL ATTENTION to the recommendations and DO NOT set the scheduling lower than 60 minutes unless you are ABSOLUTELY SURE that you have specific permission from webmaster who provides that specific feed to poll more frequently than that. If you set this too low (and about 60 minutes is the polite minimum if you haven't been given a different figure), most webmasters will consider the frequent hits on their server as rude, or even downright abusive.
OTHER SETTINGS: New settings also include the ability to stop FWP from resolving relative URLs within syndicated content, and the ability to choose whether FeedWordPress should indicate the comment feed from the original source, or the local comment feed, when providing the comment feed URL for a syndicated post.
BETTER DATE HANDLING -- FEWER FLASHBACKS TO 1969 and 1970: FeedWordPress has made some bugfixes and some improvements in the logic for parsing dates. This should allow FeedWordPress to correctly parse more dates in more feeds; and, in the last resort, when FeedWordPress fails to correctly parse a date, to fall back to a more intelligent default. This should hopefully avoid most or all error conditions that have resulted in articles being erroneously dated to the dawn of the Unix epoch (31 December 1969 or 1 January 1970).
FULL-TEXT "EXCERPTS" NOW PROPERLY SHORTENED. Based on a straightforward reading of the existing RSS specs, it's reasonable for the rss:description element to be read as a plaintext summary or excerpt for the item containing the description -- with the full text of the item, if available, in another, better-suited element, such as the de facto standard content:encoded extension element. The problem is that uses of RSS rarely have much to do with anything like a straightforward reading of the specs. As a result, many actual RSS producers in the wild put the full text of the article in a description element. But since FeedWordPress has treated this text as a summary, this produces aggregated posts with lengthy "excerpts" containing the full text of the article. This release of FeedWordPress fixes the problem by doing a little digging before treating rss:description as a summary: if the description element is used properly as a plain text summary, then FeedWordPress will take the summary provided by the feed, rather than recreating its own excerpt from the full text; but if an RSS item has no full-text element other than description, FeedWordPress will treat the description element as the full text of the article, and generate a shortened excerpt automatically from that text.
TEMPLATE API: new template tags
the_local_permalink()allow you to access the permalink for a post on your aggregator site, even when FeedWordPress is rewriting permalinks to point to the original source site.
NEW HOOKS FOR ADD-ONS AND FILTERS: I have added a number of new hooks which allow add-on modules to filter more precisely, gather information at more points, and to enhance the FeedWordPress admin interface. For a list of new hooks and documentation, see the FeedWordPress documentation wiki at http://feedwordpress.radgeek.com/wiki/add-ons-and-filters
FILTER API: A number of new utility methods have been added to the SyndicatedPost class to make it easier for filters and add-ons to
FILTER API: Globals $fwp_channel and $fwp_feedmeta DEPRECATED. These global variables, originally introduced to allow filters access to information about the source feed in
syndicated_itemfilters (which were passed in through global variables rather than as parameters because of a bug in WP 1.5 which was then fixed in 1.5.1) have been DEPRECATED. If you have any filters or add-ons which still depend on these global variables, you should see about fixing them to access data about the source feed using the SyndicatedPost::link element instead. For documentation, see the FeedWordPress documentation wiki at http://feedwordpress.radgeek.com/wiki/syndicatedpost and http://feedwordpress.radgeek.com/wiki/syndicatedlink.
DIAGNOSTICS: I've included a number of new diagnostic options and messages, which should allow an experienced user to better investigate any problems that may crop up.
Bug Fixes
BUGFIX: & IN PERMALINKS NO LONGER CAUSING ATOM OR HTML VALIDATION EFFORTS: Many users reported an issue in which syndicating a feed with special XML characters in the URLs (& was the most common, since it is used to separate HTTP GET parameters) would cause the aggregator's feeds to produce invalid (malformed) XML. This update addresses the issue in Atom feeds. Unfortunately, it has not been technically possible to address the problem in RSS 2.0 feeds, due to limitations on WordPress's internal templates for RSS feeds.
BUGFIX: BROKEN URLS IN "POPULAR POSTS" AND SIMILAR PLUGINS SHOULD NO LONGER BE BROKEN. A number of users noticed an issue where plugins and templates that listed posts in locations outside of the post loop (for example, "Popular Posts"-style plugins that listed posts in the sidebar), often produced the wrong URL for post links. (Typically, all the posts listed would get the same wrong URL.) This should now be fixed. Thanks to Björn for sending in a quick fix!
MINOR BUGFIXES: This release includes a number of fixes to minor bugs and compatibility issues, including: silent failures of the "Syndicate" button, "Illegal Offset Type" error messages from MagpieRSS, and others.
BUGFIX: WORDPRESS 2.8 AJAX COMPATIBILITY ISSUES RESOLVED (blank or truncated "Syndicated Sites" administration page): Due to changes in the AJAX interface elements between WordPress 2.7 and WordPress 2.8, several FeedWordPress users encountered an issue where the front "Syndication" page in the FeedWordPress administrative interface would come up blank, without the normal "Syndicated Sites" list and "Update" control, or sometimes wth the boxes visible but one or both of them truncated, with only the title bar. This issue should now be resolved: with the new version of FeedWordPress, the compatibility issue that caused the disappearance should be eliminated, and if boxes are shown with only their handle visible, you should once again be able to drop down the rest of the box by clicking once on its title bar.
BUGFIX: TAG SETTING WIDGET FIXED. Due to changes in interface elements between WordPress 2.7 and WordPress 2.8, people using FeedWordPress with WordPress 2.8 found that the widget for setting tags to be applied to all syndicated posts, or all syndicated posts from a particular feed, no longer displayed "Add" and "Remove" buttons for individual tags. This issue has now been fixed, and the tagging widget should once again work more or less exactly like the tagging widget for individual posts in the normal WordPress admin interface.
BUGFIX: MYSTERY ERRORS WITH WITH WP_Http_Fsockopen HTTP TRANSPORT ELIMINATED: Thanks to a combination of a subtle bug in FeedWordPress, and changes to the HTTP transport code in WordPress, a number of users encountered an error in which any time they attempted to add a new feed through the FeedFinder interface, FeedWordPress would fail and display an HTTP request failure diagnostic message. The subtle bug has been fixed, and with it, most of these errors should now be eliminated.
Be sure to upgrade your MagpieRSS to the most recent MagpieRSS version after you have insalled FeedWordPress 2009.0618, or this bug fix will not take effect.
INTERFACE/BUGFIX: WORDPRESS 2.8 CATEGORY BOX FIX. Thanks to a subtle change in class names between the WordPress 2.7 and 2.8 stylesheets, category boxes in the FeedWordPress settings interface tended to overflow and have a lot of messy-looking overlapping text under WordPress 2.8. This has now been fixed.
FeedFinder FAILURE DIAGNOSTICS: When FWP's FeedFinder fails to find any feeds at a given URL (for example, when you are trying to add a subscription through the administrative interface and you run into an error message), FeedWordPress now provides more diagnostic information for the reasons behind the failure. If that helps you, great; if not, it should help me respond more intelligently to your support request..
WORDPRESS 2.8 COMPATIBILITY: FeedWordPress 2009.0612 has been tested for compatibility with the recent version 2.8 release of WordPress.
INTERFACE RESTRUCTURING: In order to avoid settings posts from becoming too crowded, and to modularize and better organize the user interface, new "Posts" and "Categories & Tags" subpages have been created under the "Syndication" menu. "Posts" controls settings for individal syndicated posts (such as publication status, comment and ping status, whether or not to use the original location of the post as the permalink, whether or not to expose posts to formatting filters, and so on). "Categories & Tags" controls settings for assigning new syndicated posts to categories and tags, such as categories or tags to apply to all syndicated posts, and how to handle categories that do not yet exist in the WordPress database. These subpages, like the Authors subpage, handle settings for the global default level and for individual syndicated feeds.
Corresponding to these new subpages, the old Syndication Settings and Feed Settings subpages have been cleaned up and simplified, and now only link to the appropriate subpages for options that can be set in the Posts, Authors, or Categories & Tags subpages.
FEATURE: ADD CUSTOM SETTINGS TO EACH SYNDICATED POST: FeedWordPress has long had an interface for creating custom settings for each syndicated feed which could be retrieved in templates using the
get_feed_meta()template function. But it had no feature for ad


text:
Peabody HS Hillsboro, TX Alumni List
Last names starting with "K"
Looking for Peabody High School Hillsboro, TX alumni not listed? If so, check out Classmates.com® - hundreds of more PHS alumni have posted their profiles.
About the Peabody High School Alumni Directory
Check out all of the names of the Peabody High School alumni that attended high school in Hillsboro that are listed above. Registering will allow you to join the directory. Peabody High School alumni can relive their experiences from high school by sharing memories and pictures, reconnecting with those alumni listed, and more.

subset: commoncrawl


text:
Bios flash for the m5750/m5790 to enable unlockable T7600 core2duo 2.33 GHZ to T7600G 2.66 GHZ
This BIOS update is presented in an ISO format, and may be used to create a bootable CD-ROM with all the necessary files to flash your BIOS. Apply this update ONLY if you are experiencing problems with your system.
Features and fixes in this BIOS release:
Adds support for the Intel® Core 2 Duo Processor T7600G 2.66GHz
Already tried it? Give your review.


text: Seller: *biobuddy* (19,047) 99.7% , Location: Louth, Ships to: GB, Item: 301467866300 Home About Us Payment Shipping Returns Contact Us 12V Wall Mounted Diesel Transfer Fuel Pump Kit - With Automatic Nozzle Item Description Item Description Exceptionally well priced - Top quality wall mountable 12v fuel transfer pump kit. Run straight from your car battery. Compare our package to others and you will see why we sell so many!Your kit will come complete as follows: Hose adaptors (x4) - 2 x for pump inlet / outlet; 1 x for fuel dispensing nozzle; 1 x for mesh foot filter. Hose clips (x4) Automatic fuel dispensing nozzle (Shuts off when tank is full) Mechanical fuel meter 5 meters of 20mm black reinforced PVC hose Carry Handle IP55 On/Off Switch PTFE Sealing Tape Mesh filter Crocodile battery connectors Item Specification Output 55 litres per minute Head 10.0m head / lift Power output 160w Voltage DC 12V Hose length 5.0m | 500cm | 197" | 16ft 4" (Approx) Nozzle type Automatic Connection 3/4" (20mm) connections Manufacturer Parker Part number PTP-KIT-WALL-AUTO Item Specification Other Items About Us Payment Shipping Returns Contact Us About Us Parker Products Limited is a family run business based in Lincolnshire, UK. We provide our customers with high quality products at affordable prices. We have been trading since 2002 and in this time we have gained valuable industry knowledge that enables us to be one step ahead of the competition. Customer service is a subject close to our heart and key to our success. We will endeavour to help and resolve any questions, queries or problems you have as quickly as possible. Payment Unless otherwise stated all prices shown are inclusive of VAT at the standard rate of 20%. Our VAT registration number is GB 175 8133 90. Payment can be made via PayPal, Credit or Debit card, Cheque, Postal Order or Banks Transfer. Items are only shipped once clear funds are received. Shipping All delivery prices (including those quoting free delivery) are for Zone 1 only. Surcharges will apply to all other zones (Including Northern Ireland, Islands, Highlands and parts of Scotland). If you are unsure about which zone your delivery address is then please contact us prior to purchase. Dispatch time Orders are usually dispatched within 24 hours and delivered on a "Next Working Day" service. This is not a guaranteed service and someone will be required to sign for the delivery. Requests can be made for the order to be left in a "safe place" but this is at the discretion of the driver. Timed Service Early morning (AM) and Saturday delivery options can be added for additional cost. Please contact us for more information. Collection Goods can be collected but must be a request must be made in advance. Tracking Our freight partner is FedEx UK. As soon as your order is dispatched, you will be sent an email to confirm that it's on its way. You can track your parcel here: https://www.fedexuk.net/accounts/track.aspx Damaged Good Goods arriving damaged must be reported within 24 hours of delivery. Claims made after this time will not be accepted. For more information please read the FedEx conditions of carriage which can be found here: https://www.fedex.com/gb/ukservices/services/terms.html What do I do if my item has been returned to sender? If your item was returned to sender, this means the address you have provided us was wrong or incomplete, or you did not contact the local depot in time. If you'd like us to send your item out again, you will have to pay for re-postage. Please contact us for instructions. Returns We hope you will be delighted with everything you have bought from us, but if you are unhappy with your products for any reason, you can return them to us within 14 days. Please be advised we reserve the right to refuse refunds if we feel any damage may have been caused by the customer whilst using the item. Returned items must be: new and unused resalable returned at your own cost Although it is not a requirement- we strongly suggest that all items returned are shipped using a recorded courier.It is the buyers responsibility to return all items to our warehouse. Contact Us Buyers are welcome to contact us for more information regarding this listing. This can be done by clicking the "Ask a Question" link at the bottom of this page. Shop Categories Air Compressors Chainsaws Fuel transfer Garden tools Generators Ladders Tools Water pumps Welding Machines Other items Helpful Links Add To Favourite Seller Ask Seller a Question About Us Contact Us View Feedback Visit Our Ebay Store Condition: New, Brand: Parker, Manufacturer Part Number: PFTK-12V-WALL-AUTO


text:
The Hall of Fame!
Welcome to the Icon Hall of Fame! The icons reach the Hall of Fame though popular vote and nomination, go ahead and submit your vote, we will consider every vote and icon set nominated for possible induction. You can nominate any of your favorites, from folders and storage icons to your favorite Apple icons; from cartoons and popular TV shows to music and movie icons, it's all up to you. So tell us about your favorites, we're all ears!
Apple's Top 30
Featuring 57 Icons
Around the House III
Featuring 60 Icons
Featuring 21 Icons
DigiPix (Vol. I)
Featuring 24 Icons
Super Storage
Featuring 31 Icons
Featuring 40 Icons
Apple Hardware (Vol. I)
Featuring 35 Icons
Lightbulbs Max
Featuring 48 Icons
DigiPix (Vol. II)
Featuring 32 Icons
DigiMotion (Vol. I)
Featuring 24 Icons
Solar System
Featuring 16 Icons
Auto Mechanic
Featuring 34 Icons
All icons available for Mac OS X , Windows Vista and XP.Please remember to click the "Return to Merchant" link after processing your payment through PayPal to be transported to the download zone.


text:
- Description
Product Overview:
Availability: Ships in 8 - 10 weeks Dimensions: 33"L x 26"W x 22"H Weight: 42 lbs. Assembly: Some Assembly Required Collection: Wagons & Wheelbarrows Handcrafted In: Pennsylvania, USA Shown In: Unfinished w/ wooden wheels Reviews:
This Amish-made goat wagon makes for a very unique coffee table. This beautiful home accent is not just for looks either. Remove the coffee table glass top and you have a real usable goat wagon. Designed and handcrafted by skilled Amish woodworkers, this goat wagon coffee table is built to last for many years.
This painted Amish goat wagon coffee table is available in a number of colors. Choose the color that goes best with your living room.
Height: 22"
Width: 26" (outside of wheel hubs)
Length: 33"
Tongue Length: 29"
Weight: 42 lbs.
Rear Wheel Diameter: 15"
Front Wheel Diameter: 11.5"
Interior Box: 10" x 18" x 28"
- Additional Information
Additional Information
Collection Wagons & Wheelbarrows Warranty No Assembly Some Assembly Required Handcrafted In Pennsylvania, USA Material Wood Wood No Product Dimensions 33"L x 26"W x 22"H Weight 42 Ships in 8 - 10 weeks
- Reviews
You may also be interested in the following product(s)
Amish Furniture Factory Cart Coffee TableSKU: 1700
Regular Price: $700.00
Special Price $548.00


text:
Facility & Directions
We'll be pleased to welcome your visit to our warm and comfortable offices. Pfeifer Funeral Home • 7915 East Main Street • Reynoldsburg, Ohio 43068 was designed to be unlike any funeral home you've ever seen; it's truly a one-of-a-kind place. We invite you to come in and see for yourself how we're revolutionizing the way you think about funeral service.
Pfeifer Funeral Home and Crematory
7915 East Main Street
Reynoldsburg, OH 43068
Telephone: (614) 755-9500
Email: [email protected]
Website: www.pfeiferfuneral.com
Driving Directions: Click Here


text:
I am a life-long fan of the British sci-fi TV show Doctor Who. I am slowly putting together a costume to wear to conventions that will incorporate elements of outfits from all of the regenerations of the Doctor.
I already own a scarf from the Tom Baker era and the knit jumper from the Sylvester McCoy era.
From David Tennant's years, I own a pair of red Chuck Taylor All-Star tennis shoes. I also have the blue pinstripe sportscoat and brown frock coat. Even my prescription glasses are very similar to his "brainy specs". Hell, I probably have a pair of 3-D glasses around here as well.
For this 2016 season, I am hoping to add something to my wardrobe that I have fancied since the beginning -- Colin Baker's multi-colored frock coat. This blog will catalog the work my wife and I will do to make that coat a reality. We'll discuss all of the many fabrics choices we made and where we acquired them.
Here is a list of my planned costume elements for each Doctor.
- William Hartnell - yellow pin-stripe trousers?
- Patrick Troughton - Recorder flute, bow tie
- Jon Pertwee - not sure yet
- Tom Baker - the scarf (and jelly babies?)
- Peter Davison - Shirt with ? collar, a stalk of celery
- Colin Baker - the frock coat (and maybe a cat pin?)
- Sylvester McCoy - ? knit jumper/sweater vest
- Paul McGann - pocket watch
- John Hurt (The War Doctor) - not sure yet
- Christopher Eccleston - not sure yet
- David Tennant - red Chucks, glasses
- Matt Smith - bow tie and sonic screwdriver (maybe a fez?)
- Peter Capaldi - not sure yet


text: Reid Goldsborough describe the algorithmic basis for Facebook's news feed, writing "The ever-changing algorithm behind Facebook's news feed, called EdgeRank, is … crucial in today's social media-infused world. It determines what you see when you check Facebook," … adding … "Facebook is largely mum about EdgeRank, keeping many things private for competitive reasons. But based on what is publicly known as well as EdgeRank's behavior, Facebook uses EdgeRank to help create your news feed mostly through Affinity Score, Edge Weight, and Time Decay." Goldsborough proceeds by describing Affinity Score, Edge Weight, and Time Decay in layman's terms. He also comments on the echo chamber effect of Facebook's news feed in his Information Today article. Informative. — Joe


text:
Biogen, Merck use predictive modeling to better negotiate value-based contractsAugust 15, 2017
What's holding back value-based pricing deals from moving beyond the pilot phase?
On Shkreli, Here Are the Lessons for Pharma to Learn and ApplyAugust 07, 2017
Though Shkreli may soon slip from the public eye, separated from his Twitter account and prohibited from trading securities, pharma communicators must learn from these events.
Five things for pharma marketers to know: Tuesday, July 11, 2017July 11, 2017
Trump administration considers outcomes-based approach to lower drug prices; Sanofi to acquire vaccines biotech; Nestle partners with Enterome to develop microbiome-based diagnostics
Five things for pharma marketers to know: Tuesday, May 30, 2017May 30, 2017
Harvard Pilgrim signs two outcomes contracts with AstraZeneca; lobbyists fight over drug-pricing proposals; docs say no to adult ADHD screening test
Value-based care requires innovators to challenge the status quoMay 02, 2017
Execs stressed the importance of collaboration, consumer-mindedness.
Five things for pharma marketers to know: Thursday, April 27, 2017April 27, 2017
Novartis, Kaiser, and Qualcomm partner on heart-failure pilot; Novartis and GSK disclose DTC plans; cancer-treatment hype can be negative for patients
Genentech urges broader adoption of value-based payment modelsApril 12, 2017
A study published in Health Affairs detailed an outcomes-based pilot developed by the drugmaker and Priority Health, a Michigan-based health insurer.
Pharma/Payer Collaboration: A Kumbaya Moment or a Passing Trend?February 01, 2017
The idea is that each gets some of what it needs. Payers gain some control over cost, and pharma may get to stay on formulary.
Merck and Aetna pair population health with risk-sharing in two dealsJanuary 29, 2017
But have pharma and payers learned enough from earlier pilots to make modern risk-sharing deals work?
Five things for pharma marketers to know: Wednesday, November 16, 2016November 16, 2016
The AMA votes in favor of value-based drug pricing; Amgen says insurers are balking at PCSK9 inhibitor prices; docs aren't focused on prices when prescribing
Five things for pharma marketers to know: Tuesday, June 7, 2016June 07, 2016
Gilead CEO talks drug pricing; multiple-sclerosis drugmakers study the overall cost of care; Biden launches national cancer database
Five things for pharma marketers to know: Wednesday, May 11, 2016May 11, 2016
Cigna signs value contracts for new cholesterol drugs; Yelp partners with ProPublica for hospital reviews; ad-blocking threat to digital publishers intensifies
4 Ways to Create a Sustainable Pricing ModelJanuary 27, 2016
The formula's pretty simple: Be sure you can defend your drug's value proposition, without blushing, says BioPharma Alliance's Mike Luby.
Inhaled insulin stymied by drive for valueMay 18, 2015
Experts say Afrezza's tepid launch may have more to do with value proposition than product positioning.


text:
I have been suffering the most disturbing panic and anxiety attacks along with sleepness nights for about 8 weeks. I have now been given Lorazepam to take when needed at 0.5mg.
Has anyone been prescribed Lorazepam whilst pregnant?
- Asked
- 7 Aug 2013 by joanneherit
- Updated
- 9 August 2013
- Topics
- anxiety, panic disorder, generalized anxiety disorder, lorazepam, pregnancy
Responses (2)
From what I've read, the risk is a class "D" with a high newborn withdrawl, and cleft palette deformities,I have included a link
I was taking lorezapam with each of my three pregnancies and I was taken off then and put on diazapa. this is the safest way for baby I was than slowly reduced off thw diazepam up until baby was born I was still taking 2mg when my youngest was born and he's in high school now.
Further Information
- Lorazepam Information for Consumers
- Lorazepam Information for Healthcare Professionals (includes dosage details)
- Side Effects of Lorazepam (detailed)
Search for questions
Still looking for answers? Try searching for what you seek or ask your own question.
Similar Questions
I can take over 14mg lorazepam in one day & it doesnt do anything for my anxiety.whats wrong w/me?
Posted 10 Nov 2010 • 5 answers
Lorazepam - does lorazep help for IBS?
Posted 7 Dec 2010 • 2 answers
I'm prescribed adderall klonopin and suboxone also pregnant what is your opinion on the safety?
Posted 2 May 2011 • 6 answers
Lexapro - have panic attacks and generalized anxiety most of the time. Dr.Rx'd Lorazepam 1mg x?
Posted 21 Mar 2012 • 2 answers
Lorazepam for panic disorder?
Posted 21 Jul 2018 • 0 answers


text:
Just Released: 2011 AJISS Fall Issue
The 2011 Fall issue of the American Journal of
Islamic Social Sciences (AJISS) has just been released.
Table of Contents - Editorial
IIIT Book, Azeri Translation
IIIT's publication, "Kayfa nata'amal ma' al Qur'an al Kareem"
by Muhammad al Ghazali
has been translated into the Azeri language.
The following 5 new titles and 2 new editions of IIIT publications will appear in the US in January, 2012.
IIIT and Hartford Seminary Sign MOU
IIIT Hosts Friends of IIIT Iftar/Dinner
On Friday July 22nd, IIIT celebrated the completion of its 5th annual Summer Program in Islamic Studies with the graduation of fifteen students. The program, which ran for six weeks between June 13 and July 22, included instruction in core courses such as Qur'an and Sunna, Islamic History and Civilization, Islamic Jurisprudence, Contemporary Islamic Thought, and Muslim World Affairs.
IIIT organized the first of a series of on-day seminars on American Muslim identity on Saturday, May 7th, 2011. The seminar, entitled "American Muslim Identity: Contexts, Dynamics, challenges & Prospects", brought together twenty five scholars, intellectuals, experts and community leaders from diverse academic backgrounds, professions and community organizations.
Summer Students Program 2011 Launched
IIIT launched its 5th annual Summer Students Program in Islamic Studies for graduate and senior undergraduate students on June 13, 2011. This year's program offers five core courses in Islamic studies including Quran and Sunna, Islamic History and Civilization, Contemporary Islamic Thought, Islamic Jurisprudence and Muslim World Affairs. In addition, four seminars covering Islamic Reform movements, Islamic Finance, Faith-Based Entrepreneurship and Muslim organizations will be offered.
The Valency of Victimhood
AJISS: Call for Papers
Call for Papers
Special Issue: Muslims and Political Change
Guest Editors: Dr. Malik Mufti (Tufts University )& Dr. Katherine Bullock (University of Toronto)
IIIT hosted Dr. Louay Safi, Common Word Fellow at Prince Al Waleed Bin Talal Center for Muslim Christian Understanding (ACMCU), the School of Foreign Service, Georgetown University, on Friday, May 27, 2011. Dr. Louay spoke on Christian Muslim Encounters: Conflict, Cooperation and Convergence. The presentation was based
on research work he is conducting, supported by IIIT, with the aim of producing a book manuscript before
the end of 2011.
Tel: (703) 471-1133
Fax: (703) 471-3922


text:
Earlier this summer, Rick Franzo, tall and graying, with a New York accent and a penchant for malapropisms, stood to speak at a St. Tammany Parish Council meeting. That, in itself, was not unusual — Franzo has spoken at many such public meetings, and the group he heads, the Concerned Citizens of St. Tammany, is a fixture at them.
The unusual part was what Franzo said: He offered to allow the parish's attorneys to partner with CCST in working on legal avenues to prevent a New Orleans company from drilling an oil well in the parish.
The sheer audacity of the statement — an unelected head of a citizens' group offering to let parish government aid the group — took some elected officials in the room by surprise. But Franzo's offer, and the fact that few batted an eyelash when he made it, underscored that Concerned Citizens has become a force in the parish that seemingly can mobilize its army of resident activists on behalf of any cause, no matter how large or small.
Although some parish officials privately express skepticism or even scorn for Franzo and the group, in public they are more circumspect.
To ascribe the group's rise in profile and power to any one factor would ignore the fortuitous set of circumstances that has fostered its growth from a small cadre of Lacombe residents banded together over a zoning dispute to a multifaceted organization that claims to have regular contact with the Louisiana legislative auditor, the state Inspector General's Office and the FBI.
Franzo claims that the group has more than 2,000 members, each of whom pays $25 per year in dues. It has a centralized leadership structure, with an executive board overseeing an array of issue-specific committees.
The group has its tentacles in a number of issues, none hotter in St. Tammany Parish right now than a plan by Helis Oil & Gas to drill that oil well.
If the company's project gets the go-ahead from the state, Helis plans to use a controversial method of oil extraction known as hydraulic fracturing, or fracking.
CCST decided early on to oppose Helis' plans, and the group has put its full weight into pressuring politicians and agencies as varied as the Mandeville City Council, the state's commissioner of conservation and the U.S. Army Corps of Engineers to try to block the well. The group also has shown its willingness to go to state or federal court to get its way, and Franzo has promised to take the fight against the well all the way to the U.S. Supreme Court.
A Lacombe issue
It's heady stuff for a group that didn't even exist five years ago. But in 2010, when the Parish Council rezoned a parcel of land along La. 434 near Interstate 12 to allow the construction of a waste transfer station, some residents, including Franzo, decided it was time to get off the sideline.
"We were at my house, about eight to 10 of us," Franzo recalled. Soon afterward, the group decided to hold a public meeting in Lacombe. When about 300 people showed up, Franzo knew they had tapped into a powerful vein of public discontent.
The group told those 300 that they were going to fight the plan in the courts and asked them to donate to the cause. Concerned Citizens of Lacombe hired lawyers and sued the parish and IESI, the company that planned to build the waste transfer station, alleging that the parish had erred when it issued IESI a permit for the facility. The group won in state district court, but the matter was appealed all the way to the Louisiana Supreme Court.
Before the high court could decide the case, in stepped a businessman and consultant for IESI who offered a nearby piece of land and promised to build a business park adjacent to the waste transfer station and pay $250,000 of CCL's legal bills, which by then had climbed to nearly $500,000.
Fearful of what might happen at the Supreme Court, CCL agreed to the compromise, allowing IESI to build its station on the nearby land, but not on the same site as originally planned.
"I feel that the end result is better than what could have happened," Franzo told The Times-Picayune at the time. "Is it the ideal solution? No."
After that fight, the group, still centered in Lacombe, could have faded away. But it didn't.
"During that process, we saw so many things we thought were wrong about how government operated and how it was unfair to the citizens," Franzo said in a recent interview. "We thought the only way we could change this was if we grew CCL to parishwide."
Soon, chapters were formed in Slidell, Covington and Mandeville, and the group began to get involved in municipal issues.
And then came Peter Galvan.
The longtime parish coroner was transformed from a relatively obscure public official to the poster child for wasteful spending in just a few months as media reports about his profligacy piled up. Those reports — and subsequent federal and state investigations — revealed not only that Galvan had used Coroner's Office funds to pay for lavish meals and for accessories for his boat and plane but also that he had awarded himself and other top Coroner's Office employees six-figure salaries.
The revelations disgusted members of Concerned Citizens, who launched a petition to recall Galvan, complete with signs, T-shirts and a motivated volunteer force. The recall was eventually rendered moot by Galvan's indictment and subsequent resignation and guilty plea.
The recall campaign, though ultimately unnecessary, raised CCST's profile in the parish and helped grow the membership by leaps and bounds, Franzo said. When CCST hosted the first forum for candidates to replace Galvan, several hundred people filled the John Davis Center in Lacombe to hear the four candidates address questions prepared by the group.
CCST grew so much, in fact, that Franzo decided it had sprawled out of control.
"We were turning into a bureaucracy," he said. Every chapter "had its own mail system, bank accounts, etc."
Franzo brought all of the individual chapters under a single executive committee and consolidated all the bank accounts. The group is now run by an 18-member executive committee. Franzo is the group's president, elected by the general membership to a two-year term.
Engaged but not partisan
Some of the people at the first meeting at Franzo's house — Carl Ernst, Kort Hutchison and Paula Borne among them — form the core of the CCST leadership. In a parish where being a Republican is a necessary part of any aspiring politician's résumé, those core leaders have tried to keep CCST steadfastly nonpartisan.
"This is not a Republican or Democrat or tea party organization," said Ernst, who is an advisory member of the executive committee. "This is not a political party."
The group doesn't endorse political candidates, and the leadership includes members of both major parties, Ernst said.
All the group cares about is "good governance and holding elected officials accountable," he said. "We attempt to stay out of politics."
But the group's nonpartisan nature hasn't kept it from targeting specific officials, starting with Galvan.
Councilman Marty Gould became a target of CCST's wrath for his endorsement of an Archdiocese of New Orleans development off Dove Park Road. One member of Concerned Citizens, Terri Lewis Stevens, repeatedly accused Gould of ducking questions and the Parish Council of taking advantage of residents in the area by refusing to require sufficient buffers between the development and private homes and ignoring residents' wishes.
More recently, Parish President Pat Brister and some members of the council have been targeted for special criticism because of what group members saw as their passivity in opposing the proposed oil well.
When word of Helis' plans first emerged, Brister said parish attorneys had advised her that authority to permit the well lay with state officials, and the parish was largely powerless to stop it. CCST jumped on that, accusing Brister of complicity with Edward Poitevent, who owns much of the land that Helis plans to drill, and of knowing about the plans long before they became public.
In that context, Franzo and CCST revealed a more bare-knuckled side. In a June 11 Facebook post on the CCST Facebook page, Franzo blasted Brister, calling statements she made during a radio interview "idiocies" and comparing her to a character from "Invasion of the Body Snatchers." The post has led some detractors to question the group's claim to be nonpartisan.
Success and failure
Needless to say, Brister is no fan of CCST.
"I think CCST takes credit for a lot of things that other people have been responsible for," she said in a recent interview. "I don't think they are as powerful as they think they are."
Brister pointed specifically to Galvan, whose fall she attributes more to the work of the media and the FBI than to that of Concerned Citizens. But the same media, she noted, have raised the group's profile by repeatedly seeking its input on various public matters.
Clearly, CCST has succeeded in raising its profile by cultivation of the local media. Franzo has a long list of local reporters in his Rolodex, and he is always accessible and ready to offer a sound bite for a news story. It's a symbiotic relationship — CCST members tend to be engaged, informed and often outraged; reporters are often seeking voices in their stories. Having members quoted on TV or in the newspaper helps to keep the group relevant.
Another sign of CCST's growing profile is that one of its founding members, Jake Groby, now sits on the Parish Council. The proposed oil well lies in Groby's district, and Groby, along with CCST, helped convince the other council members they needed to act.
The group also engaged the assistance of attorneys from Tulane and Loyola universities, some of whom filed for temporary restraining orders in state and federal courts to stop Helis' applications for wetlands permits. Those filings helped convince the Army Corps of Engineers to make Helis' full application available online and to extend the public comment period on it.
Not all of Concerned Citizens' efforts have met with success.
The group pushed strongly for creation of a parish inspector general, repeatedly urging a parish task force studying the issue to recommend that the Legislature create one. But the task force instead recommended only that the Legislature require "forensic audits" of parish agencies once every few years. Franzo promised CCST would act as the parish's inspector general in the absence of one created by law.
What's next?
With fracking looking to be the hottest fight in St. Tammany Parish for the foreseeable future, it's safe to say CCST's profile will remain high. The group has a team of attorneys working on its behalf and promises to fight the matter to the end.
Regardless of whether the proposed oil well is drilled or defeated, Franzo promises the group has other issues in its crosshairs, including pushing for term limits and acting as the de facto inspector general for the parish.
"We have a very close relationship with the Louisiana legislative auditor and state inspector general. We have had meetings with them to set up a fast track of information going back and forth," Franzo said.
Political consultant James Hartman, who has several clients on the north shore, has watched the group's meteoric rise from humble beginnings.
"They are increasingly powerful," said Hartman, whose company built CCST's website but no longer works for the group. "I don't think they are going away anytime soon."
Follow Faimon A. Roberts III on Twitter @faimon.


text:
The Biggest And Greatest Guide To Jewelry
What do you get out of jewelry? Can you identify the difference between costume jewelry and characteristics of different pieces? The ideas presented here will aid in the below article should be able to give you more of an understanding about the complexities of jewelry. This article will give you some great tricks for all


text:
Separate names with a comma.
Discussion in 'NDS - Flashcarts and Accessories' started by Scorpin200, Jul 10, 2007.
Does anyone know the best place to order this from?
DealExtreme, there's a link in my signature
- Sam
you can get a tri-wing screwdriver to open your nintendo consoles from ncsx.com, considering that you're located here in the states. here's a link:
Yeah i was looking for the best , because usually that's the fastest since my top ds screen is messed up maybe i can fix it.
Sam got it right. 2.00USD for a triwing and a phillips head. I ordered it and they work on a DSL. Sam's sig has a link
Damnit i can't order from that place why the hell can't the accept payment the normal way?
Divineo.cn was where I got mine from, was cheap as chips for shipping and came within 4 days


text:
Dharmo rakshati rakshitaha.
One who destroys Righteousness is destroyed by the very force of Righteousness, and One who protects Righteousness is protected by it.
Westerners quoted it as "You get what you give, whether it's bad or good".
Read, Why Ramayana and Mahabharata are so popular among Indians?
Why Good always triumphs over Evil?


text:
33' Houseboat Christmas/New Year period
- Product code: 33HPeak
The 33' houseboat can accommodate up to 4 people.
Any hires up to 7 days, containing these dates, can be booked here.
The Myall Lakes are the largest freshwater lake system on the Eastern Seaboard of Australia. All our houseboats are fully equipped and boast spacious sundecks. Each has a stainless steel BBQ, 4 burner gas stove, oven and grill, 12v frige/freezer and a large esky.
The Myall lakes have numerous public moorings and countless sandy bottomed areas for anchoring and swimming.
A fee of $25.00 per motoring hour applies to cover the cost of servicing, replacing motors and fuel usage.
Past hires have produced an average of 2-3 motoring hours per day. There are no other costs.
A full list of inventory can be found on the website.
Supplied on board includes all your crockery, cutlery and cooking utensils. It will be necessary for you to bring your own food, drinks, towels and personal belongings. There is a doona and pillows for each bed and one double will be made including sheets. Extra sheets are available for hire at $10 per bed. Towels are available for hire at $5 each.


text:
Chronic inflammation is considered to be the most lethal disease of these modern times, such as Alzheimer's diabetes, heart problems, stroke and cancer.
This is mostly due to the inflammatory ingredients that are contained in the foods.
Here is a list of 6 foods that contain the most inflammatory ingredients:
1. White bread
The refined carbohydrates, which are contained in huge amounts in white bread, are instantly transformed in glucose in the body. As a result of this, the level of insulin is increased and it leads to inflammation.
The Journal of Nutrition published the results of a study from 2012, which showed that the inflammation can be reduced by consuming whole grain bread.
2. Cow's Milk
It is abundant in proteins and lactose, which makes it the most inflammatory food. On the other hand, skimming increases the inflammatory properties of milk, and it is not helpful at all.
3. Fried Foods
Inflammation can appear as a result of formation of advanced glycation end products, which is caused by high temperatures. The inflammation is a result of an infection in the body.
4. Vegetable Oil
Omega-6 fatty acids are the main culprit for inflammation, and they are contained in vegetable oils such as soy, corn and sunflower. So replace these oils with olive oil, which is rich in omega-3 fatty acids.
5. Alcohol
The liver cells can be damaged by the toxins that are created in the process of breaking down the consumed alcohol.
6. The Three 'Ps'
The term three 'Ps' is used for prepared, packaged and processed food, and it was invented by Michelle Schoffro. All these foods have strong inflammatory properties, and you should not consume any of them and also avoid processed cheese, cereals, candy and soda.
Just a few simple changes in your diet, will improve your health and it will reduce the risk of inflammation.
Here are some more advices from David in his video:
Source: www.davidwolfe.com
Journal of Nutrition
Women's Health Magazine
Medical News Today
Wall Street Journal
Featured image source: www.davidwolfe.com


text:
Versatile and innovative managed IT support services for growing businesses
The Network Overdrive team offer IT managed support to mid-sized and growing enterprises throughout Australia. From day-to-day running of operations through to
We can provide onsite IT support in Melbourne, Sydney, Brisbane, Adelaide and Perth and other locations in regional Victoria. In other locations, we can provide fast remote support.
When should you switch Managed IT Service Providers? When you hit the glass ceiling.
Partnering with Network Overdrive means:
- Fast and friendly onsite. phone and remote managed IT support
- Fixed priced agreements for IT managed services
- Professional and ethical advice
- Business orientated IT outcomes
Browse our IT Managed Services, Melbourne, Australia:
Strategic Alignment of I.T.
Where I.T. services meets sustainable business goals.Visit page
Service Desk Support
Standard 9 hours x 5 days customer support for your peace of mind.Visit page
Hardware & Software Management
Complete system management – predictable, fast, flexible and efficient.Visit page
Vendor Management
A range of prompt services, including hardware replacement/repair.Visit page
Software Deployment and Support
Fully tailored solutions to meet your business needs.Visit page
Healthcare IT Support
I.T. services expertly matched to the healthcare industry.Visit page
Internet Access and Voice Management
Reliable, dependable systems backed up by on-the-ball supportVisit page
Messaging and Email Services
Communication done rightVisit page
Network Monitoring and Remediation
We keep our eyes on the ballVisit page


text:
A charming smallish city in the south of Hungary, Pecs has a long and exciting history. With a Mediterranean climate and a reputation for producing good wines in surrounding regions, Pecs is an interesting place in which to spend a bit of time.
First settled by Celts about 2,000 years ago, it soon became a Roman bastion, and one of its historical sites, the Necropolis of Sopianae, is the largest early Christian burial chamber to be found outside of Italy.
Not that many people travel all the way to Pecs just for the sheer joy of visiting an ancient necropolis, of course.
Located near the border with Croatia, Pecs is part of the Mecsek Mountains and is quite a hilly city in some areas. It is not unusual for many of the households to grow grapes from which they make their own homemade wine, although the nearby Villany region also has a great reputation for the quality of its wines.
The city is also well known for its sparkling wines and at the Pannonia wine making facility, which is the best known label, visitors are invited to inspect the five underground levels of cellars and caves.
As well, there is a brewery there called Pecsi Sorfozde which produces a beer that can only be bought at a single outlet.
The town has a somewhat chequered history, but essentially it is a university city, and has been so since 1367. It still has a large student population, and places where students congregate usually means that accommodation prices are reasonable, and there is an active nightlife.
Lined by fashionable shops, restaurants and outdoor cafés, Király Street in the city's centre is always popular. This is the city's most beautiful pedestrian precinct. Many baroque-style buildings, including a church, a former monastery and Pécs's National Theater are all located here. The Hungarian Art Nouveau-style Palatinus Hotel, built in 1914, stands out from the many Baroque buildings.
To get there, Pecs is well serviced by rail services with direct trains to Budapest and Vienna and also to Coratia and Bosnia.


text:
Breaking the 35 Plateau In Church Revitalization. Today in the United States and Canada there are over 100,000 Protestant congregations that average less than thirty-five in the main weekly worship services. The small church represents twenty-five percent of all churches.. There are at least fiftee
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


text:
sunbonnet- hazel
$23.40 / On Sale
—40 % off—
the wolfechild sunbonnet in floral cotton lawn is fully lined in super soft cotton and has a tie closure under chin.
composition: 100% cotton
machine washable
originally: $39.00
now: $23.40
all sale items are final sale
please note: we have shortened our lead time. Each garment is skillful constructed by hand will ship within 7 days.


text:
"This Valentine's Day, Be Kiss-Ready," says this ad for Nivea Lip Moisturizers. The image shows a woman at a window. On the other side of the window is her love, whose teenage-fuzz mustache makes him look all of 16-years-old.
Maybe this is another case of "hot for teacher." Maybe she's his mom. Maybe they should have considered their choice of models more carefully.
By Marc Librescu