WordPress.org

Plugin Directory

Test out the new Plugin Directory and let us know what you think.

JSON Content Importer

Plugin to import, cache and display a JSON-Feed / JSON-API: Connect your WordPress to an API / Webservice and display live JSON-data.

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

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

Requires: 3.0 or higher
Compatible up to: 4.7.1
Last Updated: 1 month ago
Active Installs: 1,000+

Ratings

5 out of 5 stars

Support

6 of 10 support threads in the last two months have been marked resolved.

Got something to say? Need help?

Compatibility

+
=
Not enough data

1 person says it works.
0 people say it's broken.

100,1,1 100,1,1 100,2,2 100,1,1 100,1,1
100,1,1 100,1,1 100,1,1
100,1,1 100,2,2 100,1,1 100,2,2
100,1,1 100,1,1
100,1,1
100,1,1
100,2,2 100,1,1 100,1,1 100,1,1 100,2,2
100,1,1
100,1,1
100,1,1 100,1,1
100,1,1 100,1,1
100,1,1
100,1,1
100,1,1
100,1,1 100,1,1
100,1,1
100,1,1