1.7.0

Features:

• Support nextcloud 33

Fixes:

• Frame creation did not work under some server configurations, see #14

1.6.4

Bugfixes:

• Fixes an issue where albums containing more than 1000 images would fail for Oracle databases.

1.6.3

Photo frames urls can now be iframed from any domain.

1.6.2

Improves the display of photo place in older browsers with no support for "last baseline"

1.6.1

Minor improvements:

• On edit page, show disclaimer about photo place availability
• Improve look of capture date icon in edit page preview

1.6.0

Photo Frames can now show photo places.

The data is sourced from Nextcloud Photos, then Memories.
In my testing I found that Photos uses more fine-grained places, which works better for my own albums.

The data from Photos comes as a string and as such is not translatable.
Data from Memories can potentially be translated to the browser's language, I decided not to implement that just yet - let me know if you need it!

1.5.1

Improvements:

• Fixes potential "flashes" when transitioning between images.
  • This would happen if the rotation was "per minute" and it took more than 1 second to load the next image.
• Better performance when fetching metadata
  • Performance severely regressed after adding support for Memories (in 1.5.0) - which was likely the reason that the "flashing bug" was uncovered.
  • Now the performance hit should be negligible.

1.5.0

Photo Frames now reads metadata from the Memories app if possible.
Nextcloud's own metadata is used as fallback - per image.

This fixes some edge cases where the shown date would be unprecise due to missing metadata in Nextcloud.

1.4.2

Fix frame not loading for files with missing metadata

1.4.1

Add support for custom JavaScript code