Jetpack and XML-RPC

Posted on February 21, 2023 by Kyle Smith

XML-RPC is a communication protocol that Jetpack uses to connect your site to WordPress.com. Learn more about XML-RPC and how it powers Jetpack.

What is XML-RPC?

XML-RPC is a protocol that allows communication between your website and external servers. Jetpack uses this protocol to connect your site to WordPress.com. WordPress’s core software has had XML-RPC support since WordPress version 3.4 and is considered a stable tool. You can learn more about WordPress’s XML-RPC API and how it can be leveraged in the WordPress.org developer resources.

How does XML-RPC work?

With Jetpack, your site becomes an XML-RPC server, so that WordPress.com can communicate with while it establishes a connection to WordPress.com. Similar to other API implementations, it requires a preset list of procedures that can be called remotely, as well as a specific list of data it can provide.

Is XML-RPC deprecated?

Although XML-RPC has lost popularity, it’s still widely used. While newer APIs are often built upon other standards like REST or GraphQL, XML-RPC is integrated into a large number of existing systems, so it’s not going anywhere anytime soon.

Is XML-RPC removed from PHP?

The PHP (PECL) XML-RPC extension provides functionality to simplify development of XML-RPC APIs. Beginning with PHP 8.0, the extension is no longer bundled into PHP and needs to be installed separately.

Jetpack does not use this extension. Jetpack sites are not affected by this change. Jetpack includes its own implementation of XML-RPC that does not rely on this PHP extension.

What security concerns are there with using XML-RPC?

Just like most technologies, it’s neither secure nor vulnerable by itself. It all depends on the particular implementation, and Jetpack provides the most secure way to use it.

Typical integrations with an XML-RPC API send a username and password in plain text to facilitate communication between your website and the service leveraging it. This does make the use of this API less secure. However, Jetpack’s XML-RPC integration is different.

How is Jetpack’s XML-RPC integration different?

Jetpack doesn’t send a username and password through any API to connect your site to WordPress.com. Our connection method is different in that we use a token-based system, similar to OAuth. This means that instead of sending a username and password, Jetpack generates a special string called an API signature, which gets attached to all API requests. Before sending the request, the API signature gets encoded using a secret token.

Think of the secret token like a cipher used to turn a message into a secret code. First, the message sender uses that cipher to turn the message into a secret code. Then the message receiver, who also has access to the cipher, can use it to translate the secret code back into the original message. Jetpack’s usage of XML-RPC works very similarly.

The only place that the secret token (a.k.a. the cipher) exists is on your Jetpack site and on the WordPress.com server that your site communicates with. This means that even if the API request were to be intercepted along the way, there wouldn’t be a way to decode the API signature because decoding that API signature requires access to the secret token.

This approach is considered universally safe and reliable, and is in use by other API standards, including REST.

Graphic representation of the XML-RPC process used by Jetpack to integrate with your site.

What benefits are there to using XML-RPC over the REST API?

For Jetpack, it’s all about stability. Continuing to use XML-RPC means that users who are on older versions of Jetpack can still leverage the features of Jetpack. While we strongly recommend keeping your Jetpack plugin up to date, we understand that isn’t always possible. We don’t want to abandon our users on older versions of the plugin, so we intend to stick with XML-RPC for as long as we can.

If at some point in the future we have to make the transition to the REST API, we will communicate this transition to our users prior to the switch.

Still need help?

Please contact support. We’re happy to advise.

Comments Off on Jetpack and XML-RPC

Add Jetpack IPs to an Allowlist

Posted on December 7, 2021 by bob matyas

Control who can (or cannot) access your website by allowing IP addresses in WordPress.

Make sure Jetpack can access your site so that we can run backups, security scans, and restore it back to a previous version.

Allow all communications between Jetpack and WordPress.com

If you want to ensure Jetpack can communicate with your site, or if you have been advised to allowlist our IPs by support, please allow these IP ranges:

Jetpack IPs

