@outcast creatures

outcast creatures → created an issue.

outcast creatures → created an issue.

outcast creatures → created an issue.

I recieved this error also but it was based on Field Permissions → trying to add field level permissions to " Entity Extra Field → . Normally Field Permissions → has a permissions form in the edit form of a field.

I wanted to add this, isnce i stuggled to find a solution that worked.

There is now  View Mode Page →  that does this exact thing for drupal 9 and 10, the views solution doesn't work with some other modules.

outcast creatures → created an issue.

Yes this does happen, a fix for it is the "remove duplicates" option in easy breadcrumbs

Just got smacked with this issue, just as a side thought i decided to check the url redirects listing to see if pathauto or any url modules messed with something and YEP!! deleted the url redirect and all is good.

USed on Outcast Creatures

• frontpage: Home
• cinema (all), cinema(movies), cinema(tv shows)

The site is always a work in progress, so I am sure it will be used other places too.

Same issue
@chemjim nice catch!!

PEERFECT!!! As always thanks so much, that fixed it perfectly.

bad typo the error is

Error: Class "Drupal\config\StorageReplaceDataWrapper" not found in Drupal\eca_ui\Form\Import->submitForm() (line 331 of modules/contrib/eca/modules/ui/src/Form/Import.php).
call_user_func_array() (Line: 129)
Drupal\Core\Form\FormSubmitter->executeSubmitHandlers() (Line: 67)
Drupal\Core\Form\FormSubmitter->doSubmitForm() (Line: 597)
Drupal\Core\Form\FormBuilder->processForm() (Line: 326)
Drupal\Core\Form\FormBuilder->buildForm() (Line: 73)
Drupal\Core\Controller\FormController->getContentResult()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 638)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 181)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle() (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 741)
Drupal\Core\DrupalKernel->handle() (Line: 19)

outcast creatures → created an issue.

outcast creatures → created an issue.

I am not at my desk right now, but its https://ecaguide.org/plugins/eca/tamper/actions/eca_tamper_keyword_filter/

outcast creatures → created an issue.

If I understand correctly, that's already possible. When you are at the ECA overview page /admin/workflow/eca, then you can export each model as a recipe and then later import that elsewhere again.

I was more meaning a community portal or something.

to solve this issue i credited a twig template file, i am also posting it for anyone else that needs it.

Create a file named: field--node--co-authors.html
put that file in your theme folder.
add the following code to the new created file.

{#
/**
 * @file
 * Default theme implementation for a field.
 *
 * To override output, copy the "field.html.twig" from the templates directory
 * to your theme's directory and customize it, just like customizing other
 * Drupal templates such as page.html.twig or node.html.twig.
 *
 * Instead of overriding the theming for all fields, you can also just override
 * theming for a subset of fields using
 * @link themeable Theme hook suggestions. @endlink For example,
 * here are some theme hook suggestions that can be used for a field_foo field
 * on an article node type:
 * - field--node--field-foo--article.html.twig
 * - field--node--field-foo.html.twig
 * - field--node--article.html.twig
 * - field--field-foo.html.twig
 * - field--text-with-summary.html.twig
 * - field.html.twig
 *
 * Available variables:
 * - attributes: HTML attributes for the containing element.
 * - label_hidden: Whether to show the field label or not.
 * - title_attributes: HTML attributes for the title.
 * - label: The label for the field.
 * - multiple: TRUE if a field can contain multiple items.
 * - items: List of all the field items. Each item contains:
 *   - attributes: List of HTML attributes for each item.
 *   - content: The field item's content.
 * - entity_type: The entity type to which the field belongs.
 * - field_name: The name of the field.
 * - field_type: The type of the field.
 * - label_display: The display settings for the label.
 *
 * @see template_preprocess_field()
 *
 * @ingroup themeable
 */
#}
{%
  set title_classes = [
    label_display == 'visually_hidden' ? 'visually-hidden',
  ]
%}

{% if label_hidden %}
  {% if multiple %}
    <div class="co-author"}>
      {% for item in items %}
        <div class="content">{{ item.content }}</div>
      {% endfor %}
    </div>
  {% else %}
    {% for item in items %}
      <div class="content">{{ item.content }}</div>
    {% endfor %}
  {% endif %}
{% else %}
  <div class="co-author">
    <div class="title">{{ label }}</div>
    {% if multiple %}
    {% endif %}
    {% for item in items %}
      <div class="content">{{ item.content }}</div>
    {% endfor %}
    {% if multiple %}
    {% endif %}
  </div>
{% endif %}

Save and upload your newly created file.
Clear site wide cache.

Outcast Creatures → created an issue.

Outcast Creatures → created an issue.

Mine disappeared as soon as ! ran "check for updates"

This post should be on a doc page or something, after arguing with auto entity labels, entity prepopulate, prepopulate and a few others, your posted saved me. You guys are amazing, keep up the good work.

All i wanted to do is take the "name" and "year" field values and put it in the "title" field as "Name (year)" format.

Thanks for the examples, worked amazing and fixed my plural issues.

Outcast Creatures → created an issue.

I would like this ability too, the re-order isnt important to me but i do need to click on the term name.
My use case is a bit diffrent as i am using editable fields to expose the field on the view-mode so genres can be added on the front end to movie pages, it would be awsome if i could turn off the sorting in lue of clicking on the term link so people can see all movies with X genre term.

Outcast Creatures → created an issue.

I am using the latests (non-dev) release and i just got nailed by this issue. luckily i just reverted to a daily backup of the database.

Where does the tid actually come from, this threw me off. 

The 2 module don't work together so that isnt an option as per https://www.drupal.org/project/unique_entity_title/issues/3427195 🐛 Unique unity title and Automatic Entity Label Active

Outcast Creatures → created an issue.

Outcast Creatures → created an issue.

I just added the Teaser view, no idea why it was gone but it fixed the issue.

IS this patch commited yet?

Outcast Creatures → created an issue.

I am not using the dev version but if anyone else comes across this like i did with layout build.
Here is how i solved the issue:

• must have a default value
• Allow users to cancel their ratings.
• Allow users to re-vote on already voted content.
• Allow users to vote on their own content.

why this makes it work is over my head but its a solution.