Seems not working yet

Created on 2 May 2024, over 1 year ago

Problem/Motivation

I like this simpleness, but it seems not working yet.

The node I tested is for users with a certain role to view. I put the test user to node access field. The test user is an authenticated user only. Still access denied for the test user. I cleared the cache, even rebuilt the content access, still the same.

This module, if working, would be very nice!

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

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

Comments & Activities

  • Issue created by @sdsc
  • Assigned to radheymkumar
  • Status changed to Needs review about 1 year ago
  • 🇮🇳India radheymkumar Jaipur, Rajasthan, India

    Hi

    Please patch file

    Thanks

  • 🇮🇳India radheymkumar Jaipur, Rajasthan, India

    Hi @sdsc

    Please share patch file

  • Status changed to Needs work 5 days ago
  • 🇮🇳India sushyl@gmail.com Pune

    Hi @radheymkumar,
    Thanks for contributing this module, it seems very useful.

    I think there might be some confusion about the workflow here. Typically, patch files are created by contributors (including maintainers) to fix reported issues, not requested from bug reporters.
    I also, tried the module and when I assigned access to a test user for a node, the test user was still getting 403/access denied for that node.
    I think @sdsc has provided a clear bug report - the module isn't working as expected when authenticated users are added to the node access field but still get access denied despite having the proper role.

    This needs investigation to determine why the access control logic isn't working properly, so I will change the status of the issue.

    As the maintainer, do you think you could you look into this issue or let us know if you need assistance from other contributors?

    Per Drupal community guidelines, when someone assigns an issue to themselves, they're indicating they plan to work on it. If circumstances change and they're unable to continue, the standard practice is to un-assign the issue so other contributors can pick it up.

    Thanks,
    Sushil

Production build 0.71.5 2024