Frederik Sauer

I have the same issue, but it happens just by having the `suggest` fieldtype in a grid in a different section (tab) than main. ```yaml title: Footer hide: true sections:...

This can be fixed with a simple patch: ```diff diff --git statamic/core/CP/Fieldset.php statamic/core/CP/Fieldset.php index f8aa593..bf9a474 100644 --- statamic/core/CP/Fieldset.php +++ statamic/core/CP/Fieldset.php @@ -639,7 +639,15 @@ class Fieldset implements FieldsetContract return array_merge($this->preProcessField($config),...

@jasonvarga I know v2 is not your first priority, but would it be possible to get this fixed?

Yes, the editors don't have access to files in any way.

Ahhh... just updated to clarify :)

Nope, the site settings are locked so they can't be changed outside of local development, and the issue occurs on the client's stage site. Might be related to #2163 -...

@jackmcdade we experience the same issue, with a customer not knowing you shouldn't write uppercase letters into the slug. Would it be an issue to actively force the slug to...

As a side note, using `from` in a slug field doesn't work within the context of a replicator, only on root level.

I can confirm, that when you try and create a translation for a term, the translation is not saved - this fix in https://github.com/statamic/eloquent-driver/issues/78#issuecomment-1285034671 doesn't work. I'll look into this...

We have a fork running where I basically rewrote the entire package, yet made the endpoints compatible with the existing package - https://github.com/dwarfhq/laravel-saml2/tree/multi-providers The `multi-providers` branch hasn't been merged yet...