Contrib.social

Expose a display setting to hide new EVA fields by default

Open on Drupal.org →
Created on 20 June 2013, almost 12 years ago
Updated 12 September 2024, 7 months ago

When you create a EVA view it will add the "EVA field" on every display of the node. To be consistent with drupal core it should only add the field on the "default" display. In some situation it can even create infinity loop if you use EVA to display the same node type than the one you attach to.

✨ Feature request
Status

Needs review

Version

2.0

Component

Code

Created by

🇨🇭Switzerland gagarine

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment over 1 year ago →
    🇺🇸United States AaronBauman Philadelphia

    bump

  • Merge request !18Adds 'hide by default' option to EVA fields to prevent them from being... → (Open) created by AaronBauman
  • Comment 7 months ago →
    🇺🇸United States AaronBauman Philadelphia

    version bump, now with MR

  • Comment 7 months ago →
    ahebrank

    LGTM, looking for a RBTC from someone to merge.

  • Comment 7 months ago →
    🇬🇧United Kingdom SirClickALot Somerset

    I'm with you aaronbauman → , keep it up!

  • Comment about 2 months ago →
    🇯🇵Japan s-jack Tokyo

    The EVA field cannot even be hidden when using the full page in ''default'' view mode.
    Any field should be able to be hidden.

    I hope this patch will be committed.

  • Comment about 1 month ago →
    ahebrank

    @sirclickalot @s-jack I need an RTBC on this issue, ideally with testing from more than one person. If the current patch works for you and is bug-free, please update the issue status and I will merge so we can save @aaronbauman from rebasing again.

  • Comment 4 days ago →
    🇯🇵Japan s-jack Tokyo

    I could not apply the patch.
    I am a Sunday programmer and it is difficult for me.

    composer install
Gathering patches for root package.
Removing package drupal/eva so that it can be re-installed and re-patched.
  - Removing drupal/eva (dev-3.1.x 118c17c)
Deleting /app/web/modules/contrib/eva - deleted
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Package operations: 1 install, 0 updates, 0 removals
  - Syncing drupal/eva (dev-3.1.x 118c17c) into cache
Gathering patches for root package.
Gathering patches for dependencies. This might take a minute.
  - Installing drupal/eva (dev-3.1.x 118c17c): Cloning 118c17c1b4 from cache
  - Applying patches for drupal/eva
    https://www.drupal.org/files/issues/2019-06-07/eva-hide_by_default-2024011-16.patch (Expose a display setting to hide new EVA fields by default: https://www.drupal.org/project/eva/issues/2024011)
   Could not apply patch! Skipping. The error was: Cannot apply patch https://www.drupal.org/files/issues/2019-06-07/eva-hide_by_default-2024011-16.patch

Generating autoload files
45 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
  • Comment 3 days ago →
    🇯🇵Japan s-jack Tokyo

    I had installed 3.1.1, but the patch was not applied, so I ran composer require 'drupal/eva:3.1.x-dev@dev.
    I don't have a solid understanding of patching using composer, and I still get a message that the patch was skipped, but looking at the code diff, the patch seems to have been applied.

    I have enabled the default hide EVA setting in VIEWS and confirmed that EVA is hidden in the default view for the new content type.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024