MoDev

@theodorosploumis Thanks sound like a good solution to me.

Seems that $settings ['config_exclude_modules'] is not for excluding configs. It is for excluding "modules" https://drupal.stackexchange.com/questions/291639/how-does-the-new-config-exclude-modules-setting-work-exactly

ok this here seems to be the correct way to bind the file properties.: `select: { title: "asset.title", asset: "asset" },` closing the issue

damn ... we planned to use Plyr for 3 upcoming NextJs projects ... hopefully it can be fixed... strange is also that the error is thrown randomly - but in...

@nikita-fuchs Yeah. I totally agree... working with users feels like a nasty hack. I understand the idea behind the user feature being a plugin. But really this is so close...

I can confirm this happens to a fresh Next JS 14 Setup on Node.js v21.6.0

Hey @Developer-Kings-dev .. we spoke already on Slack regarding this issue. I was able to install the package by using this setup (next 14 latest & sanity installed in the...

In this case we should update the documentation. Otherwise every newcomer will have struggle to install anything... giving up eventually or maybe finding this thread. Am 6. Mai 2021, 13:44...

Yeah until we cannot prevent users from selecting images, italic or h1 tags, layouts can get killed and we need editors who check gainst seo rules. It is really bad...

Yeah would be nice to have an endpoint that delivers via type/id true or false. In my case the admin is really just used for the configuration. So this feature...