Mulitsite Installations?

The free version can be used on multisites: Their limited features has no effects on this.
With the PRO-Version you can store Templates in the database for using it on multiple pages / blogentries. As these Templates are stored site by site multisite Management comes into the game. PRO-Versions prior to 2.0.9 do not support multisite. Versions after 2.0.9 are multisite ready.

Thanks to Rod from Canada and Layth from Australia!

Documentation of JSON Content Importer PluginMulitsite Installations?

Version 3.4.13 (June 10 2019), see detail here (most changes are affecting generating Custom Post Types):

Customfields when generating Custom Post Types:
When defining Customfields in the shortcode with the parameter "createoptions" and it's JSON use this: "customfields": #BRO# {"extracustomfield1": "extravalue1"}, {"1#SEP#extracustomfield2": "extravalue2#SQM #SingleQuote#SQM#"}, {"2#SEP#extracustomfield2": "extravalue3"} #BRC#
#SQM# is the mask for single quotes, use "integer#SEP#" if you want to have idential keys in several Customfields (here: "extracustomfield2" is the key)
Date of generated Custom Post Types:
When defining Customfields in the shortcode with the parameter "createoptions" use "postdateoffset": "VALUE" to set the time and date of the generated Custom Post Fields.
If not set the current PHP-Servertime is used.
"VALUE" can be numeric: Then this number is subtracted from the current Servertime, e.g. one hour is 3600 seconds or 3600000 miliseconds.
"VALUE" can be "wptimezone": Then the in the Wordpress-installation defined timezone is used
"VALUE" can be a valid timezonestring
Delete of existing Custom Post Types when calling the generating Page (e.g. manually or by cronjob)
This can be configured by the parameter "deleteold" and the values for the "key" of each generated CPT. You have these options:
If "deleteold":"no" then no previous CPT is deleted, the new CPT are just added.
If "deleteold":"yes" then all CPT with the key defined for these CPT are deleted (twig-code in the key is not executed!)
If "deleteold":"some" the twig-code in the key is executed for each CPT. Those CPT are deleted when the result of the twig-key matches the key of the CPT.
The twig-key is defined at the JCIpro-Plugin-Options at tab "Custom Post Types" settings at ...;key={% if VALUE_FROM_JSON>0 %}date{{ ANOTHER_VALUE_FROM_JSON }} {% endif %}...
Bugfix when generating Custom Post Types: Handling of special chars and selecting Data out of JSON
Bugfix Debugmode-Messages: cleaned up when 2 or more JCI-Shortcodes are on one page
New Shortcode-Parameter: If "forcetemplate=1" then all settings from the JCI-Template are used (otherwise a parameter set in the Shortcode overwrites it´s template-parameter)

Version 3.4.12 (February 22 2019), see in detail here:

bugfix 1: Now you can use HTML-Entities in the Template-Code (before those were converted in the textarea), e. g. ">"
bugfix 2: Better Infomessage before the 1st Licence-Check is done
bugfix 3: Creating CustomPostTypes: If "deleteold" is not "yes", both old and new CPT are available. This previously didn't work as it should.
bugfix 4: Using Shortcode-Parameter "maskspecialcharsinjson=no" now really works as it should (importaint when special chars are in the JSON)
rearranged code for better handling (twig, cache, debug-messages)
plugin ok with wp 5.1

Related posts: