Registro de cambios

1.3.12

• Importaint speed-up Bugfix for JCI-Gutenberg-Block! If you run your WordPress with Gutenberg-Blocks (no ClassicEditor-Plugin active) several unneeded libraries are loaded (independend of using a JCI-Block or not). This slows the site and gives bad load-ratings e. g. at Googles Pagespeed ( https://developers.google.com/speed/pagespeed/ ). With this fix the unneeded libraries are not loaded any more and the load-rating should be better.
• Background-Check for allow_url_fopen in Plugin Options: If allow_url_fopen is not set to TRUE in the PHP-Settings, this might prevent PHP and the plugin to get JSON via http-requests from remote servers (if there no red text, all is ok)
• Plugin Ok with WP 5.6.1

1.3.11

• Internationalization added: Available languages are English, German. Feel free to add other languages!
• Shotcodeparam nojsonvalue: If «nojsonvalue=y» the API-Answer is available as {nojsonvalue}, helpful if the API answer is not JSON
• Plugin Ok with WP 5.6

1.3.10

• Bugfix if subloop’s have several unreplaced {…} items
• Plugin Ok with WP 5.5.1

1.3.9

• Bugfix if a JSON-field is not always there or null (loop stopped if so)
• Placeholders for template: If you want to have curly or square brackets {}[] in the template, this can trouble the shortcode-syntax or the template-parser. Use the placeholders #CBO# (curly brackets open), #CBC# (curly brackets close), #SBO# (square brackets open) and #SBC# (square brackets close) in the template, the placeholders will be replaced by it’s bracket-values in the end after parsing.
• Plugin ok with WP 5.4.2

1.3.8

Compatibility fix: Plugin is now Ok with PHP 7.4

1.3.7

• New Option: If a http-API request fails, you can use the maybe cached JSON. Set the radio-button in the plugins settings: what API-problem should be handled how (either a non valid API-http-response or a non JSON-API-response – or both). By default for backwards-compatibility this is switched off. Recommendation: Switch on the plugins-cacher (e. g. some minutes) and select the radiobutton for «If the API-http-answercode is not 200 OR sends invalid JSON: try to use cached JSON» in the plugins options.

1.3.6

• Bugfix: Add Gutenberg-JS only in the backend (before it was also in the frontend)

1.3.5

• New: Added a Quicktag to the WordPress-Text-Editor to insert the JSONContentImporter-Shortcode incl. an example

1.3.4

• New Plugin-Option: Switch off Gutenberg features (maybe a site builder needs that)

1.3.3

• Bugfix of Bugfix, sorry…

1.3.2

• Bugfixes: detect Gutenberg and WordPress 5.0

1.3.1

• Bugfixes

1.3.0

• Plugin is ok with the Gutenberg Plugin 3.9.0
• Gutenberg-Mode: With an active Gutenberg Plugin you get an easy example for testing and learing how to use the plugin. If you don’t want to use Gutenberg on live-stage: Use it to easy create the shortcode (almost avoid the learning of the shortcode-parameter-syntax)

1.2.20

• Plugin is ok with WordPress 4.9.8
• Plugin is ok with the Gutenberg Plugin 3.6.2
• Plugin is ok with the General Data Protection Regulation (GDPR): The plugin does not collect personal data itself. You may list the plugin in your GDPR-documentation as used software. Maybe the used API uses personal data – then you have to take care of the GDPR.
• Improved debugmode (use debugmode=10 in the shortcode for that)
• Changed the Videolink to a better HowTo-Video
• Added upgradelink to pro plugin in PluginList

1.2.19

• Plugin is ok with WordPress 4.9.1
• Adding «debugmode=10» to the Shortcode parameters will show you info about the API-JSON-retrieve and the used template for converting to HTML.
• Ever since the plugin uses the PHP function «mb_check_encoding» to detect a maybe needed character-conversion. Unfortunately some WordPress/PHP-installations do not have the PHP-optional «Multibyte String»-library required for that. Then the plugin does not work. Now the availablility of «mb_check_encoding» is checked: If it’S not there the conversion-feature is disabled.
• At the Plugin-options you can set a «Bearer»-accesskey for oAuth-Bearer-Authentication. The there defined accesskey-string is sent to the API as «Authorization:Bearer accesskey». Some APIs just need «Authorization:accesskey». So «Bearer » should not sent. To do this add «nobearer » (with one space at the end) at the beginning of the option-field.

1.2.18

• Plugin is ok with WordPress 4.7.5
• New option: Add Default Useragent for http-request (some APIs need that)

1.2.17

• Plugin is ok with WordPress 4.7
• https instead of http for Plugin-Website
• Remove invalid quotation marks in shortcode-attributes (when copypasting example code this can happen)

1.2.16

• Plugin is ok with WordPress 4.6.1
• Plugin is ok with PHP 7.0
• Cleaner Code

1.2.15

• Plugin is ok with WordPress 4.5.2
• Added features for coming future addons

1.2.14

• Plugin is ok with WordPress 4.5
• Improved description

1.2.13

• Caching-Bug Fixed: WordPress 4.4.2 does not create a «/cache/» folder. If «/cache/» is missing, the plugin creates on. This is relevant for totally new WordPress installations, as older ones should have such a directory.

1.2.12

• Plugin is ok with WordPress 4.4
• minor change: prevent direct calls of plugin
• bug fixed: path of cached files is now set ok

1.2.11

• bugfix: problems with numeric JSON-values and field manipulators like {JSONkey:ifNotEmptyAdd:….}
• beta feature Vers. 0.2: Fixed bug in using oAuth-Bearer-Accesscode for authentification at JSON-Server: Bearer-Code is added to the Request-Header.

1.2.10

• bugfix: caching now works even with very long URLs
• beta feature: On the Optionpage you can set an oAuth-Bearer-Accesscode for authentification at JSON-Server: This Bearer-Code is added to the Request-Header.

1.2.9

• new: «{street:purejsondata}»: Default-display of a datafield is NOT HTML, but HTML-Tags are converted. If you want to use really the pure data from the JSON-Feed, add «:purejsondata». Try first {street}, then {street:html} and then {street:purejsondata}. In some cases: Take care that «meta http-equiv=content-type…» is set to «utf-8»

1.2.8

• bugfix: handling of JSON-values with $

1.2.7

• WordPress 4.3.1: check – all ok
• bugfix: correct encoding of spaces when using {FIELD:html}
• bugfix: deleting unfilled template-items containing dots

1.2.6

• WordPress 4.3: check – all ok
• added feature: remove unfilled template-placeholders {…}
• introducing «JSON Content Importer PRO»

1.2.5

• WordPress 4.2.3: check
• minor bugfix regarding attribute «ifNotEmptyAddRight»
• new Pluginwebsite: http://json-content-importer.com/

1.2.4

• «&» in JSON-Feed-URLs are replaced by «&»

1.2.3

• added a donated feature: new shortcode-params «oneofthesewordsmustnotbein», «oneofthesewordsmustnotbeindepth». This is for excluding JSON-data from display: When one of the «,»-separated keywords at «oneofthesewordsmustnotbein» is found in the textblock, ignore this textblock

1.2.2

• minor bugfix: JSON-Structures like { «$a»: «$b»} can be handled (before: «$» made problems)

1.2.1

• new feature «{street:htmlAndLinefeed2htmlLinefeed}»: Text-Linefeeds of JSON-data are converted to HTML-Linefeeds
• Boolean JSON-Values were ignored before this version. Now the text «true» or «False» is displayed
• Bugfixing Cacher: Timeout-Parameter of cache was not handled right
• Fixed a bug with JSON-Value containing «$»

1.2.0

• new shortcode-parameter: «oneofthesewordsmustbein» and «oneofthesewordsmustbeindepth»
• filter & hook for third party extensions added: hook «json_content_importer_extension» and filter «json_content_importer_result_root»
• Sourcecode: Classes rearranged
• minor bugfix: number of items in subloop/subloop-array was sometimes ignored and all was displayed
• «made in munich» added (see faq)

1.1.2

• Bugfix: tags like «{aa/aa}» are ok (previous: error)
• Display JSON-HTML-Data really as HTML. Default: JSON-HTML-Data is displayed not as HTML but as HTML-Text. New in this version: tag-sytax like «{tag:html}» or «{street:html,ifNotEmptyAddRight:extratext}» allows real HTML-display.
• New parameter in «[jsoncontentimporter]»-shortcode: set http-timeout «urlgettimeout». default is 5 seconds (ueful if source-website of JSON is slow)
• Logo of plugin: WordPress-Logo inserted
• Update of screenshots

1.1.1

Bugfixes

1.1.0

Completely rewritten template engine for even better JSON-handling:

• «subloop-array»: key should also be in the closing tag, e.g. «{subloop-array:KEY:10}{some_array_field}{/subloop-array:KEY}».
  The «subloop-array» without KEY in the closing tag is ok if there is only one «subloop-array» in the template. But if there are more than one «subloop-array» in the template insert the KEY in the closing tag!
  Then the template engine can identify the correct JSON-data.

• «subloop»: what is above for «subloop-array» is also for «subloop», e.g. «{subloop:KEY:10}{some_object_field}{/subloop:KEY}»

• templates like «{subloop-array:AAAA:10}{text}{subloop:AAAA.image:10}{id}{/subloop:AAAA.image}{/subloop-array:AAAA}» are possible:
  one is the recursive usage of «subloop-array» and «subloop».
  the other is «{subloop:AAAA.image:10}» where «AAAA.image» is the path to an object.

• JSON-data with multiple use of arrays can be handled by the template engine

1.0.5

• Added Screenshots
• Enhanced «subloop-array», new processing of pure string/numeric-array data (before: only string/numeric-data in an object)
• Enhanced FAQs: Added Link to Website for better creating shortcode-markups

1.0.4

Bugfixes

1.0.3

Enhanced the template engine for better JSON-handling.

1.0.2

Initial release on WordPress.org. Any comments and feature-requests are welcome: blog@kux.de