[ip_ranges service=jetpack format=html version=ipv4]

Important: These IP addresses are subject to change. If you are writing IP-based firewall rules, you’ll need to update those rules any time the addresses change. We also have machine-readable versions of these IP ranges in JSON and plain text format that you can use to automate configuration changes on your systems.

A note about xmlrpc access

Some hosts and plugins believe that blocking access to xmlrpc.php will stop various hacking attempts. However, XML-RPC support has been built into WordPress core since version 3.5 and is a stable tool. Jetpack, like other plugins, services, and mobile apps, relies on the XML-RPC file to communicate with WordPress.com. If this is blocked, your Jetpack connection will stop working properly. You can read more about how Jetpack uses xmlrpc.php.

You should be able to protect a site’s XML-RPC file without having to allow specific IP ranges. The most popular hosts use tools like fail2ban or ModSecurity, for example.

Use Jetpack with Cloudflare (no additional security rules)

By default, Cloudflare and Jetpack should require no additional configuration to operate together if there are no additional security configurations specified with Cloudflare.

Use Jetpack with Cloudflare (additional security rules) and Sucuri

If you are using Cloudflare (with additional security rules) or Sucuri, please manually add Jetpack’s IPs.

If you are using Cloudflare they also support only allowing traffic coming from servers with a specific ASN (autonomous system number). To configure that, you can allow access to 2635.

  • 192.0.64.0/24
  • 192.0.65.0/24
  • 192.0.66.0/24
  • 192.0.67.0/24
  • 192.0.68.0/24
  • 192.0.69.0/24
  • 192.0.70.0/24
  • 192.0.71.0/24
  • 192.0.72.0/24
  • 192.0.73.0/24
  • 192.0.74.0/24
  • 192.0.75.0/24
  • 192.0.76.0/24
  • 192.0.77.0/24
  • 192.0.78.0/24
  • 192.0.79.0/24
  • 192.0.80.0/24
  • 192.0.81.0/24
  • 192.0.82.0/24
  • 192.0.83.0/24
  • 192.0.84.0/24
  • 192.0.85.0/24
  • 192.0.86.0/24
  • 192.0.87.0/24
  • 192.0.88.0/24
  • 192.0.89.0/24
  • 192.0.90.0/24
  • 192.0.91.0/24
  • 192.0.92.0/24
  • 192.0.93.0/24
  • 192.0.94.0/24
  • 192.0.95.0/24
  • 192.0.96.0/24
  • 192.0.97.0/24
  • 192.0.98.0/24
  • 192.0.99.0/24
  • 192.0.100.0/24
  • 192.0.101.0/24
  • 192.0.102.0/24
  • 192.0.103.0/24
  • 192.0.104.0/24
  • 192.0.105.0/24
  • 192.0.106.0/24
  • 192.0.107.0/24
  • 192.0.108.0/24
  • 192.0.109.0/24
  • 192.0.110.0/24
  • 192.0.111.0/24
  • 192.0.112.0/24
  • 192.0.113.0/24
  • 192.0.114.0/24
  • 192.0.115.0/24
  • 192.0.116.0/24
  • 192.0.117.0/24
  • 192.0.118.0/24
  • 192.0.119.0/24
  • 192.0.120.0/24
  • 192.0.121.0/24
  • 192.0.122.0/24
  • 192.0.123.0/24
  • 192.0.124.0/24
  • 192.0.125.0/24
  • 192.0.126.0/24
  • 192.0.127.0/24

Strict Firewall Configurations and Jetpack Boost

If you are using Jetpack Boost features alongside strict firewall rules, you will need to grant exceptions for Fly.io Hosting Provider Sub-processors. To take full advantage of all Jetpack Boost features, ensure the ASN for each of Fly.io’s Hosting Providers are added to an allowlist. At present those include CacheNetworks, Equinax, NetActuate, and OVH. If Fly.io adds new hosting providers, you can use PeeringDB.com to locate the ASNs to add to the allowlist.

Still need help?

Please contact support. We’re happy to advise.

Comments Off on Add Jetpack IPs to an Allowlist
Code Snippets plugin

Add PHP Code Without Editing Files

Posted on December 21, 2017 by Emily Axel

Want to add a code snippet without having to edit your theme’s functions.php file? Use a functionality plugin instead.

Editing your theme’s functions.php file carries the risk of breaking the rest of the code in the file and also opens you to the potential that the code will be lost when you update your theme. Instead, you can safely add code snippets using a plugin.

There are several functionality plugins available in the WordPress.org repository. The instructions below explain how to install and use Code Snippets.

  1. Go to Plugins → Add New and install and activate the plugin. This will add a Snippets item to your wp-admin dashboard menu.
  2.  Navigate to Snippets → Add New. 
  3. Enter a title.
  4. Paste or type your code in the Code field
  5. Click Save Changes and Activate.

Still need help?

Please contact support. We’re happy to advise.

Comments Off on Add PHP Code Without Editing Files

Safe Mode

Posted on November 21, 2016 by bob matyas

Use Safe Mode in Jetpack to prevent issues when switching between development, staging, and production environments. Ensure continuity and prevent an “Identity Crisis” by maintaining consistent site data.

You can also prevent losing your production site data by mistake by using the WP environment variable.

Identity crisis explained

In short, an “Identity Crisis” happens when changing a URL causes Jetpack to create a new ID instead of updating the old one, leading to an apparent loss of valuable historical data and subscriber information.

When a website using Jetpack connects to WordPress.com, it receives a unique ID and token tied to the site URL. This ID functions much like a username and password, identifying the site within our system. The ID is important because it keeps track of data like site stats and subscriber lists.

Problems can occur if the site’s URL changes. Ideally, the system should update the existing blog ID with the new URL, keeping all historical data connected to the site. But sometimes the system sometimes doesn’t recognize the new URL as an updated address for the same site, or a site with multiple domains. Instead, it treats the new URL as a completely different site and assigns a new ID.

This causes an “Identity Crisis.” The original site’s data—such as site statistics, visitor counts, and subscriber information—stay linked to the old ID and appear to be lost. The new ID starts tracking from zero, making it seem that the site’s history has been erased. This is a problem for site administrators who rely on consistent tracking of site performance and audience engagement.

How Safe Mode helps

Safe mode helps prevent these problems before they start.

There are several cases where your Jetpack-enabled site’s URL could change:

  • Updating to a new domain.
  • Cloning a site from production to staging.
  • Using multiple URLs for the same installation.
  • Any other scenario where the URL of your site might change.

In most cases, we can safely update the URL and not cause an Identity Crisis. But, there are a handful of cases where we’re not able to automatically determine whether we should update the URL in our data caches.

In these cases, Jetpack takes some extra steps to make sure that we’re not causing an Identity Crisis:

  • We don’t allow syncing any more information from the Jetpack-enabled site to the WordPress.com caches.
  • We begin displaying the Jetpack Safe Mode notice.
  • We continue showing that notice until an admin of your site resolves the potential Identity Crisis.

Safe Mode notice and actions

Safe Mode Notice:

When the notice is first displayed, you’ll see something like this:

Looking at the above screenshot, there are three actions you can take:

  1. Move your settings:
    • Use when replacing an old URL with a new one (e.g., moving from a development to a production environment).
    • Migrates stats and subscribers to the new URL.
    • The notice disappears after migration is complete.
  2. Create a fresh connection:
    • Use when creating a new, separate site.
    • Starts a new Jetpack connection process for the new site.
    • Redirects to WordPress.com for authorization.
    • Useful for full Jetpack functionality on a development site.
  3. Stay in Safe Mode:
    • Use when cloning for testing.
    • Keeps the site in Safe Mode and hides the notice.
    • The “Jetpack Safe Mode” button in the admin bar reopens the dialog if needed.

