Allow disabling Glide for JSON-LD organization logo

[samalisam-novu]

The Glide-generated logo URL in the Organization JSON-LD snippet causes a "Signature is not valid" error in headless setups. I believe this happens because the Statamic backend URL differs from the configured site URL, so GlideController::validateSignature() can't correctly extract the request path and the signature check fails.

This adds a json_ld.use_glide_for_logo config option (defaults to true for backward compatibility). When set to false, the logo outputs the asset's permalink directly instead of going through Glide. The idea is that in a headless context, the user can just upload a properly sized image and skip Glide entirely.

Please let me know if this feature doesn't properly fit. Here to help out :)

[duncanmcclean]

Out of curiosity, did you only start running into this error after updating to Statamic v6.4.0?

[samalisam-novu]

TBH, we are just now switching to Statamic 6 and we don't have any Statamic 6 projects live currently.
I'm currently building the boilerplate for the rest of the team to start new projects with.
Also we were using Seotamic with Statamic 5 before, so Statamic 6 + SEO Pro are both new in our stack.

All of our projects run headless with GraphQL + nuxt. I know we're kind of niche with that, but that's what we like to work with :)

[duncanmcclean]

I don't suppose you'd be able to downgrade to v6.3.3 and let me know if the "Signature is not valid error" still happens? Just wondering if it's related to a recent change we made in Core.

I don't really want to introduce a new config option for something small like this unless we need to.