Developer Tools

Unmaintained Developer Tools 1.4.3

No permission to download
  • New: Button to clear email logs (#90)
  • Change: Options, Permissions and Style Properties are now grouped in the output rather than displaying group inline (#88)
  • Change: Increase mails per-page to 100 (#89)
  • Fix: Fix newline printing literally in the resulting Markdown code (#88)
  • Fix: Cron entries that use "Day of the week" run schedule will now correctly generate readme entries (#87)
  • Like
Reactions: Masetrix
  • New: Arguments must now be passed to tck-devtools:build-readme in order to build any of the 3 different output formats
  • New: A new argument can be passed to tck-devtools:build-readme in order to copy the resulting file to the _no_upload directory
  • New: Support for @Xon's require-soft recommendations parameter in addon.json
  • Change: Stop building readme when building add-on (#83)
  • Fix: Suppress DOM errors when attempting to convert markdown to HTML (#81)
  • Fix: Potential server error when attempting to copy files
  • Fix: Error with building the list of requirements if the version was * instead of an array
Some of the contributions were made by @DragonByte Tech
  • New: Allow viewing HTML and text sent via emails (#78)
  • Love
Reactions: Masetrix
  • Change: Disable polyfill for JsMinifier closure (#74) (Thanks @DragonByte Tech)
  • Fix: Argument 2 passed to TickTackk\DeveloperTools\Listener::dispatcherPostRender() must be of the type string, null given (#73)
  • Like
Reactions: Masetrix
  • Change: Apply default sort order for entities that are fetched when building README files (#71)
  • Fix: Style property description is same as title in README file (#67)
  • Fix: CLI command tck-devtools:build-readme does not have descriptive description (#69)
  • Fix: CLI command tck-devtools:add-phrase does not have description (#70)
  • Love
Reactions: unmöglichefirmen
  • New: Handle in-line code tags when building README files (#64)
  • Change: The .idea directory will now be excluded by default when building add-on release archive (#63)
  • Change: Do not try to autodetect google closure compiler (#66)
  • Fix: Excluded directories are not respected when building add-on release archive (#62)
  • Like
Reactions: otto and Masetrix
  • New: CLI Command to create README file (#57)
    • The following information will be available in README with description whenever possible:
      • Add-on title
      • Add-on description
      • Add-on requirements
      • Options
      • Permissions
      • Admin permissions
      • BB codes
      • BB code media sites
      • Style properties
      • Advertising positions
      • Widget positions
      • Widget definitions
      • Cron entries
      • REST API scopes
      • CLI Commands
    • Further more, you can add your own blocks by creating HTML files named after the hook positions:
      • BEFORE_TITLE
      • AFTER_TITLE
      • BEFORE_DESCRIPTION
      • AFTER_DESCRIPTION
      • BEFORE_REQUIREMENTS
      • AFTER_REQUIREMENTS
      • BEFORE_OPTIONS
      • AFTER_OPTIONS
      • BEFORE_PERMISSIONS
      • AFTER_PERMISSIONS
      • BEFORE_ADMIN_PERMISSIONS
      • AFTER_ADMIN_PERMISSIONS
      • BEFORE_BB_CODES
      • AFTER_BB_CODES
      • BEFORE_BB_CODE_MEDIA_SITES
      • AFTER_BB_CODE_MEDIA_SITES
      • BEFORE_STYLE_PROPERTIES
      • AFTER_STYLE_PROPERTIES
      • BEFORE_ADVERTISING_POSITIONS
      • AFTER_ADVERTISING_POSITIONS
      • BEFORE_WIDGET_POSITIONS
      • AFTER_WIDGET_POSITIONS
      • BEFORE_WIDGET_DEFINITIONS
      • AFTER_WIDGET_DEFINITIONS
      • BEFORE_CRON_ENTRIES
      • AFTER_CRON_ENTRIES
      • BEFORE_REST_API_SCOPES
      • AFTER_REST_API_SCOPES
      • BEFORE_CLI_COMMANDS
      • AFTER_CLI_COMMANDS
    • When an add-on is built, following README variants will be created:
      • BB code version at _dev/resource_description.txt for resource descriptions
      • Markdown version at README.md for any VCS repository
  • Change: Increase minimum XenForo version requirement to 2.1.7 (#59)
  • Change: Increase minimum PHP version requirement to 7.3 (#60)
  • Fix: When creating code event listener method, passed by reference state is not respected (#58)
  • Like
Reactions: otto
  • New: Show callback execution order in code event listener list (#51)
  • New: Allow clamping versions via CLI (#52) (Thanks @Xon)
  • Change: Make execution order selectable in class extensions select (#50)
  • New: Show warnings when attempted to check for permissions or permission groups that do not exist (#34)
  • New: Allow creating permission via permission interface even if permissions already exist (#35)
  • New: Show class extension execution order in the list (#43)
  • New: Show template modification execution order (#44)
  • Fix: Upgrading to 1.1.0 does not migrate markdown files correctly (#45)
  • Fix: Certain CLI commands have wrong namespace (#46)
  • Fix: Doc block is before namespace instead of before class (#47)
Top Bottom