/
/
FotoGrids 1.2.0: brick by brick

FotoGrids 1.2.0: brick by brick

•

3 min read

•
FotoGrids 1.2.0 is out: galleries and albums now work in Bricks, settings keep every choice, and statistics, caching and password galleries work as set.

FotoGrids 1.2.0 is out, and it brings FotoGrids to Bricks. The rest of the release was built the same way, brick by brick: settings that keep every choice you make, statistics that count what they should, and galleries that show each visitor exactly what they are allowed to see. There are twenty-one changes you can see, and many more fixes underneath.

FotoGrids, now in Bricks

Bricks now has a FotoGrids Gallery element and a FotoGrids Album element, in their own FotoGrids group in the builder panel. Pick a collection with the same picker the block and the Elementor widget use, or start a new one, and the real gallery renders on the canvas as you design, styled and clickable. The gallery element can also take its gallery from Bricks dynamic data, so one template can show a different gallery on every post.

Settings that keep every choice

Settings that hold several choices, such as the blocks in the Lightbox info panel, the share networks, breadcrumb placements and the EXIF fields to show, now keep every option you pick from the first save. Updating to 1.2.0 repairs galleries that were saved with a single value, so a Lightbox info panel that had gone missing comes back by itself, and the same repair runs on any export you import from an earlier version.

Statistics that count what they should

Share clicks now count on every network the share bar offers, and a share from a view page footer counts against the gallery or album being viewed. Track share clicks stops counting when you turn it off, and an item share counts only when its own gallery has Statistics on. A view page visit counts once, private galleries and albums count their views, and the daily history is trimmed to your retention period. All of it shows on the Statistics page.

Each visitor sees what they should

Password-protected and members-only galleries now stay out of the FotoGrids render cache and out of full-page caches, so one visitor’s unlocked gallery is never served to the next. Gallery data requested through the REST API follows the same password and visibility rules as the gallery itself. Albums show visitors only the galleries they may view, private collections open as normal view pages for users who can read them, and Recently Edited and Statistics list only the collections each user can open. An unlocked password gallery that does not remember the visitor now pages, loads more and opens every Lightbox slide.

And many more fixes

Authors and editors can open the Galleries and Albums lists, and authors can edit and delete the galleries they publish. Library access follows the Permissions Manager everywhere, and Library refuses a duplicate name and checks location coordinates. Publish and Update wait for a running autosave, and publishing a new gallery goes straight through without a leave-page prompt. Cached galleries load their Google Fonts, animate their loading icon and link back to the album a visitor came from. The Lightbox keeps responding to every arrow and thumbnail, galleries added to an album keep the order you added them in, two placements of the same gallery keep their own styles in page builder previews, and deleting FotoGrids with WP-CLI cleans up as it should.

The full list is on the changelog, and what comes next is on the roadmap.

In this article

Share the article

Related Articles