Shortcode changelog

Changelog History

• v0.7.4

  March 08, 2020

• v0.7.3 Changes

  December 03, 2019

  🛠 Fixed PHP 7.4 compatibility errors reported in #81 and #82.

• v0.7.2 Changes

  April 20, 2019

  🛠 Fixed #77, merged quality of life improvements from #73.

• v0.7.1 Changes

  February 03, 2019

  🛠 Fixed #74.

• v0.7.0 Changes

  December 18, 2018

  • 📜 many RegularParser improvements and fixes:
    • backtracks now rely on their offsets only, this is an over 10x performance and memory usage improvement which evens its performance with other parsers while still keeping its feature advantage,
    • subsequent non-token text fragments are now reported as single T_STRING tokens,
    • fixed #70, preg_match_all() with large inputs was sometimes silently failing and returning only subset of matches which reduced the number of reported shortcodes,
    • fixed #58 where invalid token sequences in shortcode content may confuse the parser,
    • inlined content() method effectively halving the call nesting level,
    • disabled xdebug.max_nesting_level during parse() to prevent development environment parsing errors,
  • 🌐 added support for PHPUnit 6.x with fallback translation for PHP 5.x compatibility,
  • 👍 dropped PHP 5.3 (still supported) and added PHP 7.2 from Travis matrix,
  • asterisk * is now a valid shortcode name,
  • minor internal Processor improvements,
  • ⚡️ minor README updates.

• v0.6.5 Changes

  January 08, 2017

  Extended parameter simple values possible value range, #44.

• v0.6.4 Changes

  December 13, 2016

  🛠 Fixed minor WordPress compatibility issue with content detection in WordpressParser.

• v0.6.3 Changes

  August 10, 2016

  🛠 Fixed bug happening when computing replacement of shortcode without handler that contained multibyte content.

• v0.6.2 Changes

  May 19, 2016

  🛠 Fixed issue with parsing shortcode tokens inside shortcode content.

• v0.6.1 Changes

  February 25, 2016

  🛠 Fixed bug with not recalculating new text length after applying shortcode replacement which caused the replacements to be applied only up to the length of source text. Thanks to @Jonatanmdez for reporting it in issue #37.