Safe Mode and Staging Mode

Jetpack’s Staging Mode is for sites known to be in a staging environment. When enabled:

  • Staging sites do not pass data to WordPress.com or Jetpack.
  • Prevents conflicts with the production site.

If a staging site is not set correctly, Safe Mode will be triggered.

Summary

  • Safe Mode: Prevents data loss when changing site URLs and offers options to manage these changes.
  • Staging Mode: Ensures staging sites are unable to take over the production site data.

Safe Mode and Staging Mode helps maintain site integrity and avoid an Identity Crisis during transitions between different environments.

Still need help?

Please contact support. We’re happy to advise.

Comments Off on Safe Mode

Features Included in the Core Jetpack Plugin

Posted on July 11, 2016 by Ashley

With the core Jetpack plugin, you can access a range of free and paid features that enhance your WordPress site to elevate your online presence.

Free features in the Jetpack core plugin

Security

Performance

  • JSON API — Authorizes applications and services to securely connect to your blog, and allows them to use your content or offer you new functionality.
  • Site Accelerator — Helps your pages load faster by allowing Jetpack to optimize your images and serve your images and static files (like CSS and JavaScript) from our global network of servers.

Management

  • Gravatar Hovercards — Make your Gravatar profile visible to those viewing your blog.
  • Plugin Management — Allows you to choose which plugins update automatically.
  • Repeat Visitor Block — Enables the author to control the visibility of its nested block(s) depending on how many times a visitor has previously visited the page.
  • Notifications — Receive notifications for new comments and Likes in your admin bar and on your mobile device.

Growth

  • Enhanced Distribution — Allows your content to be included in the WordPress.com “firehose” of public blog content.
  • Likes — Allows readers to show their appreciation for your posts with a single click.
  • SEO Tools — Optimize your site for search engines by taking advantage of our SEO tools.
  • Sharing — Adds sharing buttons to your blog posts so readers can easily share your content.
  • Site Verification — Verify your site for use with Google, Bing, and Pinterest and their tools.
  • Sitemaps — Generate a list of pages to be indexed by search engines like Google or Bing.
  • Subscriptions (Classic Editor) / Subscription Form Block — Allow visitors to receive notifications of your latest posts or comments.
  • Related Posts (Classic Editor) / Related Posts Block — Show contextual posts your visitors might be interested in reading after they’re done with their current post.
  • Comments — Replace your default comment form with an improved system with integrated social media login options.
  • Comment Likes — Allows readers to like other comments to show their agreement, approval, or appreciation.

