Stefan Göllner

@aralroca with the workaround I only get the keys and not the values returned. And can the workaround be added once in the next.js project or do we have to...

Pagespeed Insights even says that it is not gzipped. This could shave off some loading time and could improve this issue while we wait for a proper solution.

would need that in the content API too :) would be great to get that when fetching blog posts for an blog overview page

> I put in place a temporary solution, the time to do a PR to have a permanent solution. > > **Create a command:** > > ``` >

Nevermind, i added my replicas in the scout-xxx.config and had to remove this first: ``` $settings = [ ...$indexConfig, ...$replicaConfig, ]; // remove replicas from settings array, else the algolia...

Also running into this issue, would be great if anyone could share a solution to this

brick/schema can extract the data, if the context is set on a `graph` item: ``` { "@context":"https://schema.org", "@graph":[ { "@context": "http://schema.org/" "@type":"Organization", "@id":"https://example.org/#organization", "name":"Acme LTD", "url":"https://example.org/", "sameAs":[ ] } ]...

@ryanmitchell sorry, didn't see the replys. I think it was, because I manually uploaded assets to the S3 bucket. Not sure if this still happens, but Statamic didn't try to...

@ryanmitchell just running into this again. I am on 4.58.2 now and every asset I upload to S3 breaks the asset viewer. Have to manually create a corresponding yaml file....

if this could be related, i have a custom root folder in filesystems.php ``` AWS_ACCESS_KEY_ID=xxx AWS_SECRET_ACCESS_KEY=xxx AWS_DEFAULT_REGION=eu-central-1 AWS_BUCKET=xxx AWS_USE_PATH_STYLE_ENDPOINT=false AWS_URL=https://assets.example.com 'cms' => [ 'driver' => 's3', 'key' => env('AWS_ACCESS_KEY_ID'), 'secret'...