4.2.2 Patch for various Nominate This optimizations and JS Patches

This patch resolves a number of issues revealed through optimizations in the earlier 4.2.1 release.

Significant optimizations were added to the Nominate This process in order to accelerate the processing of readability and saving items to the database. Duplicated functions, flaws, and inefficiencies created through multiple user nominations of the same content were repaired and a number of user permission level conflicts were resolved.

Props for contributions from @mAAdhaTTah

Changelog:

• Moved the initiation of the REST endpoints to become more aware of the overall REST system and what has been initiated. This should do a better job of preventing initiation of REST endpoints without the supporting classes.
• Moved the image upload process in Nominate This to the end of the Nomination/Post process, this means less chance of a failed initiation of the bookmarklet.
• The addition of the Source statement at the end of a Draft or Post now occurs only when an item has been sent to Publish/Draft from Nomination or Nominate This, simplifying the process and eliminating an edge case in which the source statement might show twice.
• PHP formatting was brought in line with WordPress standards.
• Removed revisions from the Nomination Post Type as they are completely unneeded and creating additional database rows.
• Removed a flaw in the setup of the HTTPTools class
• Assure the PF JS is active on all PF Pages.
• Removed a duplicated post status declaration.
• Terminate some hanging processes.
• Remove old versions of author meta.
• Update WPUpdatePHP
• Set up a standalone permission for the Nominate This bookmarklet.
• Set up better messages for permission failures in the Nominate This bookmarklet.
• Attach correct permissions to various Nominate This actions.
• Assure that when a Nomination hits Publish/Draft it is given the permissions to match the user who sent it to the last step, not the nominating user.

4.2.2 patch Release Candidate 1

Significant performance and bugfixes.

4.2.1 Release

Announcing the Addition of PressForward API Endpoints in 4.2

In PressForward 4.1 we announced the first step toward a set of PressForward API endpoints in conjunction with the WP-API. In 4.1 we added PressForward metadata to the post endpoint and today we’re excited to announce the addition of several new endpoints that expose PressForward metadata about feed items, feeds, and folders.

As we previously described, WordPress is moving toward integrating a RESTful API into its core. The API will “expose,” in a clearly defined and secure way, certain internal functions and data so that developers can use them in their own applications or websites. We’ll post more later about what the API means for our users and how you can activate and use the API on your site. In the meantime, you can read about how WordPress is moving towards becoming an application framework, and what that means, on the WP-API website.

New Endpoints

The most significant change in version 4.2 is the addition of a PressForward endpoint on the WP-API. PressForward now has a dedicated REST endpoint at wp-json/pf/v1. Feeds, feed items, and folders can all be accessed (as resources) through this new endpoint. Additionally the status of PressForward, including version and active modules is available at /wp-json/pf/v1/status. Users can utilize the API response to programmatically sort, filter, and view information about the content retrieved by a PressForward installation. The feed items resource contains metadata such as item date, item author, the original item link, and the date the item is retrieved, the id of the feed it was retrieved from, as well as the word count. The feed resource contains information about the feed such as title, link, the date last retrieved and which folders, if any, the feed belongs to.

Performance Enhancements

In addition, version 4.2 also includes several significant performance optimizations. Updates to an outdated jQuery library will increase the responsive speed of the user interface. Enhancements to the retrieval code and the post delete process will increase performance and lead to a slimmer overall database.

A list of all the changes in 4.2 can be found on our GitHub milestone.

Changelog

Features:

• Added feeds, feed items, and folders to the PressForward endpoint.
• Optimized the the retrieval code.
• Updated jQuery library and switched from jQuery Toggle to Click.
• Enhancements to the post delete function.
• Optimized overall Javascript features.
• Optimized old item deletion.
• Readability library optimized and cleaned for general release.
• Improved relationship table install and check process.
• PressForward post meta keys are now registered with WordPress Core functions.
• Assured compatibility with 4.7
• Optimized item link tracking for published posts.
• Added additional checks for keywords to add to the tags in the Nominate This bookmarklet.

Bug Fixes:

• Fixed a bug that prevented the bookmarklet from retrieving tags
• Fixed an issue that caused the interface to stop functioning on Windows 8 touch screens.
• Wordcounts recorded in post metadata are now accurate.
• Fixed a conflict between PressForward and Jetpack.
• Repaired broken unit test methodology.
• A more useful error when Nominate This can’t add a post to the database.

4.2.1 Release Candidate

4.2.1-RC1

Uptick version to 4.2.1

Further PHP back-compatible fixes

4.1.2

Update pressforward.php

Bugfix for php 5.4 issues

4.1.1

Update version number

4.1.0

Announcing the Addition of PressForward Data to the WP API with PressForward 4.1

Today the PressForward team is pleased to announce the release of PressForward 4.1, an update to our WordPress plugin that enables the aggregation of RSS / ATOM feeds and the curation of web publications. Version 4.1 of PressForward serves as the first step toward the release of a complete PressForward Application Programming Interface (API).

The most notable new feature of 4.1 is the addition of PressForward metadata to the WordPress API’s post endpoint. WordPress is in the process of moving toward becoming a application framework and the REST API allows users to make their site data available in a JSON format. Among the information included in this format is information about users, posts, and taxonomies. All of this information can be accessed with a HTTP request. For more information on the WordPress API as well as instructions on how to install and activate it, see the WP REST API documentation.

When complete, the PressForward API will introduce a number of performance enhancements for users. By moving toward API responses rather than AJAX responses and formalizing the code structure, the system will be faster and more responsive. Further, the API will allow the full range of data associated with PressForward posts, nominations, feeds, and items, to be easily integrated and extended by other tools.

PressForward 4.1, our first step toward a fully functional PressForward API, adds PressForward metadata to the WP API post endpoint. Users will now see PressForward metadata attached to the Post endpoint for any post that is drafted using PressForward. The post endpoint will include metadata such as: item date, item author, item link, the date the item was retrieved, as well as the wordcount. A full list of fields available on the Post endpoint can be found in the API documentation. In addition to the post endpoint, 4.1 also adds endpoints for feeds and folders. However, feed and folder endpoints have not been completed and should be considered only within the context of the post endpoint. Developers should not consider those API locations final.

Another improvement in 4.2 is an upgrade to the Readability library, which improves the Nominate This bookmarklet and other areas where they see the full text of an article. In this release users will see that the full text of articles is found more consistently, the content of the article is more complete, and previously missing blocks of reference links are now included.

Changelog:

Features:

• Added PressForward data to the WP-API post endpoint.
• Drastically decreased PressForward’s potential impact on overall site queries.

Bug Fixes:

• Fixes a bug where servers without cURL would fail to load pages or Nominate This.
• Fixed bug that prevented Project MUSE RSS feeds from loading.
• Assured that readability catches all content on sites where the “div” structure is unclear.
• Fixed a bug that broke the outbound OPML link
• Assured that editing a folder does not redirect users to Post Categories in the WordPress menu
• Fixed a bug that caused large OPML subscriptions to trigger an error
• Assure that readability is catching content in the references block

4.0.4 - Remove cURL code causing some servers to crash

4.0.35

Patch user nom-count

4.0.4 - Remove cURL code causing some servers to crash

Also problems with lower PHP versions.

4.0.3 - OG and cURL hotfix

Patch should resolve #814