[{"name":"PlatiOnline Payments","slug":"plationline","version":"6.3.2","author":"PlatiOnline","author_profile":"https://profiles.wordpress.org/adrianpo/","requires":"5.0","tested":"6.6.2","requires_php":"5.5.0","requires_plugins":[],"rating":100,"ratings":{"1":0,"2":0,"3":0,"4":0,"5":2},"num_ratings":2,"support_threads":0,"support_threads_resolved":0,"downloaded":12946,"last_updated":"2024-07-23 1:52pm GMT","added":"2018-06-14","homepage":"https://plati.online","sections":{"description":"

Overview

Since 2002 PlatiOnline has been one of the most efficient, cost-effective and secure Integrated Online Payments Processing Platforms for online businesses for Romanian ecommerce region. Our cloud-based integrated online payment management system provides a fast, reliable and secure trading platform which offers both dedicated online management solutions for bank payment card and alternative online payment operations as well as customized reporting for online businesses.

PlatiOnline payment for Woocommerce allows online merchants to accept Visa, Visa Electron, MasterCard and Maestro, directly on their Woocommerce store via PlatiOnline’s API. First, you need to create a PlatiOnline merchant account to receive payment through PlatiOnline, then, you need to connect your PlatiOnline merchant account with your Woocommerce store through an API keys.

PlatiOnline will charge a fee for each authorized transaction. To see specific pricing and offers please fill out the online form. PlatiOnline will wire the settled amount to the merchant’s account on a weekly bases.

Summary of services

PlatiOnline integrated e-commerce merchant services include:
\n* Online interface with full-service management and reporting platform for online sales;
\n* EU companies registered;
\n* Multicurrency accounts EUR, USD and RON;
\n* SEPA payments;
\n* 3D secure standards (MasterCard SecureCode and Verified by Visa) reliable and secure online payment processing solutions;
\n* CVV2/CVC2 verification;
\n* proprietary powerful anti fraud engine PlatiOnline Argus;
\n* PCI DSS Level 1 – Merchant Services Provider certification;
\n* SSL Extended Validation (Secure Socket Layer) security certificates;
\n* PayLink & PayButton Options – fast & simple payment link creation directly from our platform/ideal for easy integration of payment buttons on any website and/or for push marketing campaign messaging;
\n* online credit card instalments with zero interest;
\n* recurring card payments;
\n* one click login and pay card payments;
\n* bank transfer processing and settlement by PlatiOnline;
\n* offline cash collection at Romanian Post Office & Raiffeisen Bank branches;

Summary of features

PlatiOnline transactions features include:
\n* Authorization only: Payment info is sent to customer’s bank to check the owner and available fund on card. The fund is kept on customer’s bank account until merchants make a request to receive payment.
\n* Capture (Authorized transactions): Once funds are authorized, merchants can capture their money using the online interface.
\n* Sale – (Authorization & Capture): The same as Authorize only, but customer’s money will be transferred immediately to merchant’s bank account so they do not to wait or capture it manually.
\n* Void: After the payment has been authorized, merchants can directly void the payment using the online interface so it will be released and not captured.
\n* Refund full and partial: Merchants can refund to customers from online interface, ensuring customers will get money back.

Highly secured payment technologies

PlatiOnline payment system is committed to protecting customer information and to actively combat fraud. Development of the PlatiOnline payment platform started in May 2002 with the mission to provide secure and reliable payment solutions for online merchants and their customers worldwide.

Based on our extensive experience in the field of anti-fraud protection, PlatiOnline developed the ARGUS online fraud detection and prevention system, which is permanently updated and optimized using machine learning algorithms.

Our advanced anti-fraud system ARGUS use algorithms so that the risk of rejecting valid orders due to the emergence of imperfect anti-fraud protection is almost completely eliminated.

Worry-free shopping

PlatiOnline has the highest level of PCI DSS certification (Level 1 PCI DSS on-site). This means outsourcing processing tasks to PlatiOnline system would reduce most of the PCI DSS scope for merchants. PlatiOnline is hosting the credit card page over SSL secure connection, so the merchants have no worry about cardholder data.

CVV2/CVC2 online verification

To protect merchants from payments made by fake cards or invalid cards, PlatiOnline will stop payments when the CVV2/CVC2 of a card fails to pass the verification process.

3D secure standards

Verified By Visa and MasterCard SecureCode offer the cardholder the ability to set up and use a personal/random password that will confirm his identity and protect his card data against fraudulent use. That’s why 3D systems are security signs for merchants and issuing banks that the user of that card is also the right holder of the card.
\nPlatiOnline Merchant Account have 3 options:
\n* Optional 3D Secure: performs 3D Secure test when it is supported by bank. If 3D Secure is not supported, the card will still be charged as usual;
\n* Required 3D Secure: always check for 3D Secure and stop the payment if it is not supported;
\n* Off: disable checking for 3D Secure support.

\n","installation":"

Minimum Requirements

PHP version 5.5 or greater (PHP 7.4 or greater is recommended)
MySQL version 5.0 or greater (MySQL 5.6 or greater is recommended)
cURL version 7.29.0 or greater
Woocommerce 3.0.4 or greater
SOAP extension enabled
cURL extension enabled
OpenSSL version 1.0.1 or greater

Automatic installation

Automatic installation is the easiest option as WordPress handles the file transfers itself and you don’t need to leave your web browser. To do an automatic install of PlatiOnline, log in to your WordPress dashboard, navigate to the Plugins menu and click Add New.

In the search field type PlatiOnline and click Search Plugins. Once you’ve found our payment plugin you can view details about it such as the point release, rating and description. Most importantly of course, you can install it by simply clicking “Install Now”.

Manual installation

The manual installation method involves downloading our payment plugin and uploading it to your webserver via your favourite FTP application. The WordPress codex contains instructions on how to do this here.

Updating

Automatic updates should work like a charm; as always though, ensure you backup your site just in case.

\n","faq":"\n

\nWhere can I get support for installing and configuring the plugin?\n\n

For help, please send an email to adrian[at]plationline[dot]eu

\n\n","changelog":"

6.3.2

fix Woocommerce Subscriptions subscription ITSN status

6.3.1

fix woocommerce subscriptions status after payment
added woocommerce_order_received_verify_known_shoppers

6.3.0

implemented additional PlatiOnline payment method
Woocommerce HPOS support
updated schemas url

6.2.12

fix for plationline_email_payment_link and plationline_email_payment_link_format_string

6.2.11

fix for plationline_email_payment_link

6.2.10

added plationline_email_payment_link to show retry payment button in email via order note
updated woocommerce subscriptions renewal order management

6.2.9

added plationline_email_payment_link to show retry payment button in email

6.2.8

mark orders paid if status is po-incasare or po-incasata

6.2.7

added yearly recurrence

6.2.6

Woocommerce Subscriptions payment response update custom order status
Woocommerce Subscriptions additional verifications
mark orders paid if status is po-autorizata
added processing order status in plugin admin

6.2.5

Woocommerce Subscriptions update status for subscription after onhold
filter payment gateways for recurrence
added admin notice if woocommerce is not active

6.2.4

Woocommerce Subscriptions cancel subscription on Master Transaction Recurrence cancel

6.2.3

fix ITSN for payment links

6.2.2

fix reccurence available payment gateways filter
set subscription end date to 2 years if not set
update subscription next payment and end date if payment is demoted to one time payment

6.2.1

fix subscription on-hold if payment is declined

6.2.0

added support for Woocommerce Subscriptions

6.1.3

added cancel recurrence option in admin

6.1.2

get order fees and send them as discount or additional cost

6.1.1

send processing email when status changed from authorized to processing
update coupon usage counts on authorized status

6.1.0

implemented recurring payments
added Plati.Online order status history check for authorized transactions
fixed stock reduce or increase based on PlatiOnline transaction status
added confirmation to Plati.Online remote actions
added expiration days for payment links
added option to disable retry failed payment if any product is out of stock on customer order page
relay response page can now use order-received page if empty string or custom URL using our shortcode
prevent order status update to Pending Settle or Settled if current status is Completed
fallback language sent to Plati.Online to English if website language not supported
fixes to login with Plati.Online
added settings link

6.0.14

fix reduce stock levels ITSN
updated Login with Plati.Online

6.0.13

fix currency code sent to PlatiOnline for multicurrency shops

6.0.12

fix plugin deactivation if Woocommerce not detected

6.0.11

fix plugin deactivation if Woocommerce not detected

6.0.10

fix customer new order email

6.0.9

added Posta Romana payment method
added retry payment option for declined/error orders

6.0.8

tracking script minor glitch fix

6.0.7

login with Plati.Online payment token
select authorized status for order: PO Authorized/Completed
added JS Tracking script for PTOR relay method and authorized status
fixed some translations

6.0.6

fixed schema validation
fixed firstname and lastname if they are sent in 1 field

6.0.5

fixed some links

6.0.4

fix update

6.0.3

fix update

6.0.2

fix update

6.0.1

fix readme

6.0.0

6.0.0 is the initial release. Make a full site backup before installing the plugin

\n","screenshots":"

$\"PlatiOnline$
PlatiOnline admin setup interface
$\"PlatiOnline$
PlatiOnline payment method selection
$\"Login$
Login with Plati.Online

"},"short_description":"Overview","download_link":"https://downloads.wordpress.org/plugin/plationline.6.3.2.zip","screenshots":{"1":{"src":"https://ps.w.org/plationline/assets/screenshot-1.png?rev=1892754","caption":"PlatiOnline admin setup interface"},"2":{"src":"https://ps.w.org/plationline/assets/screenshot-2.png?rev=1892754","caption":"PlatiOnline payment method selection"},"3":{"src":"https://ps.w.org/plationline/assets/screenshot-3.png?rev=1892754","caption":"Login with Plati.Online"}},"tags":{"e-commerce":"e-commerce","ecommerce":"ecommerce","sales":"sales","sell":"sell","store":"store"},"versions":{"6.0.0":"https://downloads.wordpress.org/plugin/plationline.6.0.0.zip","6.0.1":"https://downloads.wordpress.org/plugin/plationline.6.0.1.zip","6.0.10":"https://downloads.wordpress.org/plugin/plationline.6.0.10.zip","6.0.11":"https://downloads.wordpress.org/plugin/plationline.6.0.11.zip","6.0.12":"https://downloads.wordpress.org/plugin/plationline.6.0.12.zip","6.0.13":"https://downloads.wordpress.org/plugin/plationline.6.0.13.zip","6.0.14":"https://downloads.wordpress.org/plugin/plationline.6.0.14.zip","6.0.2":"https://downloads.wordpress.org/plugin/plationline.6.0.2.zip","6.0.4":"https://downloads.wordpress.org/plugin/plationline.6.0.4.zip","6.0.5":"https://downloads.wordpress.org/plugin/plationline.6.0.5.zip","6.0.6":"https://downloads.wordpress.org/plugin/plationline.6.0.6.zip","6.0.7":"https://downloads.wordpress.org/plugin/plationline.6.0.7.zip","6.0.8":"https://downloads.wordpress.org/plugin/plationline.6.0.8.zip","6.0.9":"https://downloads.wordpress.org/plugin/plationline.6.0.9.zip","6.1.0":"https://downloads.wordpress.org/plugin/plationline.6.1.0.zip","6.1.1":"https://downloads.wordpress.org/plugin/plationline.6.1.1.zip","6.1.2":"https://downloads.wordpress.org/plugin/plationline.6.1.2.zip","6.1.3":"https://downloads.wordpress.org/plugin/plationline.6.1.3.zip","6.2.0":"https://downloads.wordpress.org/plugin/plationline.6.2.0.zip","6.2.1":"https://downloads.wordpress.org/plugin/plationline.6.2.1.zip","6.2.10":"https://downloads.wordpress.org/plugin/plationline.6.2.10.zip","6.2.11":"https://downloads.wordpress.org/plugin/plationline.6.2.11.zip","6.2.12":"https://downloads.wordpress.org/plugin/plationline.6.2.12.zip","6.2.2":"https://downloads.wordpress.org/plugin/plationline.6.2.2.zip","6.2.3":"https://downloads.wordpress.org/plugin/plationline.6.2.3.zip","6.2.4":"https://downloads.wordpress.org/plugin/plationline.6.2.4.zip","6.2.5":"https://downloads.wordpress.org/plugin/plationline.6.2.5.zip","6.2.6":"https://downloads.wordpress.org/plugin/plationline.6.2.6.zip","6.2.7":"https://downloads.wordpress.org/plugin/plationline.6.2.7.zip","6.2.8":"https://downloads.wordpress.org/plugin/plationline.6.2.8.zip","6.2.9":"https://downloads.wordpress.org/plugin/plationline.6.2.9.zip","6.3.0":"https://downloads.wordpress.org/plugin/plationline.6.3.0.zip","6.3.1":"https://downloads.wordpress.org/plugin/plationline.6.3.1.zip","6.3.2":"https://downloads.wordpress.org/plugin/plationline.6.3.2.zip","trunk":"https://downloads.wordpress.org/plugin/plationline.zip"},"donate_link":"","icons":{"1x":"https://ps.w.org/plationline/assets/icon-128x128.jpg?rev=1892980","2x":"https://ps.w.org/plationline/assets/icon-256x256.jpg?rev=1892980"}},{"name":"lazysizes","slug":"lazysizes","version":"1.3.3","author":"Patrick Sletvold","author_profile":"https://profiles.wordpress.org/16patsle/","requires":"3.9","tested":"5.5.15","requires_php":"5.6","requires_plugins":[],"rating":100,"ratings":{"1":0,"2":0,"3":0,"4":0,"5":6},"num_ratings":6,"support_threads":0,"support_threads_resolved":0,"downloaded":16801,"last_updated":"2020-08-13 10:19am GMT","added":"2017-11-02","homepage":"http://wordpress.org/plugins/lazysizes/","sections":{"description":"

lazysizes is a WordPress plugin for the high performance, SEO-friendly and auto-triggering lazyloader with the same name. Support includes images (including responsive images with srcset and the picture tag), iframes, scripts/widgets and much more. It also prioritizes resources by differentiating between crucial in view and near view elements to make perceived performance even faster. Additionally, you can add low-res/blurry placeholder images using the Blurhash algorithm.

This plugin works by loading the lazysizes script and replacing the src and srcset attributes with data-src and data-srcset on the front end of a WordPress site. When a post or page is loaded, the lazysizes javascript will load the images, iframes etc. dynamically when needed. All you need to do is to enable the plugin, and possibly tweak a few settings to your liking.

Thanks to aFarkas and contributors for making the lazysizes library possible, and for letting me use the same name.

Also thanks to dbhynds who made the Lazy Load XT plugin, which this plugin is based on.

\n","faq":"\n

\nWhy aren’t my images lazy loading?\n

Lazysizes filters images added to the page using the_content, post_thumbnail_html, widget_text and get_avatar. If your images are added using another function (wp_get_attachment_image for example), lazysizes does not filter them by default. There are several options for changing what lazysizes filters, like enabling it to filter acf_the_content for WYSIWYG content from Advanced Custom Fields, and enabling wp_get_attachment_image support (somewhat limited, see below). For unsupported use cases you can also filter the HTML yourself by passing it to get_lazysizes_html.

While this plugin has opt-in support for wp_get_attachment_image, it doesn’t add a no-Javascript fallback, which causes images to become invisible for users where Javascript is disabled or unsupported. We cannot fix this for you automatically, but you can fix this with a couple of changes to the code that uses wp_get_attachment_image. For example, if a theme has: echo wp_get_attachment_image($id);, changing it to the following would lazy load the image and add no-Javascript fallback if enabled in settings: echo get_lazysizes_html( wp_get_attachment_image($id) );

If a popular plugin is incompatible and has a filter for modifying the HTML output, lazysizes could most likely get support for that plugin. In that case, feel free to ask! If the plugin has no such way to filter the output, they would have to add one for lazysizes to leverage.

\nWhat is the Blurhash placeholder feature, and how do I use it?\n

The low-res Blurhash placeholder feature generates a text string for each image using the Blurhash algorithm. This string includes all the information necessary for the Blurhash script running in the visitor’s browser to decode it into a blurry image, which will be shown while the real image is loading.

Because the final image placeholder is generated in JavaScript, users on faster internet connections can sometimes see the full image directly for images that are above the fold. Images lower down on the page will have a placeholder ready by the time the user reaches them.

The placeholder Blurhash string is not computed on page load, as it can in some cases take several seconds to do so. Instead, it will need to be pregenerated. As long as Blurhash is enabled in the settings, all new images uploaded will have a Blurhash string generated automatically. Additionally, you can manage the Blurhash string for each attachment individually in the Media Library. There is an option to generate and store Blurhash strings on page load, which can be used to easily generate Blurhash strings for lots of images by visiting the page they’re shown on. Just remember to turn that option back off, or your visitors may be slightly upset.

For technical reasons, Blurhash is only supported for local image attachments, and at the moment is not officially supported for picture elements. Images without a Blurhash string will behave just like they do with the option turned off. Blurhash placeholders work with the existing effects, like fade-in, but in some cases the perfect fade-in effect may not be possible. The Blurhash placeholder will still fade in, but it might not fade when transitioning to the full image. This is because of a few edge cases not supported by the advanced Blurhash reveal effect.

The advanced Blurhash reveal effect works by creating an additional image element positioned under the regular image. This gives the best result in combination with the fade effect, but might not support all WordPress themes. Safeguards exist to prevent using the advanced effect when not supported (by falling back to the slightly imperfect fade effect), but in some cases problems may still occur. If you see this type of problem, you can disable the advanced Blurhash reveal effect in the settings. Feel free to contact me on the support forums, and I may be able to work out what was going wrong.

\nThere’s a plugin called Lazy Load XT. Why does this one look a bit similar?\n

The PHP code for this plugin was originally based on that of Lazy Load XT, with many changes since. The main difference is that this plugin is using a completely different lazy loading library (lazysizes), with no jQuery dependency. Additionally, this plugin is actively maintained and has advanced features like Blurhash support.

Thanks to dbhynds for making the Lazy Load XT plugin. Without that project, this one would not be possible.

\nWhy is this plugin called lazysizes, the same as the JS library it uses?\n

There are a few reasons:

I like the name name.
It is a fitting name, as it makes you think of lazy loading.
I’m hoping it will help people discover the plugin. I originally tried searching for a WordPress plugin using the library myself, and other people might be trying the same.

This plugin is not affiliated with the lazysizes project, but I asked for, and got, permission by aFarkas to use the name. That’s as far as any connection between the two go.

\n\n","changelog":"

1.3.3

Add support for WordPress 5.5 and native lazy loading (see point below).
Add option for full native lazyloading, which gives the browser full control over when to load the image. Not compatible with the old native lazy load option, which only gives the browser partial control over loading. Currently only supports images, other elements will be lazyloaded like previously.
Add support for transforming HTML using single quotes instead of double quotes for attributes.
Fix lazy loading for commenter avatars. This feature had actually been disabled for a while, because it was broken. The new support for single quote attributes fixes this.
Fix positioning of the blurhash placeholder when the image is directly inside a link element.
Fix Blurhash integration in the Media Library being incompatible with certain other plugins extending this area using JS. This mainly fixes compatibility with the plugin Smush, but should make other plugins more likely to work as well.
Fix incompatibilities with certain older versions of WordPress. Please note that it is always recommended to use the latest version of WordPress, and that the next major version of this plugin will require a more up to date WordPress installation than it does now.

1.3.2

A partial deploy caused by human error led to a fatal error due to missing files for versions v.1.3.0 and v1.3.1. This has been fixed, along with the following:

Fix warning caused by missing check for metadata existing.
Fix script for the attachment page being minified even when SCRIPT_DEBUG is true.
Properly implement Blurhash management support in the post editor.
Fix non-existent CSS stylesheet being enqueued when no lazy load effect was selected.
Improve logic for finding attachment id from an image url.
Fix issue with minified lazysizes script.

1.3.0

Note that this is the last release that will support PHP 5.6 and WordPress 3.9. The next release will most likely require PHP 7.2 and WordPress 4.5 or newer.

Add support for generating low-res placeholder images using Blurhash, which stores the placeholder as a short text string. Computing this string does not happen on page load, as it’s rather expensive, but when the blurhash placeholder option is enabled it can be controlled individually for each attachment, and new attachments will have a placeholder generated automatically. For more information, see the FAQ and the settings page.
Add custom lazysizes script and styles feature, which uses scripts and styles optimized for size and fewer requests.
Improve aspectratio calculation. Local images no longer need both width and height set, only one of them, since the aspect ratio can be calculated based on attachment metadata.
Various performance tweaks.
Add experimental option for skipping adding a src attribute to images, and letting the browser load the image progressively instead.
Fix issue where a picture element with an excluded class could still be lazy loaded.
Upgrade lazysizes library to 5.2.2.

1.2.1

Improve logic for skipping transforming images inside noscript tags. Should fix compatibility issues with Envira Gallery’s noscript fallback. Thanks to snippet24 for reporting.
Fix default options not being selected. If you were affected by this bug, see a list of recommended default options here. Thanks to snippet24 for reporting.

1.2.0

Upgrade lazysizes library to version 5.2.0.
Add opt-in support for Advanced Custom Fields.
The plugin now uses namespaces for PHP classes.
Confirmed working with WordPress 5.3 and PHP 7.4.

1.1.0

Upgrade lazysizes library to version 5.0.0.
Add experimental support for native lazy loading.
Fix fatal error during ajax processing. Thanks to @eastgate for reporting.
Fix PHP warning on certain pages, like the events page from the plugin The Events Calendar. Thanks @julian_wave for reporting.

1.0.0

Big thanks to martychc23 and dutze for their help and patience in making this release as good as it is.

Proper support for the picture tag, by popular request. Big refactoring of the HTML transforming code was done to make picture element support possible.
Improve and fix support for audio/video elements. The plugin now handles the preload attribute and leaves the src attribute alone on source elements inside video/audio.
Opt-in support for get_attachment_image. Please note that the plugin cannot add a no-js fallback for images lazy-loaded using this method.
Add option to enable/disable noscript fallback
Fix plugin action links
Several fixes to improve compatibility

0.3.0

Add support for the aspectratio plugin for lazysizes, which makes images have the right height while loading. Thanks to Teemu Suoranta (@teemusuoranta) for implementing.
If Javascript is turned off, the image tag that would normally be lazy loaded is now hidden properly. Thanks to @diegocanal for reporting and fixing.

0.2.0

Update the lazysizes library to version 4.1.5
Fix lazy loading of elements without a class attribute, like some iframes
Fix translation loading

0.1.3

Remove unused code for advanced settings

0.1.2

Fix text domain loading

0.1.1

Updated readme

0.1.0

Initial version of the plugin

\n"},"short_description":"High performance and SEO friendly lazy loader for images, iframes and more. Many features, like low-res Blurhash placeholders and image fade-in","download_link":"https://downloads.wordpress.org/plugin/lazysizes.1.3.3.zip","screenshots":[],"tags":{"blurhash":"Blurhash","image":"image","lazy-load":"lazy load","lazysizes":"lazysizes","performance":"performance"},"versions":{"0.1.3":"https://downloads.wordpress.org/plugin/lazysizes.0.1.3.zip","0.2.0":"https://downloads.wordpress.org/plugin/lazysizes.0.2.0.zip","0.3.0":"https://downloads.wordpress.org/plugin/lazysizes.0.3.0.zip","1.0.0":"https://downloads.wordpress.org/plugin/lazysizes.1.0.0.zip","1.1.0":"https://downloads.wordpress.org/plugin/lazysizes.1.1.0.zip","1.2.0":"https://downloads.wordpress.org/plugin/lazysizes.1.2.0.zip","1.2.1":"https://downloads.wordpress.org/plugin/lazysizes.1.2.1.zip","1.3.0":"https://downloads.wordpress.org/plugin/lazysizes.1.3.0.zip","1.3.1":"https://downloads.wordpress.org/plugin/lazysizes.1.3.1.zip","1.3.2":"https://downloads.wordpress.org/plugin/lazysizes.1.3.2.zip","1.3.3":"https://downloads.wordpress.org/plugin/lazysizes.1.3.3.zip","trunk":"https://downloads.wordpress.org/plugin/lazysizes.zip"},"donate_link":"","icons":{"1x":"https://ps.w.org/lazysizes/assets/icon.svg?rev=2357198","svg":"https://ps.w.org/lazysizes/assets/icon.svg?rev=2357198"}},{"name":"WordPress REST API (Version 2)","slug":"rest-api","version":"2.0-beta15","author":"WP REST API Team","author_profile":"https://profiles.wordpress.org/rmccue/","requires":"4.6","tested":"4.7.29","requires_php":false,"requires_plugins":[],"rating":84,"ratings":{"1":5,"2":0,"3":3,"4":0,"5":26},"num_ratings":34,"support_threads":0,"support_threads_resolved":0,"downloaded":519573,"last_updated":"2016-10-19 2:05pm GMT","added":"2009-04-25","homepage":"https://github.com/WP-API/WP-API","sections":{"description":"

WordPress is moving towards becoming a fully-fledged application framework, and we need new APIs. This project was born to create an easy-to-use, easy-to-understand and well-tested framework for creating these APIs, plus creating APIs for core.

This plugin provides an easy to use REST API, available via HTTP. Grab your site’s data in simple JSON format, including users, posts, taxonomies and more. Retrieving or updating data is as simple as sending a HTTP request.

Want to get your site’s posts? Simply send a GET request to /wp-json/wp/v2/posts. Update user with ID 4? Send a PUT request to /wp-json/wp/v2/users/4. Get all posts with the search term “awesome”? GET /wp-json/wp/v2/posts?filter[s]=awesome. It’s that easy.

The WordPress REST API exposes a simple yet easy interface to WP Query, the posts API, post meta API, users API, revisions API and many more. Chances are, if you can do it with WordPress, the API will let you do it.

The REST API also includes an easy-to-use JavaScript API based on Backbone models, allowing plugin and theme developers to get up and running without needing to know anything about the details of getting connected.

Check out our documentation for information on what’s available in the API and how to use it. We’ve also got documentation on extending the API with extra data for plugin and theme developers!

All tickets for the project are being tracked on GitHub. You can also take a look at the recent updates for the project.

\n","installation":"

Install the WP REST API via the plugin directory, or by uploading the files manually to your server.

For full-flavoured API support, you’ll need to be using pretty permalinks to use the plugin, as it uses custom rewrite rules to power the API.

Once you’ve installed and activated the plugin, check out the documentation for details on your newly available endpoints.

\n","changelog":"

2.0 Beta 15.0 (October 07, 2016)

\n
Introduce support for Post Meta, Term Meta, User Meta, and Comment Meta in
\ntheir parent endpoints.
\n
For your meta fields to be exposed in the REST API, you need to register
\nthem. WordPress includes a register_meta() function which is not usually
\nrequired to get/set fields, but is required for API support.
\n
To register your field, simply call register_meta and set the show_in_rest
\nflag to true. Note: register_meta must be called separately for each meta
\nkey.
\n
(props @rmccue, @danielbachhuber, @kjbenk, @duncanjbrown, #2765)
\n
\n
Introduce Settings endpoint.
\n
Expose options to the REST API with the register_setting() function, by
\npassing $args = array( 'show_in_rest' => true ). Note: WordPress 4.7 is
\nrequired. See changeset [38635][https://core.trac.wordpress.org/changeset/38635].
\n
(props @joehoyle, @fjarrett, @danielbachhuber, @jonathanbardo,
\n@greatislander, #2739)
\n
\n
Attachments controller, change permissions check to match core.
\n
Check for the upload_files capability when creating an attachment.
\n
(props @nullvariable, @adamsilverstein, #2743)
\n
\n
Add ?{taxonomy}_exclude= query parameter
\n
This mirrors our existing support for ?{taxonomy}= filtering in the posts
\ncontroller (which allows querying for only records with are associated with
\nany of the provided term IDs for the specified taxonomy) by adding an
\nequivalent _exclude variant to list IDs of terms for which associated posts
\nshould NOT be returned.
\n
(props @kadamwhite, #2756)
\n
\n
Use get_comment_type() when comparing updating comment status.
\n
Comments having a empty comment_type within WordPress bites us again.
\nFixes a bug where comments could not be updated because of bad comparison
\nlogic.
\n
(props @joehoyle, #2753)
\n

2.0 Beta 13.0 (March 29, 2016)

\n
BREAKING CHANGE: Fix Content-Disposition header parsing.
\n
Allows regular form submissions from HTML forms, as well as properly formatted HTTP requests from clients. Note: this breaks backwards compatibility, as previously, the header parsing was completely wrong.
\n
(props @rmccue, #2239)
\n
\n
BREAKING CHANGE: Use compact links for embedded responses if they are available.
\n
Introduces curies for sites running WordPress 4.5 or greater; no changes for those running WordPress 4.4.
\n
(props @joehoyle, #2412)
\n
\n
JavaScript client updates:
\n
- Support lodash, plus older and newer underscore: add an alias for _.contains
- Add args and options on the model/collection prototypes
- Rework category/tag mixins to support new API structure
- Add workaround for the null/empty values returned by the API when creating a new post * these values are not accepted for subsequent updates/saves, so explicitly excluding them. See https://github.com/WP-API/WP-API/pull/2393
- Better handling of the (special) me endpoint
- Schema parsing cleanup
- Introduce wp.api.loadPromise so developers can ensure api load complete before using
\n
(props @adamsilverstein, #2403)
\n
\n
Only adds alternate link header for publicly viewable CPTs.
\n
(props @bradyvercher, #2387)
\n
\n
Adds roles param for GET /wp/v2/users.
\n
(props @BE-Webdesign, #2372)
\n
\n
Declares password in user schema, but never displays it.
\n
(props @danielbachhuber, #2386)
\n
\n
Permits edit context for requests which can edit the user.
\n
(props @danielbachhuber, #2383)
\n
\n
Adds rest_pre_insert_{$taxonomy} filter for terms.
\n
(props @kjbenk, #2377)
\n
\n
Supports taxonomy collection args on posts endpoint.
\n
(props @joehoyle, #2287)
\n
\n
Removes post meta link from post response.
\n
(props @joehoyle, #2288)
\n
\n
Registers description attribute when registering args from schema.
\n
(props @danielbachhuber, #2362)
\n
\n
Uses $comment from the database with rest_insert_comment action.
\n
(props @danielbachhuber, #2349)
\n
\n
Removes unnecessary global variables from users controller.
\n
(props @claudiosmweb, #2335)
\n
\n
Ensures GET /wp/v2/categories with out of bounds offset doesn’t return results.
\n
(props @danielbachhuber, #2313)
\n
\n
Adds top-level support for date queries on posts and comments.
\n
(props @BE-Webdesign, #2266, #2291)
\n
\n
Respects show_avatars setting for comments.
\n
(props @BE-Webdesign, #2271)
\n
\n
Uses cached get_the_terms() for terms-for-post for better performance.
\n
(props @rmccue, #2257)
\n
\n
Ensures comments search is an empty string.
\n
(props @rmccue, #2256)
\n
\n
If no title is provided in create attachment request or file metadata, falls back to filename.
\n
(props @danielbachhuber, #2254)
\n
\n
Removes unused $img_url_basename variable in attachments controller.
\n
(props @danielbachhuber, #2250)
\n

2.0 Beta 12.0 (February 9, 2016)

\n
BREAKING CHANGE: Removes meta endpoints from primary plugin.
\n
If your project depends on post meta endpoints, please install WP REST API Meta Endpoints. For the gory history of meta, read #1425 and linked issues. At this time, we recommend using register_rest_field() to expose meta (docs).
\n
(props @danielbachhuber, #2172)
\n
\n
BREAKING CHANGE: Returns original resource when deleting PTCU.
\n
Now that all resources require the force param, we don’t need to wrap delete responses with the trash state.
\n
(props @danielbachhuber, #2163)
\n
\n
BREAKING CHANGE: Uses roles rather than role in the Users controller.
\n
Building the REST API gives us the opportunity to standardize on roles, instead of having both roles and role.
\n
(props @joehoyle, #2177)
\n
\n
BREAKING CHANGES: Moves to consistent use of context throughout controllers.
\n
Contexts limit the data present in the response. Here’s how to think of them: embed correlates with sidebar representation, view represents the primary public view, and edit is the data expected for an editor.
\n
(props @danielbachhuber, #2205, #2204, #2203, #2218, #2216, #2230, #2184, #2235)
\n
\n
BREAKING CHANGE: Removes post_* query param support for GET /wp/v2/comments.
\n
The proper pattern is to use GET /wp/v2/posts to fetch the post IDs to limit the request to.
\n
(props @danielbachhuber, #2165)
\n
\n
BREAKING CHANGE: Introduces rest_validate_request_arg()/rest_sanitize_request_arg().
\n
Dedicated functions means we can use them for validating / sanitizing query args too. Removes WP_REST_Controller::validate_schema_property() and WP_REST_Controller::sanitize_schema_property().
\n
(props @danielbachhuber, #2166, #2213)
\n
\n
Requires minimum value of 1 for page param.
\n
(props @danielbachhuber, #2241)
\n
\n
Introduces media_type and mime_type params for GET /wp/v2/media.
\n
(props @danielbachhuber, #2231)
\n
\n
Uses the term cache for post data.
\n
(props @rmccue, #2234)
\n
\n
Supports for querying comments where post=0.
\n
(props @danielbachhuber, #1865)
\n
\n
Exposes taxonomy and post type capabilities in context=edit.
\n
(props @danielbachhuber, #2216)
\n
\n
Errors early when user can’t GET types or taxonomies when context=edit.
\n
(props @danielbachhuber, #2218)
\n
\n
Passes original $request context to prepare_items_query.
\n
(props @danielbachhuber, #2211)
\n
\n
Adds parent and parent_exclude params to GET Comments.
\n
(props @danielbachhuber, #2206)
\n
\n
Enforces minimum 1 and maximum 100 values for per_page parameter.
\n
(props @danielbachhuber, #2209)
\n
\n
Adds author and author_exclude params to GET Posts and Comments.
\n
(props @danielbachhuber, #2200, #2200)
\n
\n
Adds menu_order param for GET Pages; support menu_order orderby.
\n
(props @danielbachhuber, #2193)
\n
\n
Only calls sanitize_text_field() when sanitizing type=string,format=email.
\n
(props @danielbachhuber, #2185)
\n
\n
Validates GET /wp/v2/comments private query params.
\n
Returns an error when user doesn’t have permission to use them, instead of silently discarding.
\n
(props @danielbachhuber, #2178)
\n
\n
Explicitly prevents uploading attachments to other attachments or revisions.
\n
(props @danielbachhuber, #2180)
\n
\n
Permits user urls to be edited through the API.
\n
(props @danielbachhuber, #2182)
\n
\n
Marks all Status, Type and Taxonomy fields as readonly.
\n
(props @danielbachhuber, #2181)
\n
\n
Adds validation callbacks to collection query params.
\n
(props @danielbachhuber, #2170, #2171, #2176, #2174, #2175)
\n
\n
Links taxonomy terms to the post type collections they support.
\n
(props @danielbachhuber, #2167)
\n
\n
Returns error when making a GET request with invalid context.
\n
(props @danielbachhuber, #2169)
\n
\n
Adds trash status to GET /wp/v2/statuses.
\n
(props @danielbachhuber, #2158)
\n
\n
Indicates when fields have HTML in schema.
\n
(props @joehoyle, #2159)
\n
\n
Permits viewing of User who has published any Public posts.
\n
(props @danielbachhuber, #2155)
\n
\n
Respects show_avatars option when adding avatars to Users.
\n
(props @nullvariable, #2151)
\n
\n
Controllers use $namespace and $rest_base class variables for easier subclassing.
\n
(props @danielbachhuber, #2119, #2130, #2131, #2132, #2133, #2134, #2139, #2141, #2142)
\n

2.0 Beta 11.0 (January 25, 2016)

\n
BREAKING CHANGE: Moves Post->Term relations to the Post Resource
\n
Previously, a client would fetch a Post’s Tags with GET /wp/v2/posts/<id>/tags.
\n
In Beta 11, an array of term ids is included on the Post resource.
\n
The collection of terms for a Post can be fetched with GET /wp/v2/tags?post=<id>.
\n
The WP_REST_Posts_Terms_Controller class no longer exists.
\n
(props @joehoyle, #2063)
\n
\n
BREAKING CHANGE: Adds latest JS client including a minified version.
\n
See pull request for a summarized changelog.
\n
(props @adamsilverstein, #1981)
\n
\n
BREAKING CHANGE: Changes featured_image attribute on Posts to featured_media.
\n
While featuring other attachment types isn’t yet officially supported, this makes it easier for us to introduce the possibility in the future.
\n
(props @danielbachhuber, #2044)
\n
\n
BREAKING CHANGE: Uses discrete schema title for categories and tags.
\n
If you’ve used register_rest_field( 'term' ), you’ll need to change 'term' to 'tag' and/or 'category'.
\n
(props @danielbachhuber, #2005)
\n
\n
BREAKING CHANGE: Makes many filters dynamic based on the controller type.
\n
If you were using the rest_prepare_term filter, you’ll need to change it to rest_prepare_post_tag or rest_prepare_category.
\n
If you were using rest_post_query or rest_terms_query, you’ll need update your use to rest_page_query, etc.
\n
If you were using rest_post_trashable, rest_insert_post or rest_delete_post, they are now dynamic based on the post type slug.
\n
(props @danielbachhuber, #2008, #2010, #2057, #2058)
\n
\n
Renames GET /wp/v2/comments user param to author to match resource attribute.
\n
Not a breaking change, because it didn’t work in the first place.
\n
(props @danielbachhuber, #2105)
\n
\n
Adds support for GET /wp/v2/pages parent=1,2,3.
\n
(props @danielbachhuber, #2101)
\n
\n
Persists image metadata title and caption when not present in the request.
\n
(props @danielbachhuber, #2079)
\n
\n
Add parent_exclude param to GET /wp/v2/posts.
\n
(props @danielbachhuber, #2077)
\n
\n
Adds slug param support for collections of Posts, Users, and Taxonomy Terms.
\n
(props @danielbachhuber, #2071, #2072, #2103)
\n
\n
When a comment is already trashed, returns 410:rest_already_trashed.
\n
(props @danielbachhuber, #2069)
\n
\n
Filter the responses by context after processing additional fields.
\n
(props @danielbachhuber, #2067)
\n
\n
Adds offset param support for collections of Posts, Users, Comments, and Taxonomy Terms.
\n
(props @danielbachhuber, #2061, #2062, #2064, #2076)
\n
\n
Adds rest_insert_{$taxonomy} and rest_delete_{$taxonomy} actions.
\n
(props @danielbachhuber, #2060)
\n
\n
Provides more helpful error message/code on Post Create/Update fail.
\n
(props @danielbachhuber, #2053)
\n
\n
Forces GET /wp/v2/media to be limited to 'status' => [ inherit, private, trash ]
\n
(props @danielbachhuber, #2026)
\n
\n
Uses more correct error code for Comment::delete permission check.
\n
(props @danielbachhuber, #2054)
\n
\n
Calls prepare_item_for_response() directly in create and update methods.
\n
This lets us pass the original request through, giving the method and its filter genuine context, and avoids an
\nunnecessary call to get_item().
\n
(props @danielbachhuber, #2038, #2040, #2041, #2043, #2042)
\n
\n
Moves permission check methods across controllers.
\n
Placing them above the method they’re supposed to check makes the code more readable.
\n
(props @danielbachhuber, #2030, #2029, #2034, #2036, #2037, #2035, #2039)
\n
\n
Requires force argument for DELETE /wp/v2/<taxonomy>/<id>.
\n
(props @danielbachhuber, #2028)
\n
\n
Conditionally requires and defines REST API classes and functions.
\n
(props @danielbachhuber, #2023, #2024)
\n
\n
Avoid a duplicate query for the comment count.
\n
(props @rmccue, #2015)
\n
\n
Parses $date if available in prepare_date_response()
\n
(props @adamsilverstein, #1951)
\n
\n
Abstracts POST /wp/v2/media permissions check.
\n
(props @danielbachhuber, #2003)
\n
\n
Adds exclude param to getting collections of Posts, Users, Comments, and Taxonomy Terms.
\n
(props @danielbachhuber, #1998, #1999, #2000, #2002)
\n
\n
Adds rest_comment_query for filtering GET /wp/v2/comments.
\n
(props @danielbachhuber, #2007)
\n
\n
Uses HTTP status code 500 for db_update_error when creating an attachment.
\n
(props @danielbachhuber, #1993)
\n
\n
Adds helpful description to force param across all DELETE registrations
\n
(props @danielbachhuber, #2004, #2027)
\n
\n
In GET /wp/v2/<taxonomy>, drops support for orderby=>term_id.
\n
Only one id is exposed through the REST API.
\n
(props @danielbachhuber, #1990)
\n

2.0 Beta 10.0 (January 11, 2016)

\n
SECURITY: Ensure media of private posts are private too.
\n
Reported by @danielbachhuber on 2016-01-08.
\n
\n
BREAKING CHANGE: Removes compatibility repo for WordPress 4.3.
\n
WordPress 4.4 is now the minimum supported WordPress version.
\n
(props @danielbachhuber, #1848)
\n
\n
BREAKING CHANGE: Changes link relation for types and taxonomies.
\n
In Beta 9, this link relation was introduced as item, which isn’t correct. The relation has been changed to https://api.w.org/items.
\n
(props @danielbachhuber, #1853)
\n
\n
BREAKING CHANGE: Introduces edit context for wp/v2/types and wp/v2/taxonomies.
\n
Some fields have moved into this context, which require edit_posts and manage_terms, respectively.
\n
(props @danielbachhuber, #1894, #1864)
\n
\n
BREAKING CHANGE: Removes post_format as a term _link for Posts.
\n
Post formats aren’t a custom taxonomy in the eyes of the REST API.
\n
(props @danielbachhuber, #1854)
\n
\n
Declares parent query param for Pages.
\n
(props @danielbachhuber, #1975)
\n
\n
Permits logged-in users to query for media.
\n
(props @danielbachhuber, #1973)
\n
\n
Removes duplicated query params from Terms controller.
\n
(props @danielbachhuber, #1963)
\n
\n
Adds include param to /wp/v2/posts, /wp/v2/users, /wp/v2/<taxonomy> and /wp/v2/comments.
\n
(props @danielbachhuber, #1961, #1964, #1968, #1971)
\n
\n
Ensures GET /wp/v2/posts respects order and orderby params.
\n
(props @danielbachhuber, #1962)
\n
\n
Fixes fatal by loading wp-admin/includes/user.php to expose wp_delete_user().
\n
(props @danielbachhuber, #1958)
\n
\n
Permits making a post sticky when also supplying an empty password.
\n
(props @westonruter, #1949)
\n
\n
Uses WP_REST_Request internally across controllers.
\n
(props @danielbachhuber, #1933, #1939, #1934, #1938)
\n
\n
Cleans up permissions checks in WP_REST_Terms_Controller.
\n
(props @danielbachhuber, #1941)
\n
\n
Uses show_in_rest to determine publicness for post types.
\n
(props @danielbachhuber, #1942)
\n
\n
Makes description strings available for translation.
\n
(props @danielbachhuber, #1944)
\n
\n
Checks assign_terms cap for taxonomy when managing post terms.
\n
(props @danielbachhuber, #1940)
\n
\n
Defer to edit_posts of the custom post type when accessing private query vars.
\n
(props @danielbachhuber, #1886)
\n
\n
Allows Terms collection params to be filtered.
\n
(props @rachelbaker, #1882)
\n
\n
Renames post terms create/delete permissions callback.
\n
(props @wpsmith, #1923)
\n
\n
Fixes invalid use of ‘uri’ as schema type.
\n
(props @wpsmith, #1913)
\n
\n
Casts integer with (int) over intval for speed.
\n
(props @wpsmith, #1907)
\n
\n
Fixes PHP Doc typo for validate_schema_property and sanitize_schema_property.
\n
(props @wpsmith, @danielbachhuber, #1909, #1910)
\n
\n
Adds a helpful description to the filter argument.
\n
(props @danielbachhuber, #1885)
\n
\n
Changes order of Users response to match schema order.
\n
(props @rachelbaker, #1879)
\n
\n
Adjusts Posts pagination headers for filter params.
\n
(props @rachelbaker, #1878)
\n
\n
Uses proper status code when failing to get comments of private post.
\n
(props @danielbachhuber, #1866)
\n
\n
Fixes invalid capability for comments get items permissions callback.
\n
manage_comments doesn’t exist; moderate_comments does.
\n
(props @danielbachhuber, #1866)
\n
\n
Permits creating comments without an assigned post.
\n
(props @danielbachhuber, #1857)
\n
\n
Prevents error notice when show_in_rest isn’t set for a post type.
\n
(props @danielbachhuber, #1852)
\n

2.0 Beta 9.0 (December 11, 2015)

\n
BREAKING CHANGE: Move tags and categories to top-level endpoints.
\n
Tags are now accessible at /wp/v2/tags, and categories accessible at /wp/v2/categories. Post terms reside at /wp/v2/posts/<id>/tags and /wp/v2/<id>/categories.
\n
(props @danielbachhuber, #1802)
\n
\n
BREAKING CHANGE: Return object for requests to /wp/v2/taxonomies.
\n
This is consistent with /wp/v2/types and /wp/v2/statuses.
\n
(props @danielbachhuber, #1825)
\n
\n
BREAKING CHANGE: Remove rest_get_timezone().
\n
json_get_timezone() was only ever used in v1. This function causes fatals, and shouldn’t be used.
\n
(props @danielbachhuber, #1823)
\n
\n
BREAKING CHANGE: Rename register_api_field() to register_rest_field().
\n
Introduces a register_api_field() function for backwards compat, which calls _doing_it_wrong(). However, register_api_field() won’t ever be committed to WordPress core, so you should update your function calls.
\n
(props @danielbachhuber, #1824)
\n
\n
BREAKING CHANGE: Change taxonomies’ post_type argument to type.
\n
It’s consistent with how we’re exposing post types in the API.
\n
(props @danielbachhuber, #1824)
\n
\n
Sync infrastructure with shipped in WordPress 4.4.
\n
- wp-includes/rest-api/rest-functions.php is removed, and its functions moved into wp-includes/rest-api.php.
- Send nocache headers for REST requests. #34832
- Fix handling of HEAD requests. #34837
- Mark WP_REST_Server::get_raw_data() as static. #34768
- Unabbreviate error string. #34818
\n
\n
Change terms endpoints to use term_id not tt_id.
\n
(props @joehoyle, #1837)
\n
\n
Standardize declaration of context param for GET requests across controllers.
\n
However, we’re still inconsistent in which controllers expose which params. Follow #1845 for further discussion.
\n
(props @danielbachhuber, #1795, #1835, #1838)
\n
\n
Link types / taxonomies to their collections, and vice versa.
\n
Collections link to their type / taxonomy with the about relation; types / taxonomies link to their colletion with the item relation, which is imperfect and may change in the future.
\n
(props @danielbachhuber, #1814, #1817, #1829. #1846)
\n
\n
Add missing ‘wp/v2’ in Location Response header when creating new Post Meta.
\n
(props @johanmynhardt, #1790)
\n
\n
Expose Post collection query params, including author, order, orderby and status.
\n
(props @danielbachhuber, #1793)
\n
\n
Ignore sticky posts by default.
\n
(props @danielbachhuber, #1801)
\n
\n
Include full image size in attachment sizes attribute.
\n
(props @danielbachhuber, #1806)
\n
\n
In text strings, use id instead of ID.
\n
ID is an implementation artifact. Our Resources use id.
\n
(props @danielbachhuber, #1803)
\n
\n
Ensure attachment.sizes[] use mime_type instead of mime-type.
\n
(props @danielbachhuber, #1809)
\n
\n
Introduce rest_authorization_required_code().
\n
Many controllers returned incorrect HTTP codes, which this also fixes.
\n
(props @danielbachhuber, #1808)
\n
\n
Respect core’s comment_registration setting.
\n
If it’s enabled, require users to be logged in to comment.
\n
(props @danielbachhuber, #1826)
\n
\n
Default to wildcard when searching users.
\n
(props @danielbachhuber, #1827)
\n
\n
Bring the wp-api.js library up to date for v2 of the REST API.
\n
(props @adamsilverstein, #1828)
\n
\n
Add rest_prepare_status filter.
\n
(props @danielbachhuber, #1830)
\n
\n
Make prepare_* filters more consistent.
\n
(props @danielbachhuber, #1831)
\n
\n
Add rest_prepare_post_type filter for post types.
\n
(props @danielbachhuber, #1833)
\n

2.0 Beta 8.0 (December 1, 2015)

\n
Prevent fatals when uploading attachment by including admin utilities.
\n
(props @danielbachhuber, #1756)
\n
\n
Return 201 status code when creating a term.
\n
(props @danielbachhuber, #1753)
\n
\n
Don’t permit requesting terms cross routes.
\n
Clients should only be able to request categories from the category route, and tags from the tag route.
\n
(props @danielbachhuber, #1764)
\n
\n
Set fields=>id when using WP_User_Query to fix large memory usage
\n
(props @joehoyle, #1770)
\n
\n
Fix Post _link to attached attachments.
\n
(props @danielbachhuber, #1777)
\n
\n
Add support for getting a post with a custom public status.
\n
(props @danielbachhuber, #1765)
\n
\n
Ensure post content doesn’t get double-slashed on update.
\n
(props @joehoyle, #1772)
\n
\n
Change ‘int’ to ‘integer’ for WP_REST_Controller::validate_schema_property()
\n
(props @wpsmith, #1759)
\n

2.0 Beta 7.0 (November 17, 2015)

\n
Sync infrastructure from WordPress core as of r35691.
\n
- Remove register_api_field() because it’s conceptually tied to WP_REST_Controller #34730
- Update the REST API header links to use api.w.org #34303
- Require the $namespace argument in register_rest_route() #34416
- Include enum and description in help data #34543
- Save preg_match iterations in WP_REST_Server #34488
- Don’t return route URL in WP_REST_Request:get_params() #34647
\n
\n
Restore register_api_field() within the plugin.
\n
(props @danielbachhuber, #1748)
\n
\n
Require admin functions for use of wp_handle_upload(), fixing fatal.
\n
(props @joehoyle, #1746)
\n
\n
Properly handle requesting terms where parent=0 and 0 is a string.
\n
(props @danielbachhuber, #1739)
\n
\n
Prevent PHP error notice when &filter isn’t an array.
\n
(props @danielbachhuber, #1734)
\n
\n
Change link relations to use api.w.org.
\n
(props @danielbachhuber, #1726)
\n

2.0 Beta 6.0 (November 12, 2015)

\n
Remove global inclusion of wp-admin/includes/admin.php
\n
For a long time, the REST API loaded wp-admin/includes/admin.php to make use of specific admin utilities. Now, it only loads those admin utilities when it needs them.
\n
If your custom endpoints make use of admin utilities, you’ll need to make sure to load wp-admin/includes/admin.php before you use them.
\n
(props @joehoyle, #1696)
\n
\n
Link directly to the featured image in a Post’s links.
\n
(props @rmccue, #1563, #1711)
\n
\n
Provide object type as callback argument for custom API fields.
\n
(props @jtsternberg, #1714)
\n
\n
Change users schema order to be order of importance instead of alpha.
\n
(props @rachelbaker, #1708)
\n
\n
Clarify documentation for date and modified attributes.
\n
(props @danielbachhuber, #1715)
\n
\n
Update the wp-api.js client from the client-js repo.
\n
(props @rachelbaker, #1709)
\n
\n
Fix the format enum to be an array of strings.
\n
(props @joehoyle, #1707)
\n
\n
Run revisions for collection through prepare_response_for_collection().
\n
(props @danielbachhuber, @rachelbaker, #1671)
\n
\n
Expose date_gmt for view context of Posts and Comments.
\n
(props @danielbachhuber, #1690)
\n
\n
Fix PHP and JS docblock formatting.
\n
(props @ahmadawais, #1699, #1699, #1701, #1700, #1702, #1703)
\n
\n
Include media_details attribute for attachments in embed context.
\n
For image attachments, media_details includes a sizes array of image sizes, which is useful for templating.
\n
(props @danielbachhuber, #1667)
\n
\n
Make WP_REST_Controller error messages more helpful by specifying method to subclass.
\n
(props @danielbachhuber, #1670)
\n
\n
Expose slug in embed context for Users.
\n
user_nicename is a public attribute, used in user URLs, so this is safe data to present.
\n
(props @danielbachhuber, #1666)
\n
\n
Handle falsy value from wp_count_terms(), fixing fatal.
\n
(props @joehoyle, #1641)
\n
\n
Correct methods in WP_REST_SERVER::EDITABLE description.
\n
(props @rachelbaker, #1601)
\n
\n
Add the embed context to Users collection query params.
\n
(props @rachelbaker, #1591)
\n
\n
Add Terms Controller collection args details.
\n
(props @rachelbaker, #1603)
\n
\n
Set comment author details from current user.
\n
(props @rmccue, #1580)
\n
\n
More hook documentation.
\n
(props @adamsilverstein, #1556, #1560)
\n
\n
Return the trashed status of deleted posts/comments.
\n
When a post or a comment is deleted, returns a flag to say whether it’s been trashed or properly deleted.
\n
(props @pento, #1499)
\n
\n
In WP_REST_Posts_Controller::update_item(), check the post ID based on the proper post type.
\n
(props @rachelbaker, #1497)
\n

2.0 Beta 5.0 (October 23, 2015)

\n
Load api-core as a compatibility library
\n
Now api-core has been merged into WordPress trunk (for 4.4) we should no longer load the infrastructure code when it’s already available. This also fixes a fatal error for users who were on trunk.
\n
(props @rmccue)
\n
\n
Switch to new mysql_to_rfc3339
\n
(props @rmccue)
\n
\n
Double-check term taxonomy
\n
(props @rmccue)
\n
\n
Load admin functions
\n
This was removed from the latest beta of WordPress in the REST API infrastructure, a more long term fix is planned.
\n
(props @joehoyle)
\n
\n
Add Add compat shim for renamed rest_mysql_to_rfc3339()
\n
(props @danielbachhuber)
\n
\n
Compat shim for wp_is_numeric_array()
\n
(props @danielbachhuber)
\n
\n
Revert Switch to register_post_type_args filter
\n
(props @joehoyle)
\n

2.0 Beta 4.0 (August 14, 2015)

\n
Show public user information through the user controller.
\n
In WordPress as of r32683 (scheduled for 4.3), WP_User_Query now has support for getting users with published posts.
\n
To match current behaviour in WordPress themes and feeds, we now expose this public user information. This includes the avatar, description, user ID, custom URL, display name, and URL, for users who have published at least one post on the site. This information is available to all clients; other fields and data for all users are still only available when authenticated.
\n
(props @joehoyle, @rmccue, @Shelob9, #1397, #839, #1435)
\n
\n
Send schema in OPTIONS requests and index.
\n
Rather than using separate /schema endpoints, the schema for items is now available through an OPTIONS request to the route. This means that full documentation is now available for endpoints through an OPTIONS request; this includes available methods, what data you can pass to the endpoint, and the data you’ll get back.
\n
This data is now also available in the main index and namespace indexes. Simply request the index with context=help to get full schema data. Warning: this response will be huge. The schema for single endpoints is also available in the collection’s OPTIONS response.
\n
⚠️ This breaks backwards compatibility for clients relying on schemas being at their own routes. These clients should instead send OPTIONS requests.
\n
Custom endpoints can register their own schema via the schema option on the route. This option should live side-by-side with the endpoints (similar to relation in WP’s meta queries), so your registration call will look something like:
\n
`php
\nregister_rest_route( ‘test-ns’, ‘/test’, array(
\narray(
\n ‘methods’ => ‘GET’,
\n ‘callback’ => ‘my_test_callback’,
\n),
\n
‘schema’ => ‘my_schema_callback’,
\n) );
\n `
\n
(props @rmccue, #1415, #1222, #1305)
\n
\n
Update JavaScript API for version 2.
\n
Our fantastic JavaScript API from version 1 is now available for version 2, refreshed with the latest and greatest changes.
\n
As a refresher: if you want to use it, simply make your script depend on wp-api when you enqueue it. If you want to enqueue the script manually, add wp_enqueue_script( 'wp-api' ) to a callback on wp_enqueue_scripts.
\n
(props @tlovett1, @kadamwhite, @nathanrice, #1374, #1320)
\n
\n
Embed links inside items in a collection.
\n
Previously when fetching a collection of items, you only received the items themselves. To fetch the links as well via embedding, you needed to make a request to the single item with _embed set.
\n
No longer! You can now request a collection with embeds enabled (try /wp/v2/posts?_embed). This will embed links inside each item, allowing you to build interface items much easier (for example, post archive pages can get featured image data at the same time).
\n
This also applies to custom endpoints. Any endpoint that returns a list of objects will automatically have the embedding applied to objects inside the list.
\n
(props @rmccue, #1459, #865)
\n
\n
Fix potential XSS vulnerability.
\n
Requests from other origins could potentially run code on the API domain, allowing cross-origin access to authentication cookies or similar.
\n
Reported by @xknown on 2015-07-23.
\n
\n
Move /posts WP_Query vars back to filter param.
\n
In version 1, we had internal WP_Query vars available via filter (e.g. filter[s]=search+term). For our first betas of version 2, we tried something different and exposed these directly on the endpoint. The experiment has now concluded; we didn’t like this that much, so filter is back.
\n
We plan on adding nicer looking arguments to collections in future releases, with a view towards being consistent across different collections. We also plan on opening up the underlying query vars via filter for users, comments, and terms as well.
\n
⚠️ This breaks backwards compatibility for users using WP Query vars. Simply change your x=y parameter to filter[x]=y.
\n
(props @WP-API, #1420)
\n
\n
Respect rest_base for taxonomies.
\n
⚠️ This breaks backwards compatibility by changing the /wp/v2/posts/{id}/terms/post_tag endpoint to /wp/v2/posts/{id}/tag.
\n
(props @joehoyle, #1466)
\n
\n
Add permission check for retrieving the posts collection in edit context.
\n
By extension of the fact that getting any individual post yields a forbidden context error when the context=edit and the user is not authorized, the user should also not be permitted to list any post items when unauthorized.
\n
(props @danielpunkass, #1412)
\n
\n
Ensure the REST API URL always has a trailing slash.
\n
Previously, when pretty permalinks were enabled, the API URL during autodiscovery looked like /wp-json, whereas the non-pretty permalink URL looked like ?rest_route=/. These are now consistent, and always end with a slash character to simplify client URL building.
\n
(props @danielpunkass, @rmccue, #1426, #1442, #1455, #1467)
\n
\n
Use wp_json_encode instead of json_encode
\n
Since WordPress 4.1, wp_json_encode has been available to ensure encoded values are sane, and that non-UTF8 encodings are supported. We now use this function rather than doing the encode ourselves.
\n
(props @rmccue, @pento, #1417)
\n
\n
Add role to schema for users.
\n
The available roles you can assign to a user are now available in the schema as an enum.
\n
(props @joehoyle, #1400)
\n
\n
Use the schema for validation inside the comments controller.
\n
Previously, the schema was merely a decorative element for documentation inside the comments controller. To bring it inline with our other controllers, the schema is now used internally for validation.
\n
(props @joehoyle, #1422)
\n
\n
Don’t set the Location header in update responses.
\n
Previously, the Location header was sent when updating resources due to some inadvertent copypasta. This header should only be sent when creating to direct clients to the new resource, and isn’t required when you’re already on the correct resource.
\n
(props @rachelbaker, #1441)
\n
\n
Re-enable the rest_insert_post action hook for WP_REST_Posts_Controller
\n
This was disabled during 2.0 development to avoid breaking lots of plugins on the json_insert_post action. Now that we’ve changed namespaces and are Mostly Stable ™, we can re-enable the action.
\n
(props @jaredcobb, #1427, #1424)
\n
\n
Fix post taxonomy terms link URLs.
\n
When moving the routes in a previous beta, we forgot to correct the links on post objects to the new correct route. Sorry!
\n
(props @rachelbaker, @joehoyle, #1447, #1383)
\n
\n
Use wp_get_attachment_image_src() on the image sizes in attachments.
\n
Since the first versions of the API, we’ve been building attachment URLs via str_replace. Who knows why we were doing this, but it caused problems with custom attachment URLs (such as CDN-hosted images). This now correctly uses the internal functions and filters.
\n
(props @joehoyle, #1462)
\n
\n
Make the embed context a default, not forced.
\n
If you want embeds to bring in full data rather than with context=edit, you can now change the link to specify context=view explicitly.
\n
(props @rmccue, #1464)
\n
\n
Ensure we always use the term_taxonomy_id and never expose term_id publicly.
\n
Previously, term_id was inadvertently exposed in some error responses.
\n
(props @jdolan, #1430)
\n
\n
Fix adding alt text to attachments on creation.
\n
Previously, this could only be set when updating an attachment, not when creating one.
\n
(props @joehoyle, #1398)
\n
\n
Throw an error when registering routes without a namespace.
\n
Namespaces should always be provided when registering routes. We now throw a doing_it_wrong error when attempting to register one. (Previously, this caused a warning, or an invalid internal route.)
\n
If you really need to register namespaceless routes (e.g. to replicate an existing API), call WP_REST_Server::register_route directly rather than using the convenience function.
\n
(props @joehoyle, @rmccue, #1355)
\n
\n
Show links on embeds.
\n
Previously, links were accidentally stripped from embedded response data.
\n
(props @rmccue, #1472)
\n
\n
Clarify insufficient permisssion error when editing posts.
\n
(props @danielpunkass, #1411)
\n
\n
Improve @return inline docs for rest_ensure_response()
\n
(props @Shelob9, #1328)
\n
\n
Check taxonomies exist before trying to set properties.
\n
(props @joehoyle, @rachelbaker, #1354)
\n
\n
Update controllers to ensure we use sanitize_callback wherever possible.
\n
(props @joehoyle, #1399)
\n
\n
Add more phpDoc documentation, and correct existing documentation.
\n
(props @Shelob9, @rmccue, #1432, #1433, #1465)
\n
\n
Update testing infrastructure.
\n
Travis now runs our coding standards tests in parallel, and now uses the new, faster container-based testing infrastructure.
\n
(props @ntwb, @frozzare, #1449, #1457)
\n

View all changes

2.0 Beta 3.0 (July 1, 2015)

\n
Add ability to declare sanitization and default options for schema fields.
\n
The arg_options array can be used to declare the sanitization callback,
\ndefault value, or requirement of a field.
\n
(props @joehoyle, #1345)
\n(props @joehoyle, #1346)
\n
\n
Expand supported parameters for creating and updating Comments.
\n
(props @rachelbaker, #1245)
\n
\n
Declare collection parameters for Terms of a Post.
\n
Define the available collection parameters in get_collection_params() and
\nallow Terms of a Post to be queried by term order.
\n
(props @danielbachhuber, #1332)
\n
\n
Improve the Attachment error message for an invalid Content-Disposition
\n
(props @danielbachhuber, #1317)
\n
\n
Return 200 status when updating Attachments, Comments, and Users.
\n
(props @rachelbaker, #1348)
\n
\n
Remove unnecessary handle_format_param() method.
\n
(props @danielbachhuber, #1331)
\n
\n
Add author_avatar_url field to the Comment response and schema.
\n
(props @rachelbaker #1327)
\n
\n
Introduce rest_do_request() for making REST requests internally.
\n
(props @danielbachhuber, #1333)
\n
\n
Remove unused DateTime class.
\n
(props @rmccue, #1314)
\n
\n
Add inline documentation for $wp_rest_server global.
\n
(props @Shelob9, #1324)
\n
View all changes
\n
2.0 Beta 2.0 (May 28, 2015)
\n
\n
\n
Load the WP REST API before the main query runs.
\n
The rest_api_loaded function now hooks into the parse_request action.
\nThis change prevents the main query from being run on every request and
\nallows sites to set WP_USE_THEMES to false. Previously, the main query
\nwas always being run (SELECT * FROM wp_posts LIMIT 10), even though the
\nresult was never used and couldn’t be cached.
\n
(props @rmccue, #1270)
\n
\n
Register a new field on an existing WordPress object type.
\n
Introduces register_api_field() to add a field to an object and
\nits schema.
\n
(props @joehoyle, @rachelbaker, #927)
\n(props @joehoyle, #1207)
\n(props @joehoyle, #1243)
\n
\n
Add endpoints for viewing, creating, updating, and deleting Terms for a Post.
\n
The new WP_REST_Posts_Terms_Controller class controller supports routes for
\nTerms that belong to a Post.
\n
(props @joehoyle, @danielbachhuber, #1216)
\n
\n
Add pagination headers for collection queries.
\n
The X-WP-Total and X-WP-TotalPages are now present in terms, comments,
\nand users collection responses.
\n
(props @danielbachhuber, #1182)
\n(props @danielbachhuber, #1191)
\n(props @danielbachhuber, @joehoyle, #1197)
\n
\n
List registered namespaces in the index for feature detection.
\n
The index (/wp-json by default) now contains a list of the available
\nnamespaces. This allows for simple feature detection. You can grab the index
\nand check namespaces for wp/v3 or pluginname/v2, which indicate the
\nsupported endpoints on the site.
\n
(props @rmccue,, #1283)
\n
\n
Standardize link property relations and support embedding for all resources.
\n
Change link properties to use IANA-registered relations. Also adds embedding
\nsupport to Attachments, Comments and Terms.
\n
(props @rmccue, @rachelbaker, #1284)
\n
\n
Add support for Composer dependency management.
\n
Allows you to recursively install/update the WP REST API inside of WordPress
\nplugins or themes.
\n
(props @QWp6t, #1157)
\n
\n
Return full objects in the delete response.
\n
Instead of returning a random message when deleting a Post, Comment, Term, or
\nUser provide the original resource data.
\n
(props @danielbachhuber, #1253)
\n(props @danielbachhuber, #1254)
\n(props @danielbachhuber, #1255)
\n(props @danielbachhuber, #1256)
\n
\n
Return programmatically readable error messages for invalid or missing
\nrequired parameters.
\n
(props @joehoyle, #1175)
\n
\n
Declare supported arguments for Comment and User collection queries.
\n
(props @danielbachhuber, #1211)
\n(props @danielbachhuber, #1217)
\n
\n
Automatically validate parameters based on Schema data.
\n
(props @joehoyle, #1128)
\n
\n
Use the show_in_rest attributes for exposing Taxonomies.
\n
(props @joehoyle, #1279)
\n
\n
Handle parent when creating or updating a Term.
\n
(props @joehoyle, #1221)
\n
\n
Limit fields returned in embed context User responses.
\n
(props @rachelbaker, #1251)
\n
\n
Only include parent in term response when tax is hierarchical.
\n
(props @danielbachhuber, #1189)
\n
\n
Fix bug in creating comments if type was not set.
\n
(props @rachelbaker, #1244)
\n
\n
Rename post_name field to post_slug.
\n
(props @danielbachhuber, #1235)
\n
\n
Add check when creating a user to verify the provided role is valid.
\n
(props @rachelbaker, #1267)
\n
\n
Add link properties to the Post Status response.
\n
(props @joehoyle, #1243)
\n
\n
Return 0 for parent in Post response instead of null.
\n
(props @danielbachhuber, #1269)
\n
\n
Only link author when there’s a valid author
\n
(props @danielbachhuber, #1203)
\n
\n
Only permit querying by parent term when tax is hierarchical.
\n
(props @danielbachhuber, #1219)
\n
\n
Only permit deleting posts of the proper type
\n
(props @danielbachhuber, #1257)
\n
\n
Set pagination headers even when no found posts.
\n
(props @danielbachhuber, #1209)
\n
\n
Correct prefix in rest_request_parameter_order filter.
\n
(props @quasel, #1158)
\n
\n
Retool WP_REST_Terms_Controller to follow Posts controller pattern.
\n
(props @danielbachhuber, #1170)
\n
\n
Remove unused accept_json argument from the register_routes method.
\n
(props @quasel, #1160)
\n
\n
Fix typo in sanitize_params inline documentation.
\n
(props @Shelob9, #1226)
\n
\n
Remove commented out code in dispatch method.
\n
(props @rachelbaker, #1162)
\n

View all changes

2.0 Beta 1.1

\n
Fix user access security vulnerability.
\n
Authenticated users were able to escalate their privileges bypassing the
\nexpected capabilities check.
\n
Reported by @kacperszurek on 2015-05-16.
\n

2.0 Beta 1 (April 28, 2015)

Partial rewrite and evolution of the REST API to prepare for core integration.

For versions 0.x through 1.x, see the legacy plugin changelog.

\n","faq":"\n

Installation Instructions

Install the WP REST API via the plugin directory, or by uploading the files manually to your server.

For full-flavoured API support, you’ll need to be using pretty permalinks to use the plugin, as it uses custom rewrite rules to power the API.

Once you’ve installed and activated the plugin, check out the documentation for details on your newly available endpoints.

\n\n"},"short_description":"Access your site's data through an easy-to-use HTTP REST API. (Version 2)","download_link":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta15.zip","screenshots":[],"tags":{"api":"api","json":"JSON","rest":"rest","rest-api":"rest-api"},"versions":{"2.0-beta10":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta10.zip","2.0-beta11":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta11.zip","2.0-beta12":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta12.zip","2.0-beta12.1":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta12.1.zip","2.0-beta13":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta13.zip","2.0-beta13.1":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta13.1.zip","2.0-beta14":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta14.zip","2.0-beta15":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta15.zip","2.0-beta3":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta3.zip","2.0-beta3.1":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta3.1.zip","2.0-beta4":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta4.zip","2.0-beta4.1":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta4.1.zip","2.0-beta5":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta5.zip","2.0-beta5.1":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta5.1.zip","2.0-beta6":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta6.zip","2.0-beta6.1":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta6.1.zip","2.0-beta7":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta7.zip","2.0-beta7.1":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta7.1.zip","2.0-beta8":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta8.zip","2.0-beta8.1":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta8.1.zip","2.0-beta9":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta9.zip","2.0-beta9.1":"https://downloads.wordpress.org/plugin/rest-api.2.0-beta9.1.zip","trunk":"https://downloads.wordpress.org/plugin/rest-api.zip"},"donate_link":"","icons":{"1x":"https://ps.w.org/rest-api/assets/icon-128x128.png?rev=1346297","2x":"https://ps.w.org/rest-api/assets/icon-256x256.png?rev=1346297"}},{"name":"Imperfect Quotes","slug":"imperfect-quotes","version":"0.9.0","author":"Brandon Ferens, Perfect Space, Inc., Matt Parrott","author_profile":"https://profiles.wordpress.org/mattparrott/","requires":"3.0","tested":"3.3.2","requires_php":false,"requires_plugins":[],"rating":0,"ratings":{"1":0,"2":0,"3":0,"4":0,"5":0},"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"downloaded":9094,"last_updated":"2012-08-17 3:51pm GMT","added":"2012-08-16","homepage":"http://www.swarmstrategies.com/imperfect-quotes","sections":{"description":"

Use the intuitive and powerful rich text interface to add and edit quotes,
\nusing the ‘featured image’ functionality to add a thumbnail image. Then, use
\neither the supplied widget, a simple shortcode, or a straightforward function
\nin your theme to add either a specific quote or a random quote to your site.

This plugin is a fork of Perfect Quotes. I forked it because it’s an excellent
\nplugin. In some ways, it’s more powerful and flexible than this one. I highly
\nrecommend it if this plugin is too simple for you and you don’t need either
\nthe thumbnail feature or the rich text editing option.

Features

Widget based to easily place your quotes where you like.
A custom shortcode is included if you want to place your quotes within a post or a page.
Based on Custom Post types with its own admin menu.

Support languages

PHP
CSS
jQuery/javascript

\n","installation":"

Upload plugin folder to the /wp-content/plugins/ directory.
Activate the plugin through the “Plugins” menu in WordPress.
Go to the Imperfect Quotes menu and select Add new.
Type in the author.
Type in the quote.
Add a Featured Image to the post (don’t actually insert the image, though!)

It will look something like this:

The trouble with quotes on the internet is that
\nit’s difficult to discern whether or not they are genuine.
\n– Abraham Lincoln [lincoln.jpg]

Widget

Include the widget by going to Appearance > Widgets.
Drag the Imperfect Quotes widget to the area of your choice.
Give your widget a custom title if you wish.

Shortcode

From any page or post, you can add shortcode to display all your quotes.

From the Imperfect Quotes home area, there is a column called Shortcode.
\nFind the particular quote you want and copy the corresponding shortcode.
\nIt looks something like [imperfect_quotes id=”1″].
\nPaste this into your post or onto a page and your quote will magically appear!

For more help

For more help please visit http://www.swarmstrategies.com/imperfect-quotes

\n","faq":"\n

Does your plugin have a feature to randomly select quotes?

Unless you specify the quote by its id, it’ll be randomly selected.

Why am I seeing two pictures of Abraham Lincoln on my page?

That’s because you’re not only associating the quote with a featured image,
\nyou’re adding the image to the quote itself. If you click ‘Use as Featured
\nImage’ at the bottom of the image properties dialog, then ‘X’ out of the
\ndialog, you’ll have a featured image without inserting it into the quote.

While this is a bit counter-intuitive, it gives you the power to insert images
\nand other rich content into quotes when you actually want to do that.

\n\n","changelog":"

0.9.1

Forked! IMPerfect Quotes
Rich text editor for the quote
‘Featured Image’ functionality for thumbnails of the author
Removed ‘Action Button’
Simplified shortcode attributes
Don’t support showing multiple quotes
Don’t support metadata

0.3.3

No more ugly custom field interface! A nice new look that makes entering your quotes much easier!
A brand new editor window feature that allows you to select your quote(s) and insert the shortcode for you!

0.3.2

Renamed some functions to avoid conflict with other plugins

0.3.1

Added a new custom field for displaying where the author is from. It could be a book, or a company, or a… Really anything!

0.3

Added the ability to display random quotes or testimonials.

0.2

Added much better shortcode implementation.
Added the shortcode to the Custom Post overview page for easy integration into your post or page.

0.1

This is the initial release.

\n","screenshots":"

$\"How$
How the quote appears on a website
$\"Manage$
Manage the quotes on the admin page
$\"Add$
Add a thumbnail to your quote

"},"short_description":"Use the intuitive and powerful rich text interface to add and edit quotes,","download_link":"https://downloads.wordpress.org/plugin/imperfect-quotes.0.9.3.zip","screenshots":{"1":{"src":"https://ps.w.org/imperfect-quotes/trunk/screenshot-1.jpg?rev=1539293","caption":"How the quote appears on a website"},"2":{"src":"https://ps.w.org/imperfect-quotes/trunk/screenshot-2.jpg?rev=1539293","caption":"Manage the quotes on the admin page"},"3":{"src":"https://ps.w.org/imperfect-quotes/trunk/screenshot-3.jpg?rev=1539293","caption":"Add a thumbnail to your quote"}},"tags":{"imperfect":"imperfect","imperfect-quotes":"Imperfect Quotes","quote":"quote","quotes":"quotes","widget":"widget"},"versions":{"0.9.0":"https://downloads.wordpress.org/plugin/imperfect-quotes.0.9.0.zip","0.9.1":"https://downloads.wordpress.org/plugin/imperfect-quotes.0.9.1.zip","0.9.3":"https://downloads.wordpress.org/plugin/imperfect-quotes.0.9.3.zip","trunk":"https://downloads.wordpress.org/plugin/imperfect-quotes.zip"},"donate_link":"http://www.swarmstrategies.com/imperfect-quotes","icons":{"default":"https://s.w.org/plugins/geopattern-icon/imperfect-quotes.svg"}}]

Overview

Summary of services

Summary of features

Highly secured payment technologies

Worry-free shopping

CVV2/CVC2 online verification

3D secure standards

Minimum Requirements

Automatic installation

Manual installation

Updating

6.3.2

6.3.1

6.3.0

6.2.12

6.2.11

6.2.10

6.2.9

6.2.8

6.2.7

6.2.6

6.2.5

6.2.4

6.2.3

6.2.2

6.2.1

6.2.0

6.1.3

6.1.2

6.1.1

6.1.0

6.0.14

6.0.13

6.0.12

6.0.11

6.0.10

6.0.9

6.0.8

6.0.7

6.0.6

6.0.5

6.0.4

6.0.3

6.0.2

6.0.1

6.0.0

\nWhy aren’t my images lazy loading?\n

\nWhat is the Blurhash placeholder feature, and how do I use it?\n

\nThere’s a plugin called Lazy Load XT. Why does this one look a bit similar?\n

\nWhy is this plugin called lazysizes, the same as the JS library it uses?\n

1.3.3

1.3.2

1.3.0

1.2.1

1.2.0

1.1.0

1.0.0

0.3.0

0.2.0

0.1.3

0.1.2

0.1.1

0.1.0

2.0 Beta 15.0 (October 07, 2016)

2.0 Beta 13.0 (March 29, 2016)

2.0 Beta 12.0 (February 9, 2016)

2.0 Beta 11.0 (January 25, 2016)

2.0 Beta 10.0 (January 11, 2016)

2.0 Beta 9.0 (December 11, 2015)

2.0 Beta 8.0 (December 1, 2015)

2.0 Beta 7.0 (November 17, 2015)

2.0 Beta 6.0 (November 12, 2015)

2.0 Beta 5.0 (October 23, 2015)

2.0 Beta 4.0 (August 14, 2015)

2.0 Beta 3.0 (July 1, 2015)

2.0 Beta 2.0 (May 28, 2015)

2.0 Beta 1.1

2.0 Beta 1 (April 28, 2015)

Installation Instructions

Features

imperfect

PlatiOnline Payments

lazysizes

WordPress REST API (Version 2)

Imperfect Quotes

Get New Themes & Resources