Create

  • Business Hours Block — Allows you to display your business’s opening hours on your site.
  • Carousel — Display a gorgeous full-screen photo browsing experience with comments and EXIF metadata.
  • Contact Info Block — Lets you add your contact information (email address, physical address, phone number) to any post or page.
  • Contact Form (Classic Editor) / Form block — Offer your readers the ability to get in touch, without giving out your personal email address.
  • Custom Content Types — Adds custom post types (CPTs) to your site.
  • Extra Sidebar Widgets — Extra widgets you can add to your blog, including RSS Links, Twitter Timelines, and Facebook Like Boxes.
  • GIF Block — Allows you to easily search for and embed an animated GIF image from Giphy directly into a post or page on your WordPress site.
  • Infinite Scroll — Pulls the next posts automatically into view when the reader approaches the bottom of the page.
  • Map Block — Allows you to add a map to any post or page on your site.
  • Markdown (Classic Editor) / Markdown Block — Allows you to compose posts and comments with links, lists, and other styles using regular characters and punctuation marks. Markdown is used by writers and bloggers who want a quick and easy way to write rich text without having to take their hands off the keyboard.
  • Post by Email — Publish posts using any email client.
  • Shortcode Embeds — Embed videos from YouTube, tweets from Twitter, and other media across the web.
  • Slideshow Block — Lets you insert an image slideshow into a post or page. 
  • Star Rating Block — Allows any site author to add reviews to the site
  • Tiled Galleries (Classic Editor) / Tiled Galleries Block — Display your image galleries in three different styles: a rectangular mosaic, a square mosaic, and a circular grid.
  • WP.me Shortlinks — Generate short and simple links to your content using the wp.me domain.
  • Widget Visibility — Configure widgets to appear only on specific pages.
  • Backups — Save every change and get back online quickly with one‑click backup restores.
  • AI Assistant — The most powerful AI tool for WordPress.
  • Jetpack Social — Share new posts on social media networks automatically or schedule future shares with custom messages.
  • Payments — Add a payment button specifically for recurring donations, using Stripe as the payment gateway.
  • Security Scanning — Anti-virus, malware, and threat detection for your WordPress site with automated resolution.
  • Search — A powerful replacement for WordPress’ built-in search, powered by Elasticsearch in the WordPress.com cloud
  • Simple Payments Block — Lets you add a payment button to any post or page, and immediately start accepting PayPal payments for physical products, digital goods, or donations.
  • Site Stats — View site visits by date, as well as most popular Pages and Posts.
  • Spam Filtering — Automatically filter out spam comments, product reviews, or contact form submissions.
  • Video Hosting (Classic Editor) / VideoPress Block — Upload videos for fast, reliable hosting on WordPress.com.
  • WordAds — Monetize your site by displaying high-quality ads on your site.

Many Jetpack features related to content are available as blocks. For a complete list, visit our Jetpack Blocks page.

Still need help?

Please contact support. We’re happy to advise.

Comments Off on Features Included in the Core Jetpack Plugin

Staging Sites

Posted on February 19, 2016 by stefmattana

Safely use Jetpack with a staging site.

When you make a copy of your site for testing or development, Jetpack checks the WP_ENVIRONMENT_TYPE variable in the wp-config.php file. Read more on how to configure this variable.

This is a feature used by many plugins and web hosts. If the variable is set to staging or development, Jetpack will turn off the option to move site settings to the test site. This helps protect the live site from any changes made in the test environment.

Note: This guide is for online staging sites. If you have a local offline development site, please follow the Offline Mode guide instead.

Recommended workflow between staging and production sites

Manual process

In terms of a workflow between your production and staging sites, we’d advise the following:

  1. Migrate the database from your production to staging site.
  2. Make sure to flag the staging site with WP_ENVIRONMENT_TYPE. 
  3. At the “Safe Mode” prompt, click “Create a fresh connection”.
  4. Make your changes on the staging site.
  5. Migrate your changes back to your production site.
  6. When you access your WP Admin on your production site, click “Create a fresh connection” when the “Safe Mode” prompt displays.
  7. Since this is a “new” site, click the button “Create a fresh connection”. This will restore the old connection on the production site.

Automated process

Ask your hosting provider if they automatically set the WP_ENVIRONMENT_TYPE. If so, you can use the steps below:

  1. Clone to Staging.
  2. Staging site will enter “Safe Mode”.
  3. Create a fresh connection.
  4. Make changes to the staging site.
  5. Move to production.
  6. On production, you will get the “Safe Mode” warning again.
  7. Create a fresh connection since this is now a “new” connection compared to the staging environment.

Use staging mode

When your Jetpack site is accessed in staging for the first time, you will get a “Safe Mode” warning when Jetpack notices that the staging site is a copy of your production site.

There are three options:

  1. Move Jetpack data from your production site to the staging site (not available if the site marked as staging via WP_ENVIRONMENT_TYPE )
  2. Treat each site as independent sites, creating a fresh Jetpack connection
  3. Decide later and stay in Safe Mode, best used when:
    • site is created for short-term testing and will be deleted soon
    • site will be cloned back to production after testing

Jetpack features that do not work in Safe Mode

Re-enable connection migration

