Ember Wordpress is an addon for ember-cli that makes it easy to fetch data from the Wordpress API (WP-API) in your Ember sites. It includes an application adapter, serializer as well as some default models: post, page, category and tag.
Note, the demo API sometimes goes to sleep. Please open an issue if so.
A few sites using ember-wordpress:
- https://www.alivefestival.dk, http://pfadfinderei.com, http://magnus-winter.de, http://kunstjagd.com and yours?
- Run
ember install ember-wordpress
- Define where your Wordpress installation is:
// config/environment.js
...
ENV.emberWordpress: {
host: 'https://my-wordpress-site.com'
}
On a version before 2.0.1? Use ENV.wordpressHost
instead.
You'll have seven models ready out of the box: wordpress/post
, wordpress/page
, wordpress/category
wordpress/tag
, wordpress/attachment
, wordpress/comment
, wordpress/user
.
Note: the wordpress/post
and wordpress/page
models are identical and so are wordpress/category
and wordpress/tag
. For your own custom post types, it is recommended to extend the post
model:
// app/models/recipe.js
import DS from 'ember-data';
import PostModel from 'ember-wordpress/models/post';
export default PostModel.extend({
ingredients: DS.attr()
});
If you're using the ACF plugin your custom fields will be at model.get('acf.myCustomField')
.
Since Wordpress version 4.7 the REST API is included in core Wordpress. If you are on an earlier version you will need to install the WP API v2 plugin, which also works fine.
After installing, create some posts or pages in Wordpress and see your data at example.com/wp-json/wp/v2
.
If you're having CORS trouble: WP-CORS If you want custom fields: Advanced Custom Fields and ACF To REST API
To use a custom post type together with the WP API you have to be aware of two additional arguments, when you define them.
show_in_rest
must be set to true.rest_base
will be the endpoint of your post type. Sset it to the plural form of your model, as this is what Ember expects. E.g. the endpoint for arecipe
post type should berecipies
and notrecipe
.
Here's a full example. You could save this file as wp-content/plugins/my-custom-post-types.php
.
<?php
/*
Plugin Name: My custom post types
Author URI: https://github.com/oskarrough/ember-wordpress/
*/
function artist_post_type() {
$labels = array(
'name' => 'Artists',
'singular_name' => 'Artist',
'menu_name' => 'Artists',
);
$args = array(
'labels' => $labels,
'show_in_rest' => true,
'rest_base' => 'artists',
);
register_post_type('artist', $args);
}
add_action('init', 'artist_post_type');
?>
The WP API supports many arguments that you can use but it's not super friendly so here are some tips.
By default the WP API returns a maximum of 10 items. For instance, this.store.findAll('post')
would return 10 posts. To change that we need to find the right argument and endpoint. Looking at the documentation for WP API we find per_page
. It could look like wp-json/wp/v2/posts?per_page=99
which translates into the ember-data query this.store.query('post', {per_page: 99})
.
- Endpoint:
wp-json/wp/v2/posts?slug=some-post-slug
- Query:
this.store.query('post', {slug: 'some-post-plug'}).then(models => models.get('firstObject'));
We take the first object because query
always returns an array and we expect our query to only return a single object.
To query posts by category slug you will need two queries.
First get the category id with the
- Endpoint:
wp-json/wp/v2/categories?slug=some-category-slug
- Query:
this.store.query('category', {slug: 'some-category-slug'}).then(models => models.get('firstObject'));
Then, get the posts
- Endpoint:
wp-json/wp/v2/posts?categories=category-id&per_page=99
- Query:
this.store.query('post', {per_page: 99, categories: category-id}).then(models => models.get('firstObject'));
Enable caching by installing the wp-rest-api-cache wordpress plugin.
To get server-side rendering, install Ember Fastboot. Here's a demo of the Ember Wordpress dummy app served by fastboot. You'll see the actual HTML rendered if you view the source. Ember Wordpress doesn't require anything special to make this work. Here's a small deployment tip.
By default, Ember loads every request to a record separately from the server. If you want to display a post and the names of all of it's tags for example, Ember will query the main post and every single tag. A post with five tags will result in six requests to the server.
Since Ember and WP-API supports loading of multiple resources of the same type in one request, you can opt-in to this feature:
var ENV = {
...
emberWordpress: {
coalesceFindRequests: true
}
...
With this option enabled, loading a post with five tags will result in just two requests, because all tags of the post will be loaded together. This can improve the load time of your Ember app a lot!
It's the goal of ember-wordpress to be the bridge between ember/ember-data and the official WP REST API. Ideally, in addition to the provided adapter, serializer and models, this readme and the project's demo app should serve as good examples. Please ask any questions here https://github.com/oskarrough/ember-wordpress/issues.