@frontity/wp-source
API reference of `@frontity/wp-source` package
This package is in charge of getting the data from self-hosted WordPress or WordPress.com sites, and make it available from our React components.
Add the
wp-source package to your project:npm i @frontity/wp-source
Both of the starter themes (
@frontity/mars-theme & @frontity/twentytwenty-theme) available when doing npx frontity create already include this wp-source package.This package needs to be included in your
frontity.settings.js file as one of the packages that will be part of the Frontity project:module.exports = {
packages: [
"@frontity/mars-theme",
"@frontity/tiny-router",
{
name: "@frontity/wp-source",
state: {
source: {
url: "https://wpsite.com/",
},
},
},
],
};
These are the settings you can configure for this package in your
frontity.settings.js file:We recommend you to check the guide Setting the URL of the WordPress data source to get a more practical explanation of how to properly set the URL of the WordPress data source by using the properties of this package and taking into account the different WordPress scenarios.
The URL of your WordPress backend installation. The default value of this property is derived from
state.frontity.url.Example:
// frontity.settings.js
export default {
packages: [
{
name: "@frontity/wp-source",
state: {
source: {
url: "https://test.frontity.org",
},
},
},
],
};
If you are using Embedded Mode for your Frontity project, and the
state.frontity.url property is set, you do not have to also set the state.source.url property as this will be the same as the value in the state.frontity.url property.The URL of your WordPress REST API endpoint.
From version 1.10 of the
@frontity/wp-source package, the property state.source.api should never be set manually by the end-users (it will be computed from properties like state.source.url or state.wpSource.isWpCom).Check the guide Setting the URL of the WordPress data source to understand the computed values of
state.source.api for every WordPress scenario.Boolean value to indicate if the WordPress installation used as the source of data is a Personal or Premium WordPress.com plan.
This value will be
false by default and will be automatically computed to true if needed in most of the cases.This property only needs to be set manually to
true if you're using a Personal or Premium WordPress.com plan.Check the guide Setting the URL of the WordPress data source to understand the value of this property depending on the WordPress scenario.
Example:
// frontity.settings.js
export default {
packages: [
{
name: "@frontity/wp-source",
state: {
source: {
url: "https://test-premium-plan.frontity.org",
},
wpSource: {
isWpCom: true,
},
},
},
],
};
By using this property you can specify the prefix of your REST API, for example
"/wp-json" or "?rest_route=/". The default value is "/wp-json".This option should only be set if you have changed the path to the REST API endpoint in your WordPress installation. If you have not done that or you're not sure what it means, you can safely ignore this option.
A name or path indicating the subdirectory of your domain where your Frontity site lives. For example, if your site is in https://mysite.com/blog, you have to use it with the value of
blog or /blog. It also transform links of the entities that come from the REST API.This option allows you to show a specific page when accessing the homepage of your site. For example, if you set this value to
/about-us then that page will be shown if you access /.You have to configure your WordPress with the same setting.
As this option overrides the
/ route, you should set state.source.postsPage as well in order to be able to access the posts archive in a different route.This option allows you to show the posts archive when accessing a specific URL of your site, instead of the homepage. For example, if you set this value to
/blog, then the posts archive will be shown if you access /blog instead of /. It is useful when used in combination with state.source.homepage.You have to configure your WordPress with the same setting.
Change the base prefix of URLs for category pages with the indicated one.
For this option to work well, you have to put the same value in the WordPress site options.
Change the base prefix of URLs for tag pages with the indicated one.
For this option to work well, you have to put the same value in the WordPress site options.
Set the endpoint against which calls to the REST API are made when posts are requested, i.e. when fetching a single post, the post archive, date archives, categories, tags, authors, etc. This is useful when you want to use another post type as your default, for example “products”.
The default value is
"posts".Object of params that will be used in every call to the WP REST API when using
actions.source.fetch. This is useful to filter fields from the REST API, change the default per_page value and so on. For example, if you set this value tomodule.exports = {
packages: [
{
name: "@frontity/wp-source",
state: {
source: {
api: "https://site.com/wp-json",
params: {
per_page: 5,
type: ["post", "page"],
},
},
},
},
],
};
and then you visit a URL (or use
actions.source.fetch), the query part of the HTTP call to the REST API will be per_page=5&type[]=post&type[]=page.This option is a property which can hold authentication information. This could be a JWT token or a Basic Authentication string, or another type of authentication.
Values can be passed to
state.source.auth in a variety ways, e.g. via frontity.settings.js or by setting it in the way that any other piece of frontity state is.// frontity.settings.js
const state = {
source: {
auth: "Basic YWFhOmJiYg",
},
};
Additionally the value of
state.source.auth can be set via a query string. If a frontity_source_auth Frontity Query Option param is present in the URL state.source.auth will use its value. Values passed in this way will be removed from the initialLink URL and added to state.frontity.options.Note that the Frontity Query Option parameters are camelCased when they are added tostate.frontity.options, so thefrontity_source_authquery string param will becomestate.frontity.options.sourceAuthonce added.
The value of
state.source.auth can also be set from an environmental variable. If frontity detects a FRONTITY_SOURCE_AUTH environmental variable, it will pass its value to state.source.auth.Note that the value passed from the URL query string takes precedence over the value from the env variable.Frontity loads environmental variables from .env files using the https://github.com/motdotla/dotenv/ package.
Crucially,
state.source.auth is removed in the afterSSR() action, so if state.source.auth is present in the state on the server its value will not be sent to the client, thus confidential credentials are not revealed client-side.Via this
wp-source package, Frontity has support for 3xx Redirections that are stored in the WordPress database. Such redirections can be added for example via the popular Redirection plugin.Through the property
state.source.redirections we can configure how we want to handle the redirections. This property can have one of the following values:"no"- Does not handle the redirections at all. This is the default.-
"404"- Only send the additional request to the WordPress instance if the original request has returned a 404 error. -
"all"- Always make an additional request to the WordPress instance to check if there exists a redirection. This means that for every singleactions.source.fetch()there will be a parallel request to the WordPress server that is fired "just in case" theactions.source.fetch()returns a 404. If theactions.source.fetch()is successful, the result of fetching the redirection is discarded. Ifactions.source.fetch()fails, Fronity waits for the response from fetching the redirection and if that is successful, uses its result. string- A string that contains a regex pattern. The string must start with"RegExp:". This pattern will be matched against the current route and if matched, Frontity will make an additional request to the WordPress instance to check if there exists a redirection. Note that the shorthand character classes will have to be escaped, so for example instead of\d, you will need to write\\d.string[]- An array of strings, which can contain the"404"value as well as any number of strings starting with"RegExp:/"which represent regular expressions. An additional request will be sent to Wordpress to check for the redirection if any of the regular expressions match the current route. If the array also contains a"404", an additional request will also be made if the original request has returned a 404 error.
Some example valid values are:
"no""all""404""RegExp:/some-post/(\\d*)""RegExp:/post-(\\w*)/(\\d*)"["404", "RegExp:/some-post/", "RegExp:/another-post"]
This option allows you to show the Custom Post Types you create at WordPress when accessing their URLs. It is an array of objects, each object being a different CPT. It has three arguments:
Name | Type | Required | Description |
type | string | yes | The slug you configured for your Custom Post Type |
endpoint | string | yes | REST API endpoint from where this post type can be fetched. |
archive | string | no | the URL of the archive of this Custom Post Type, where all of them are listed. |
Differentiating
type and endpoint may be confusing as they are usually the same. You can confirm you are doing it correctly going to the CPT endpoint :
So in this case, the settings would be:
postTypes: [
{
type: "movies",
endpoint: "movies",
archive: "/movies_archive",
},
];
Similar to
postTypessetting, this one allows you to show the lists of posts of a Custom Taxonomies you create at WordPress when accessing their URLs. It is an array of objects, each object being a different Custom Taxonomy. It has four arguments:Name | Type | Required | Description |
taxonomy | string | yes | Taxonomy slug. The slug you configured for your Custom Taxonomy. If your taxonomy is registered with a rewrite, use that instead. |
endpoint | string | yes | REST API endpoint from where this post type can be fetched. |
postTypeEndpoint | string | no | REST API endpoint from which posts of this taxonomy can be fetched. If the Custom Taxonomy is meant to load Custom Post Types instead, you have to add its endpoint here. To clarify, although optional for posts in the case of a Custom Post Type this argument is required. Default value is posts |
params | object | no | Extra params to be used while fetching the list of posts. |
Differentiating
taxonomy and endpointmay be confusing as they usually are the same too. You can confirm you are doing it correctly by going to the Custom Taxonomy endpoint :
Note that in this case
taxonomyand endpointare different. In the next example, we will fetch CPT "movies" instead of "posts", and add some params. It would be something like this:taxonomies: [
{
taxonomy: "actors",
endpoint: "actor",
postTypeEndpoint: "movies",
params: {
per_page: 5,
_embed: true,
},
},
];
This package will automatically retrieve data from the related WordPress routes when accesing a React route.
The
@frontity/wp-source package requires pretty permalinks to be enabled on the WordPress admin. For more info check the guide WordPress requirements for Frontity.The data got from WordPress REST API is organized and normalized in the state. This "normalization" of the data means the data is organized in the state in a way so there's no duplicated data in it and there's only one source of truth.
The state works with two main concepts: links and entities.
The state is designed so that you can know which entities correspond to which link, and then access the data of these entities in a simple way.
Because of this there's a 2 step process to get the information from a link:
- 1.Get the data related to the link
- 2.Get the data related to the entities available in that link
For the data to exist, it will be necessary to request them previously using the
fetch action.import React, { useEffect } from "react";
import { connect } from "frontity";
// In a React component that uses "connect":
const CategoryNature = ({ state, actions }) => {
// 1. fetch data related to a path
// With this useEffect we make the call to fetch
// only the first time the component is rendered.
// When the data is fetched, the state is updated with the new data
// so the component is re-rendered and "data" will get proper content
useEffect(() => {
actions.source.fetch("/category/nature/");
}, []);
// 2. get data from frontity state
const data = state.source.get("/category/nature/");
// 3. get entities from frontity state
if (data.isCategory) {
// the category entity
const category = state.source.category[data.id];
// posts from that category
const posts = data.items.map(({ type, id }) => state.source[type][id]);
// 4. render!
return (
<>
<h1>{category.name}</h1>
{posts.map((p) => (
<a href={p.link}>{p.title.rendered}</a>
))}
</>
);
}
return null;
};
export default connect(CategoryNature);
If you want to know more about how to use the
wp-source package, here you have some videos where the Frontity DevRel team talks about it:The
wp-source package implements the interface defined in the source package and adds some extra API.Actions don't return data. Data is always accessed via the state. That's because Frontity is following the Flux pattern (like Redux).
This action fetches all entities related to a
link, i.e. the pathname of a URL in your site.It populates the state with both:
- An entry in
state.source.datawith information about that link. - Normalized entities in relevant part of the state, like
state.source.post,state.source.categoryorstate.source.authorand so on.
Syntax
(link: string, options: object) => Promise`
Arguments
Name | Type | Required | Description |
link | string | yes | Link representing a REST API endpoint or custom handler |
options | object | no | REST API endpoint from where this post type can be fetched. |
options.force | boolean | - | The entities should be fetched again. |
Return value
Type | Description |
Promise | it doesn't return data but a promise that is resolved when the action is finished (and state is updated) |
All received data are populated in
state.source and are accessible using the methods explained in the next section.actions.source.fetch("/category/nature/");
Even though actions don't return data, they return a promise that resolves when the action is finished.
So, you can do something like this:
await actions.source.fetch("/some-post");
which is useful when you need to access the new state just after calling the action:
await actions.source.fetch("/some-post"); // <- Wait until we fetch "/some-post".
const somePost = state.source.get("/some-post"); // <- The data will exist.
In React components, you won't need to use
async/await with fetch because:- They re-render when the
stateaccessed changes.
const SomePost = ({ actions, state }) => {
useEffect(() => {
// No need to use `async/await` here
actions.source.fetch("/some-post");
}, []);
// The data will not exist at first, `dataPost.isReady` will be false.
// But then, it will rerender when `actions.source.fetch` is finished.
const dataPost = state.source.get("/some-post");
// This will work just fine.
return dataPost.isReady ? <Post link="/some-post" /> : <Loading />;
};
When
fetch is called again for the same link it does nothing, as all the entities have already been fetched and there is no need to request them again. If you do want to fetch them again, you can pass an options object to source.fetch with force: true:actions.source.fetch("/category/nature/", { force: true });
The use of
actions.source.fetch() is recommended over other isomorphic methods to fetch data such as axios or superagent, because:- 1.It does not increase the bundle size
- 2.It prevents Frontity projects from having duplicated libraries doing the same job
The use of
actions.source.fetch() is also recommended over window.fetch because although window.fetch exists in the browser it is not isomorphic and doesn't exist in Node.Relationship with state.router.autoFetch
Every time you go to a new link from the Client Side (by using
actions.router.set for example) a new fetch should be done for that new link so the data of that link is properly populated to the state.Thanks to the settings property
state.router.autoFetch with a default value of true, every time you browse to a new page (Client Side Navigation) the fetch of the data in that page will we done automatically for you.Have a look at this video to learn more about this:
Returns an object that gives you info about the type of that link and related entities.
Syntax
(link: string) => object`
Arguments
Name | Type | Required | Description |
link | string | yes | Link representing a REST API endpoint or custom handler |
Return value
Type | Description |
object | Info about the type of data represented in the URL |
For exampe:
state.source.get("/category/nature/");
will return something like:
{
// Entity properties.
taxonomy: "category",
id: 7,
link: "/category/nature/page/3?s=park",
query: {
s: "park"
},
// Booleans that identify the type of link.
isArchive: true,
isCategory: true,
isTaxonomy: true,
// Booleans that show the fetch status.
isFetching: false,
isReady: true,
// Archive properties.
items: [{ type: "post", id: 60, link: "..." }, ...],
total: 53,
totalPages: 6,
page: 3,
route: "/category/nature",
next: "/category/nature/page/4?s=park",
previous: "/category/nature/page/2?s=park",
// Search properties.
isSearch: true,
searchQuery: "park",
}
The information to distinguish each type of link is based on the WP Template Hierarchy and is as follows:
- archives:
isArchive- taxonomy:
isTaxonomy- category:
isCategory - tag:
isTag - deal:
isDeal
- author:
isAuthor - postTypeArchive:
isPostTypeArchive- post:
isHome,isPostArchive(isFrontPageoptional) - product:
isProductArchive
- date:
isDate
- postTypes:
isPostType- post:
isPost - page:
isPage(isFrontPageoptional) - product:
isProduct - media:
isMedia,isAttachment
- 404:
is404
Additionally, if calling
get() has returned a status code higher than 400, we add information about the error to the state. For example, if an error code was 500, the state will include the following properties:{
isError: true,
is500: true,
errorStatus: 500,
errorStatusText: "Some string describing the error",
// booleans that describe the fetch status
isReady: true,
isFetching: false
}
- taxonomy:
taxonomy,id - author:
id - postTypeArchive:
type - date:
year,month,date - postType:
type,id
Access category, tag, or custom taxonomy’s entities. These entities have the same schema as specified in the WP REST API.
We are actually changing the WP REST API response, but only for tags, in which we are replacing the
taxonomy value from post_tag to tag.source.category[2]
source.tag[13]
source.deal[3]
Access posts, pages, attachments or custom post type’s entities. These entities have the same schema as specified in the WP REST API.
source.post[60]
source.page[7]
source.product[36]
source.author[4]
Request entity from the WordPress REST API.
Syntax
(options: object) => Promise;
Arguments
Name | Type | Required | Description |
options | object | yes | options object |
options.endpoint | string | yes | Name of the endpoint if is a /wp/v2 endpoint (e.g. posts), or the full path of other REST endpoints (e.g. /acf/v3/posts). |
options.params | object | no | Any parameter that will be included in the query params. |
options.auth | string | no | Allows the Authorization header on the fetch() request to be set. If not specified, will use the value from state.source.auth if that value is present in the state. |
options.api | string | no | Overrides the value set with api.set. |
options.isWpCom | boolean | no | Overrides the value set with api.set. |
Return value
Type | Description |
Promise | it doesn't return data but a promise that is resolved when the action is finished (and state is updated) |
Example
const { api } = libraries.source;
// Get posts from categories 2, 3 and 4
const postsCategories = await api.get({
endpoint: "posts",
params: { _embed: true, categories: "2,3,4" },
});
// Get the page 14
const page14 = await api.get({
endpoint: "pages",
params: { _embed: true, include: "14" },
});
// Other endpoints:
const postBeautiesGullfoss = await api.get({
endpoint: "/acf/v3/posts",
params: { slug: "/the-beauties-of-gullfoss" },
});
Add entities to the Frontity state.
(options: object) => Promise;
Arguments
Name | Type | Required | Description |
options | object | yes | Options object |
options.response | object | yes | The response object returned by api.get(). |
options.state | object | yes | The state object from the Frontity store. |
options.subdirectory | string | no | Domain's subdirectory where your Frontity site is accessible. When this options is passed, this subdirectory is added to the entities' links. </br> Default Value is value defined in state.source.subdirectory |
options.force | boolean | no | Value indicating if the entities should be overwritten </br> Default Value is false |
Return value
Type | Description |
Array | An array of objects with attributes type, id and link representing the added entities. |
Entities are normally never overwritten. So, if an entity already exists in the state and a new one is fetched, the one in the state will prevail. If you want to overwrite them,
populate should be called with force: true.Example
const response = await libraries.source.api.get({ endpoint: "posts" });
const entitiesAdded = await libraries.source.populate({ response, state });
entitiesAdded.forEach(({ type, id, link }