Skip to content
Get started
Browse the documentation

WordPress requirements and compatibility

What your WordPress site needs before you connect it: version, PHP, HTTPS, a reachable address, permissions and the things that block a connection.

  • WordPress
  • 3 min read
  • Updated October 15, 2026
On this page

The WordPress connector is a plugin called Freakedout Content Uploader CSV & Excel Import. Its entry in the WordPress menu is Settings → Content Uploader. Check these requirements before you install it; almost every connection problem comes from one of them.

Requirements#

Requirement Detail
WordPress 6.6 or later. Tested up to 7.1.
PHP 8.1 or later on the site.
Address The site is served over HTTPS, at a public address, on the standard port (443). It must not be a development machine or an intranet address, and it must not be reachable only over IPv6.
Account A WordPress administrator (the capability manage options) starts the connection.
Single site Multisite networks are not supported. The plugin refuses to activate on one.
Outgoing requests The site can make outgoing HTTPS requests. Images are delivered by your site downloading them from Content Uploader's storage.
WooCommerce Optional. With WooCommerce 9.0 or later the shop's products are offered too (WooCommerce requirements).

You do not need pretty permalinks. The plugin talks to WordPress through the address form index.php?rest_route=…, which works with any permalink setting.

What can get in the way#

These are the usual causes of a connection that cannot be completed. Whether one of them applies to your site depends on how it is hosted:

  • A security or firewall plugin (or a web application firewall in front of the site) that blocks requests to the WordPress REST API from unknown servers. The connector can only be reached through the REST API.
  • HTTP authentication or an IP allow-list in front of the whole site, which stops Content Uploader from reaching it.
  • A redirect on the site's address, for example from https://example.com to https://www.example.com. Content Uploader does not follow redirects, so use the address WordPress itself reports as its home URL.
  • A staging site hidden behind a login wall, for the reasons above.

If the connection fails, troubleshooting the WordPress connection works through them in order.

Permissions#

The connector is never signed in to your site; each request is checked against the permissions of the administrator who approved the connection, limited to content. If an item is not offered in Content Uploader (a content type, a custom field, the ability to upload images), the most likely reason is that the connecting account may not do it. Permissions and authentication explains the details.

Compatibility with other plugins#

Content Uploader writes content through WordPress's own functions, so plugins that hook into saving a post (SEO plugins, translation plugins, cache purgers) normally run as they do when an editor saves. A side effect such a plugin has, for example sending an email when a post is published, can happen for every item written, and again if a failed operation is retried: Content Uploader guarantees that a retry never creates a second item, but it cannot control what other plugins do when they run.

Custom fields are WordPress post meta. A plugin that stores its data in post meta (many do) can be filled by naming the meta key when you map custom fields. A plugin that keeps its data somewhere else cannot.

The plugin's name#

In WordPress the plugin is listed as Freakedout Content Uploader CSV & Excel Import, in the folder freakedout-content-uploader-csv-excel-import.

Was this article helpful?

Related articles