🇺🇸United States @gintass

gintass → created an issue.

The following drush commands work fine with 2.0.x-dev version installed:

Check the status: `drush state:get readonlymode_active`
Turn on Read Only Mode: `drush state:set readonlymode_active 1`
Turn off Read Only Mode: `drush state:delete readonlymode_active`

README in version 8.x-1.2 still has the following commands that no longer work in Drupal 9 or 10.
---
Check the status: drush vget site_readonly
Turn on Read Only Mode: drush vset site_readonly 1
Turn off Read Only Mode: drush vset site_readonly 0
---

Following commands suggested in this post do not work either:

drush config:set readonlymode.settings site_readonly 1 (to enable)
drush config:set readonlymode.settings site_readonly 0 (to disable)

I get this when I try to run them:

site_readonly key does not exist in readonlymode.settings config. Do you want to create a new config key? (yes/no) [yes]:

I get the same error. Downgraded to Group 8.x-1.6

This theme uses Twig 2 syntax and Drupal 10 requires Twig 3. In Twig 3 spaceless filter has to be added with the apply tag.

The following files in this theme have to be modified to make it compatible with Drupal 10.
templates/field/link-formatter-link-separate.html.twig
templates/form/select.html.twig
templates/form/dropbutton-wrapper.html.twig
templates/navigation/toolbar.html.twig

-      {% spaceless %}
+      {% apply spaceless %}

-     {% endspaceless%}
+     {% endapply%}

I wonder why this class is been added - node-taxonomy-container to the field even if taxonomy is not being used or even uninstalled completely.
Should there be some 'if' statement that would be adding these classes and and enclosing the field inside the div tag if the taxonomy is being used?
Right now I don't have any taxonomy (I even tried uninstalling the taxonomy module completely), but the field is still being enclosed in the 'node-taxonomy-container' which has some css that makes it hard to position this field properly.
Obviously, I can add some css to overwrite the css, but maybe that can be avoided by adding taxonomy related classes only if necessary.

@jeyro I agree, the slogan should be below the title and next to the logo, therefore I would change the code in this file /olivero/templates/block/block--system-branding-block.html.twig, so that 'site_slogan' is inside the 'site_name':

    {% if site_name %}
      <div class="site-branding__text">
        <div class="site-branding__name">
          <a href="{{ path('<front>') }}" title="{{ 'Home'|t }}" rel="home">{{ site_name }}</a>
        </div>
            {% if site_slogan %}
              <div class="site-branding__slogan">{{ site_slogan }}</div>
            {% endif %}
      </div>
    {% endif %}
  </div>
{% endblock %}

@robertom I was thinking about installing the dev version, but then I saw that beta1 has the same release date as dev, so I though that it already has a patch. Now I installed the dev version and can confirm that site editors can use the autocomplete widget without extra permissions. Thank you!

gintass → created an issue.

It appears that "Administer Content" is not enough either. It does bring back the autocomplete indicator/icon, which made me think that it works, but when I started typing, none of the existing values showed up. The only way I could get it working, if I selected the
"Bypass content access control" permission. Obviously we don't want to give it to a content editor role.

Autocomplete widget requires "Administer Content" permission. That is a problem, since I don't want to give this permission to content editors.
Tested with:
Existing Values Autocomplete Widget - 2.0.0-beta1
Drupal - 9.5.5
PHP - 8.1.17

I uninstalled the "Field Permissions" module to make sure there is no conflict.