Changing imageset of existing images -- Is it safe?

We have many images in BrXM that were created using a custom imageset with multiple variants. We now want to “migrate” these images to use the standard out-of-the-box imageset, “Image”.

Rather than manually recreating these images under the new imageset and updating all document references, we’re exploring an alternative approach that appears to work but is, as far as we know, undocumented. We’d like to confirm whether this approach is safe and supported.

In the BrXM console, it’s possible to change the imageset of an existing image (see attached screenshot).

We’ve tested this and it seems to work without any visible issues. However, we noticed that after changing the imageset to “Image”, the image variants disappear from the GUI – although they are still present in the repository.

Our concern is whether this could pose a problem now or in the future. Specifically:

  • Is it safe to change the imageset like this?
  • Could the hidden variants cause issues later on (e.g., with rendering, cleanup, or upgrade paths)?

Thanks in advance for your help!

HI,

this should be safe. The variant images will indeed still be in the repository. They won’t be shown in the GUI because the GUI classes look up the type and display what is defined for that type, not just whatever is on the node. The main issue with the dangling variants is the extra data. It takes up space and reduces performance (though you may not even notice that). Perhaps there are upgrade scenarios where this could be problematic, but likely not very.

I suggest using an updater to change the images and clean up the extra variants.

Hi @hcu

We are happy you are part of Bloomreach Developer’s Community.
Thank you for reaching out to us.

We hope we have addressed all your questions. If you need any further assistance, please feel free to reach out to us.

We are delighted to acknowledge your ongoing contributions to our esteemed Bloomreach Community.

Best Regards,
Bloomreach