This repository is no longer maintained. Issue reports and pull requests will not be attended. You are welcome to fork the repository if you'd like though.
Yii2 Wordpress is a component for Yii2 framework designed for integration with Wordpress CMS via XML-RPC API.
This component is built on top of Wordpress XML-RPC PHP Client by Hieu Le Trung.
- Yii 2.0
- PHP 5.4
- PHP extension XML-RPC
The preferred way to install this extension is through Composer.
Either run
php composer.phar require monitorbacklinks/yii2-wordpress "dev-master"
or add
"monitorbacklinks/yii2-wordpress": "dev-master"
to the require
section of your composer.json
file.
In order to use this extension, first thing you need to do is to create a blog
(you can change the name if you want)
component and configure it. Here is the example of minimal configuration (in your config/main.php
):
'components' => [
...
'blog' => [
'class' => '\monitorbacklinks\yii2wp\Wordpress',
'endpoint' => 'http://example.com/xmlrpc.php',
'username' => 'demo',
'password' => 'demo'
]
...
]
When component is configured, you can start making requests to your Wordpress site.
For example, get ten latest published posts. Select guid
, post_title
and post_content
fields only:
$blogPosts = Yii::$app->blog->getPosts([
'post_status' => 'publish',
'number' => 10
], ['guid', 'post_title', 'post_content']);
Or create a new post with title "New post" and content "Hello world!":
$postID = Yii::$app->blog->newPost('New post', 'Hello world!');
Making API calls to an external application means delays. If you don't want your users to wait for a Wordpress response each time, caching is a right thing to do:
// The user profile will be fetched from cache if available.
// If not, the query will be made against XML-RPC API and cached for use next time.
$profile = Yii::$app->blog->cache(function (Wordpress $blog) {
return $blog->getProfile();
});
In case, if you need something more complex, you can disable caching for some requests:
$blogPosts = Yii::$app->blog->cache(function (Wordpress $blog) {
// ... queries that use query cache ...
return $blog->noCache(function (Wordpress $blog) {
// this query will not use query cache
return $blog->getPosts();
});
});
Caching will work for data retrieval queries only. Queries that create, update or delete records will not use caching component.
string
Wordpress XML-RPC API endpoint URL.
string
Wordpress authentication username.
Please note, that any actions made by XML-RPC will be made on behalf of this user.
string
Wordpress authentication password.
array
Proxy server configuration.
This configuration array should follow the following format:
proxy_ip
: the ip of the proxy server (WITHOUT port)proxy_port
: the port of the proxy serverproxy_user
: the username for proxy authorizationproxy_pass
: the password for proxy authorizationproxy_mode
: value for CURLOPT_PROXYAUTH option (default to CURLAUTH_BASIC)
Empty array means that no proxy should be used.
Default value: []
.
array
Server HTTP authentication configuration.
This configuration array should follow the following format:
auth_user
: the username for server authenticationauth_pass
: the password for server authenticationauth_mode
: value for CURLOPT_HTTPAUTH option (default to CURLAUTH_BASIC)
Empty array means that no HTTP authentication should be used.
Default value: []
.
boolean
Whether to catch exceptions thrown by Wordpress API, pass them to the log and return default value,
or transmit them further along the call chain.
Default value: true
.
boolean
Whether to enable query caching.
Default value: true
.
integer
The default number of seconds that query results can remain valid in cache.
Use 0 to indicate that the cached data will never expire.
Default value: 3600
.
Cache|string
The cache object or the ID of the cache application component that is used for query caching.
Default value: 'cache'
.
The full list of available methods can be found in Wordpress XML-RPC PHP Client Class Reference.
Please note, that all those methods are throwing an exceptions in case of any errors.
While this extension is configured (by default), in case of errors, to return an empty array for any data retrial
methods and false for any create, update or delete methods. Please see $catchExceptions
configuration option for details.
There are a lot of things that can go wrong (network problems, wrong Wordpress user permissions, etc.).
If $catchExceptions
configuration option is set to true
(default value), this extension will catch them and pass to
monitorbacklinks\yii2wp\Wordpress::*
logging category.
In order to see them, you can configure your Yii2 log
component to something similar to this:
'components' => [
...
'log' => [
'targets' => [
'file' => [
'class' => 'yii\log\FileTarget',
'levels' => ['error'],
'categories' => ['monitorbacklinks\yii2wp\Wordpress::*'],
],
],
],
...
]
- Report any issues on the GitHub.
yii2-wordpress is released under the MIT License. See the bundled LICENSE.md
for details.