Free: Basic Settings
Video: Install JCI free
Check installed Plugin: All ok?
The free JCI plugin adds an entry into the admin menu. A click on it opens a page with several settings:
- Cacher:
The plugin can store answers from an API on the webserver to avoid unneeded, time and performance-consuming requests.
The cache folder will beWP_CONTENT_DIR/cache/jsoncontentimporter
SoWP_CONTENT_DIR/cache/
must be writable for the webserver. The plugin checks this and might abort with an error message like “dir is missing” or “dir is not writeable”. If this happens, check your directory permissions.
You can leave the Cacher switched off if you can’t do that (because your webserver-hoster does not allow that). - Handle unavailable APIs:
If the API is offline, the plugin can try to save this situation using cached data (even if the Cacher is switched off: if the Cacher was active before and created some cached data, this data is used). You have some options there.
Recommended (not switched on due to backward compatibility):
“If the API-HTTP-answer code is not 200 OR sends invalid JSON: try to use cached JSON.”
- API-Request:
Consult your API manual to see what the API expects!
The free Plugin sends a simple request to an URL. To this HTTP(s)-request, you can add Authentication-Info or a Browser-User-agent:- Authentication:
You can either send “Authorization: Bearer accesskey” where “accesskey” is the info you give on the plugins page (usually a long cryptic string). This is called “oAuth Bearer”.
OR:
If you use “nobearer accesskey” – mind the space! – the plugin sends “Authorization:accesskey” without “Bearer”. - User-Agent:
Some APIs expect a User-agent to identify whos calling.
If activated, the plugin sends “JCI WordPress-Plugin – Free Version.”
- Authentication:
- Gutenberg?
You might switch off the JCI-Gutenberg-Block (needed with some Pagebuilders). Read more on the JCI-Gutenberg-Block here.