I have discovered an issue relating to the case of file extensions for FileListingPage and Gallery page types.
If the file extension is lowercase (ie. jpg), all works fine.
However, if the file extension is uppercase (ie. JPG) this reports errors:
(1) When calling the page:
[User Error] Uncaught Exception: Object->__call(): the method 'loaduploaded' does not exist on 'Image'
(2) When calling the image directly (http://www.domain.com/assets/gallery/image.JPG):
Page Not Found (this is caused by the .htaccess rule protecting the assets folder using FilesMatch
Is this working as intended or should this be logged as a bug?