All add-ons currently require PHP 7.4 or greater.

On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.

Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: Clicking the “Remove” icon affects all image fieldtypes in all nested blocks

Status Resolved
Add-on / Version Bloqs 4.0.18
Severity
EE Version 5.3.0

Jason Morehead

Dec 02, 2019

I’m using nested blocks to create a photo gallery, i.e., you add a “Gallery” block to a page, and then you nest “Gallery Image” blocks underneath it to create the gallery items.

My users have recently experienced a glitch when modifying the image that’s contained within a “Gallery Image” block. Here’s how to replicate it:

1) Edit an existing entry that has a gallery on it.
2) Click on the “Remove” trash can icon to remove the image that’s currently being used by the block.
3) Select a new image.

Here’s the glitch: As soon as an image is selected, all of the other image fields in the other nested blocks are updated, too. I’ve attached some screenshots that show this process.

Obviously, only the image for the block you’re working in should be updated; all of the sibling blocks’ images should be left alone.

#1

BoldMinded (Brian)

Hi, Jason. That bug was fixed some time ago. You should upgrade to the latest version.

#2

Jason Morehead

My apologies. I thought I was using the latest version because I didn’t see the “Update Available” flag in the admin area. I’ll upgrade ASAP.

#3

BoldMinded (Brian)

No worries. I’m going to go ahead and close this ticket b/c the newer version should fix the issue.

Login to reply