Focal point and asset container ignored in SEO preview (tab)

[helloDanuk]

Bug description

If you open the seo preview tab I noticed two things:

1. The social images do not respect the focal point on the CP's SEO Preview Tab.

The path to the image is just src="assets/filename-xy.jpg". The image has a class object-cover but nothing gets cropped, when using a focal point.

---

The template tag {{ seo_meta }} on other hand renders <meta property="og:image" content="http://raster.test/img/asset/YXNzZXRzL2FuZHJpaS1kZW55c2Vua28tX2tzY3hoaC1yd28tdW5zcGxhc2guanBnLndlYnA/andrii-denysenko-_kscxhh-rwo-unsplash.jpg.webp?p=seo_pro_og&amp;s=ea087b9d6d8881b35f25af38cc26ec4f">.

This respects the focal point and results in a different image section.

2. Behaviour with and without published configs

I am uncertain whether this is a consequence of the above issue or whether publishing the configs is mandatory?

Having a social_image in your entry's blueprint and linked this field in SEO Pro…

…results in following behaviours:

• <meta property="og:image"… tag in your template view

  • The image renders with and without published configs fine.

• SEO Preview Tab

  • The image only renders, if you use the default asset container from a fresh Statamic installation.
  • If you change your filesystem disks you need to publish your SEO Pro configs and make changes. For example…

filesystem.php:

    'assets' => [
            'driver' => 'local',
            'root' => public_path('assets/mediathek'),
            'url' => '/assets/mediathek',
            'visibility' => 'public',
            'throw' => false,
            'report' => false,
        ],

needs the following settings in seo-pro.php

    'assets' => [
        'container' => 'assets',
        'folder' => 'social-previews',
        'twitter_preset' => [
            'w' => 1200,
            'h' => 600,
        ],
        'open_graph_preset' => [
            'w' => 1146,
            'h' => 600,
        ],
    ],

if you don't publish your configs you see this in your entry. But I guess, this is mainly a problem because the image is not rendered through glide?

With published configs you see this in your entry:

How to reproduce

• add an social_image asset fieldtype in your entry'y blueprint
• link this fieldtype with SEO Pro
• choose an image and a focal point

=> compare the SEO Preview Tab and the generated image in the <meta property="og:image" … tag of your template view.

=> compare the SEO Preview Tab with and without published configs, when you not use the default filesystem/container form your Statamic installation.

Logs

Environment

Environment
Application Name: Statamic
Laravel Version: 12.53.0
PHP Version: 8.4.18
Composer Version: 2.9.5
Environment: local
Debug Mode: ENABLED
URL: raster.test
Maintenance Mode: OFF
Timezone: UTC
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file

Storage
public/storage: NOT LINKED

Statamic
Addons: 2
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.5.0 PRO

Statamic Addons
jacksleight/statamic-raster: 0.5.0
statamic/seo-pro: 7.2.0

Additional details

No response