Skip to content

Prevent exception on usage reports, file extension fallbacks
Compare
Choose a tag to compare
@mabolek mabolek released this 06 May 13:46
· 20 commits to master since this release
v1.0.2
49e8acd
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

BUGFIXES

  • If no URL to where a file is used can be generated during usage reporting, an empty string will be used. This fixes an issue where adding an image to a record on a page outside of a site or within a folder would throw an exception, for example when adding an image to a frontend user.
  • Introduces configuration option qbankBrowserAllowed, a comma-separated list of file extensions similar to TYPO3 core's elementBrowserAllowed. If this option is not set, elementBrowserAllowed will be used. (See TCA Reference)
  • Allowed image extensions falls back to the default image extensions ($GLOBALS['TYPO3_CONF_VARS']['GFX']['imagefile_ext']) if qbankBrowserAllowed or elementBrowserAllowed is not set.
  • The "Use media from QBank" selector button is hidden if access token has not been set. This is instead of an exception.
Assets 2
Loading