A mis-named class introduced in #2865615: Not compatible with REST module unfortunately completely broke taxonomy pages, by getting this error message:

Fatal error: Cannot declare class Drupal\taxonomy_access_fix\TermAccessControlHandler, because the name is already in use in /var/www/drupalvm/web/modules/taxonomy_access_fix/src/TermAccessFixTermControlHandler.php on line 0

The fix however is easy. I'll provide a patch

CommentFileSizeAuthor
#2 fix_access_handler-2943950-2.patch498 bytesagoradesign

Comments

agoradesign created an issue. See original summary.

agoradesign’s picture

agoradesign commented
Status: Active » Needs review
StatusFileSize
new fix_access_handler-2943950-2.patch498 bytes

here's the patch.. please verify and commit asap incl new release

willieseabrook’s picture

willieseabrook commented

I'm not sure if it's related but I'm arriving here after an upgrade to 2.3 around 20 minutes ago.

When trying to visit a taxonomy term page e.h /taxonomy/term/13 I get the following:

Drupal\Component\Plugin\Exception\InvalidPluginDefinitionException: The "taxonomy_term" entity type did not specify a access handler. in Drupal\Core\Entity\EntityTypeManager->getHandler() (line 236 of /docroot/core/lib/Drupal/Core/Entity/EntityTypeManager.php).

I have fixed by pinning composer.json to 2.2 and flushing the cache a couple of times

agoradesign’s picture

agoradesign commented

It sounds definitely related, as the mentioned commit has swapped out the default access handler defined by core.

However, it sounds weird that using version 2.2 fixes the issue for you. The bug was definitely introduced in 2.2 already. 2.3 only added a less important line to the info.yml file

  • pifagor committed 366f094 on 8.x-2.x authored by agoradesign 
    Issue #2943950 by agoradesign: Fatal error: Cannot declare class Drupal\...
pifagor’s picture

pifagor
Location 🇺🇦 Rivne
commented
Status: Needs review » Fixed

Done

pifagor’s picture

pifagor
Location 🇺🇦 Rivne
commented
Status: Fixed » Closed (fixed)