Nadiya - SG Support

Recommended fix for SiteGround Speed Optimizer / Lazy Load Media conflict:

Open the affected gallery block in the editor, then go to:

Gallery Settings → Media HTML Output → Inline HTML

This changes the fallback gallery output from <noscript> HTML to hidden inline HTML. It avoids cases where optimization plugins remove <noscript> tags and expose fallback media on the frontend.

If possible, also disable the external Lazy Load Media feature for pages using SimpLy Gallery Block, because the plugin already includes lazy loading for gallery images.

Hi Alan,

Thank you for reporting this.

The “Gallery data is missing” message means that the frontend script is running, but the gallery data expected on the frontend page is not available. This can happen for different reasons, including theme behavior, another plugin modifying block output, cache/optimization tools, or changes in the WordPress environment.

At this point, I cannot confirm that this is a bug in the SimpLy Gallery Block plugin itself.

Since the gallery is visible in the editor but not rendered correctly on the frontend, please first test the site environment by doing the following:

1. Temporarily switch to a default WordPress theme, such as Twenty Twenty-Four or Twenty Twenty-Five.
2. Temporarily disable all other plugins except SimpLy Gallery Block.
3. Clear all cache, including browser cache, site cache, CDN cache, and any optimization/minification cache.
4. Create a new test page with only one Masonry gallery block and a few images.
5. Check whether the gallery renders correctly on the frontend.

If the issue still happens in that clean environment, please send me the results of that test, including the theme name, WordPress version, plugin version, and any console/PHP errors. In that case, I will treat it as a confirmed plugin issue and investigate it from the plugin side.

However, if the gallery works correctly in the clean environment, then the problem is caused by a conflict with the active theme, another plugin, or site optimization/caching settings.

Hello,
That’s great that you’ve found a solution that works for you.

Hello,
On the page mentioned at the beginning of this topic, you are using the Album Navigator block. This block (album) displays galleries strictly according to its own layout rules.

Album blocks are independent blocks that present the galleries included in them based on their own display logic. It does not matter which blocks were originally used to create the galleries, because album blocks only pull the gallery content (data sources), not their visual styling.

If you would like your galleries to retain their individual appearance, you should not use albums on that page. Instead, create a list with links to those galleries — this way visitors will see each gallery exactly in the format and design in which you originally created it.

Hello, we did see this message, but unfortunately the author of the report is currently not responding to us despite multiple attempts to reach out through Patchstack. Because of this, we do not have access to the report details and therefore cannot verify or fix the issue yet.

From my side, I can only assume that this may be related to Contributor-level permissions — for example, if users with the Contributor role on your site attempted to add harmful links or scripts through gallery content, that could potentially create a problem. However, until Patchstack restores our access to the report, we are unable to properly investigate or close the issue on their platform.

We are keeping this on our radar and continue to request access periodically. Unfortunately, unlike reports coming from the official WordPress Plugin Directory team — where volunteers send issues to developers through a centralized WordPress infrastructure — communication with independent researchers can sometimes be much more complicated.

Hello,
The basic gallery blocks only allow you to control the caption position inside the gallery item container (top or bottom).

Only the Portfolio block (part of the extended plugin package) allows captions to be displayed below the image, and in that case the gallery layout will use the Masonry type.

The link

https://forepoint.co.uk/for_staff_andrew_0614_rs/

is the permalink of a WordPress attachment page.

In WordPress, attachment pages are enabled by default.

Every media item (image, video, audio) in the Media Library has its own page, which can be used for SEO purposes (description, caption, contextual content, indexing).

Our plugin correctly outputs this attachment permalink on purpose, as it is a standard WordPress behavior and helps search engines better understand and index site content.

In your case, attachment pages are disabled at the site level, which is why the link returns a 404 error.

This is most commonly caused by:

• an SEO plugin (such as Yoast SEO or Rank Math), or
• the active theme, which may intentionally disable attachment pages.

The media file itself is accessible and working correctly — only the attachment page is disabled.

This behavior is not caused by our plugin, but by site-specific SEO or theme settings.

Hello,
To start the conversation, the best thing is to share a link to your gallery.

You can also use this demo page for reference – https://simplygallery.co/grid-tags-filter/ Please try to audit this page on your side. If you experience the same issues there, I’ll be able to analyze the possible causes.

For general context: sgbdata contains the gallery data. The URLs inside sgbdata are the actual image URLs used for rendering the gallery. If sgbdata contains broken links, then the gallery itself has broken image URLs.

In short, if the plugin isn’t working on your site, it’s most likely due to a conflict with another plugin or your theme. You’ll need to identify the source of that conflict — or consider using a different gallery plugin if needed.