VERF breaks the views

Created on 5 May 2021, over 3 years ago
Updated 11 May 2023, over 1 year ago

Problem/Motivation

The activation of VERF either breaks the views (I become fine after removing the VERF module) or cannot be activated via Filter Criteria in a Views :
The selector turns for long time and nothing can be validated.
Is there an issue with a large data base ?

🐛 Bug report
Status

Fixed

Version

2.0

Component

Code

Created by

🇫🇷France andrimont

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

Comments & Activities

Not all content is available!

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

  • 🇨🇭Switzerland Tilo

    Confirm same issue with Drupal 9.5. Ajax enabled or disabled does not make a difference.

  • 🇧🇪Belgium blueblot

    Same problem here: cannot add verf-field. View breaks. After uninstalling module, the view is back.

  • 🇨🇦Canada No Sssweat

    Why not upgrade to version 2.0.0?

  • 🇮🇳India yamzalal

    Same issue happens with Drupal 10 and VERF 2.0.0.

  • 🇵🇹Portugal andrerdiogo Lisbon

    Also get this issue on Drupal 9.4.5 with both VERF 1.0 and 2.0. Ajax doesn't make a difference.

  • 🇺🇸United States sadman

    I think I'm having the same issue or at least the same issue as those reported in the last few months with Drupal Version 9.5.2, PHP Version 8.0.25, VERF Version: 8.x-1.0 on a production website. The AJAX setting in the View makes no difference.

    I can still add VERF filters on the local instance of the same site after a fresh sync of DB, Code and Files. I'm ashamed to admit the most significant difference on my local server is it's running PHP Version 7.4.33. I know this is circumstantial evidence at best and there are other differences with regard to timeout values and debugging settings on the local site. I was able to export a View created on my local site and import it on the production site and the VERF filter(s) worked after import.

    I get this error in Watchdog Logs:
    Drupal\Core\Http\Exception\CacheableAccessDeniedHttpException: The 'administer views' permission is required. in Drupal\Core\Routing\AccessAwareRouter->checkAccess() (line 118 of /mnt/www/html/psufandbsites/docroot/core/lib/Drupal/Core/Routing/AccessAwareRouter.php). (Yes, I have permission to administer views.)

    @RgnYLDZ, Thanks for the break-lock tip in #8 🐛 VERF breaks the views Fixed .

  • 🇧🇭Bahrain nafsinvk

    I am also getting a similar error on Drupal 10.0.3 with PHP 8.1.14

    Log: TypeError: Drupal\block\BlockViewBuilder::view(): Argument #1 ($entity) must be of type Drupal\Core\Entity\EntityInterface, null given, called in /var/www/web/themes/custom/toyota/toyota.theme on line 61 in Drupal\block\BlockViewBuilder->view() (line 31 of /var/www/web/core/modules/block/src/BlockViewBuilder.php)

  • First commit to issue fork.
  • @borjack87 opened merge request.
  • Status changed to Needs review almost 2 years ago
  • Adding accessCheck() to the entity query makes the view work

  • 🇳🇱Netherlands casey

    MR as patch file to be able to use it via composer-patches

  • 🇩🇪Germany Anybody Porta Westfalica

    Re #19 + #20 I think these are different issues? Could you please create a separate one for that? It's Drupal 10 specific!

  • 🇩🇪Germany Anybody Porta Westfalica

    Guess the original issue here is a duplicate of Performance problem Needs work

    And afterwards it became a list of different issues. This should be closed as duplicate and split into separate issues, please.

  • Status changed to Fixed over 1 year ago
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024