If the site is using the WP_ENVIRONMENT_TYPE set to staging, but you need to enable connection migration anyway, use a filter:add_filter( 'jetpack_is_development_site', '__return_false);

The code can be added to any existing plugin or via Code Snippets or a similar plugin.

Still need help?

Please contact support. We’re happy to advise.

Comments Off on Staging Sites

Manage Jetpack via WP-CLI

Posted on June 24, 2015 by Emily Axel

Learn to manage Jetpack via the WP-CLI commands and configure your Jetpack options and features.

Jetpack has built-in support for WP-CLI, allowing you to modify your Jetpack installation with just a few commands. You’ll need SSH access and a basic understanding of command-line tools.

Main commands

  • wp jetpack
  • wp jetpack status [<full>]
  • wp jetpack module <list|activate|deactivate|toggle> [<module_name>]
  • wp jetpack options <list|get|delete|update> [<option_name>] [<option_value>]
  • wp jetpack protect <whitelist> [<ip|ip_low-ip_high|list|clear>]
  • wp jetpack reset <modules|options>
  • wp jetpack disconnect <blog|user> [<user_identifier>]

wp jetpack status

wp jetpack status [<full>]

With this command, you get the details about your Jetpack setup.

  • wp jetpack status : get basic Jetpack details.
  • wp jetpack status full : get full details, including the Jetpack version, WordPress version, and more.

wp jetpack module

wp jetpack module <list|activate|deactivate|toggle> [<module_name>]

Interact with individual modules via this command: you can Activate, Deactivate, Toggle, and List.

  • wp jetpack module list : list all modules and their status (Activated or Deactivated).
  • wp jetpack module activate stats : will activate the Stats module.
    • wp jetpack module activate all : will activate all modules.
  • wp jetpack module deactivate stats : will deactivate the Stats module.
    • wp jetpack module deactivate all : will deactivate all modules.
  • wp jetpack module toggle stats : will toggle the Stats module on/off.

wp jetpack options

wp jetpack options <list|get|delete|update> [<option_name>] [<option_value>]

This is the command to manage the Jetpack options.  You can list all your Jetpack options and their values, get individual option values, update some options, and delete non-essential ones.

  • wp jetpack options list : list all Jetpack options and their values.
  • wp jetpack options get <option_name> : get the value of a specific option.
  • wp jetpack options delete <option_name> : delete a specific option, but only those not essential to your connection to WordPress.com.
  • wp jetpack options update <option_name> <option_value> : update an option with a new value. Please note that it only works for string option values.

wp jetpack reset

wp jetpack reset <modules|options>

This command resets your Jetpack environment to its default state. You can reset all Jetpack options or revert to the default active modules.

  • wp jetpack reset modules : resets modules to default active state.
  • wp jetpack reset options : resets options to default state, as if you just connected for the first time.  Please note that it also resets modules to default.

wp jetpack disconnect

wp jetpack disconnect <blog|user> [<user_identifier>]

You can disconnect Jetpack from WordPress.com or unlink a user’s account from their WordPress.com connection.

  • wp jetpack disconnect blog : will disconnect Jetpack from WordPress.com.
  • wp jetpack disconnect user <id|email|username> : will unlink their user account from WordPress.com.

wp jetpack protect

wp jetpack protect <whitelist> [<ip|ip_low-ip_high|list|clear>]

Allowlist an IP address from Protect with this command.

  • wp jetpack protect whitelist list : will list your current allowlist.
  • wp jetpack protect whitelist clear : will clear your current allowlist.
  • wp jetpack protect whitelist <ip_address> : allowlist a single IP address.
  • wp jetpack protect whitelist <ip_low-ip_high> : allowlist a range of IP addresses.

Still need help?

Please contact support. We’re happy to advise.

Comments Off on Manage Jetpack via WP-CLI

Jetpack for developers

Posted on November 7, 2013 by Emily Axel

If you’re a developer, Jetpack includes tools to extend and customize Jetpack to fit your needs.

Work in your local environment with Jetpack

When working on a theme or a plugin in your local environment, you can enable the Jetpack Development mode to use features that do not require a connection to the WordPress.com servers.

To use Jetpack in Development mode, you can add the following code to your wp-config.php file:

define( 'JETPACK_DEV_DEBUG', true );

Learn more about Jetpack Development mode.

Your themes and Jetpack

When developing a new theme, you can include several features that come bundled with Jetpack:

You can also use this dependency script to inform your users that their theme relies on certain Jetpack features and help them install or activate them as needed.

Your plugins and Jetpack

If you’re working on a WordPress plugin, check our tips and tricks for interacting with the Jetpack plugin. We also have instructions on how to use the Code Snippets plugin along with Jetpack.

Integrate WordPress with Jetpack

The JSON API module allows you to build a link between WordPress and your applications.

Klout and StackEdit are examples of apps that can interact with your Jetpack site through the JSON API module.

Contribute to Jetpack

If you want to help us build Jetpack and improve and contribute to the plugin, follow our contributor guide.

Still need help?

Please contact support. We’re happy to advise.

Comments Off on Jetpack for developers

Offline Mode

Posted on November 6, 2013 by shaylynnm

Offline Mode lets you work on your site locally and avoid connection issues when there is no internet connection. This feature is primarily for developers who want to build and test sites in offline or unstable environments.

Note: This is specifically for offline, local development sites. If you have an online, staging site, please follow the Staging Sites guide instead.

Enabling Offline Mode in your local environment

You can enable some of the Jetpack features on your localhost by activating the Offline Mode. Here is how:

  1. Turn on Offline Mode by adding define( 'JETPACK_DEV_DEBUG', true ); to your wp-config.php file.
  2. Make sure you add it before the /* That's all, stop editing! Happy blogging. */ line.

Offline mode may be automatically enabled if you don’t have a period in your site’s hostname, i.e. localhost. If you use a different URL, such as mycooltestsite.local, then you will need to define the JETPACK_DEV_DEBUG constant.

You can also enable Jetpack’s Offline Mode through a plugin, thanks to the jetpack_development_mode filter:

add_filter( 'jetpack_offline_mode', '__return_true' );

Limitations of Jetpack on local installations

Please keep in mind:

  • While in Offline Mode, some features will not be available at all, as they require WordPress.com for all functionality—Related Posts and Jetpack Social, for example.
  • Paid features do not work in Offline Mode. You will not be able to activate a license on a localhost, even in the Offline Mode.
  • Other features will have reduced functionality to give developers a good-faith representation of the feature. For example, Tiled Galleries requires the WordPress.com image CDN. In Offline Mode, Jetpack provides a fallback so developers can have a similar experience during development and testing.

Jetpack features that will not work in Offline Mode

In localhost installations, these are the features that will not work. If you need to test these features, please set up an online staging site instead:

Still need help?

Please contact support. We’re happy to advise.

Comments Off on Offline Mode

JSON API in the Jetpack plugin

Posted on November 5, 2013 by Emily Axel

Authorize applications and services with Jetpack by using the JSON API feature. Securely connect to your blog and allow them to use your content in new ways.

Once you connect Jetpack to your site, the JSON API is enabled by default. For detailed instructions on deactivating it or ensuring it is active, please visit Control Jetpack’s Features on One Page.

JSON API for developers

Developers can manage and access the website’s content using WordPress.com’s OAuth2 authentication system and WordPress.com REST API.

Custom post types, custom taxonomies and JSON API

The JSON API feature does support custom post types and custom taxonomies, but you need to take some steps to make it work smoothly.

You can follow the instructions in this post to add Custom Post Type and metadata support to your site. You can also learn more about the API by visiting the REST API documentation.

Still need help?

Please contact support. We’re happy to advise.

Comments Off on JSON API in the Jetpack plugin

  • Enter your email address to receive news and updates from Jetpack

  • Join 99.1K other subscribers

  • Browse by Topic