Closed (fixed)
Project:
Paragraphs
Version:
7.x-1.0-rc5
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Apr 2016 at 15:25 UTC
Updated:
19 Nov 2019 at 23:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
DerTobi75 commentedLooks like the notice was not a problem from paragraphs!
Comment #3
drupupp commentedI'd like to re-open this, because I am also getting error message. While I"m using VBO on the site, it's appearing on the node page of a content type that has a paragraph field. I have set permissions for all roles, and the site is functioning correctly (including creating and editing the paragraph bundle that I have created), but the error message continues to appear (twice, in fact) whenever the page renders.
Comment #4
jlockhartI ran into this as well with VBO. After doing a little investigation I believe this is a bug with Paragraphs. Reading the comments for paragraphs_bundle_permissions_paragraphs_item_access the IF statement at line 30 says, "If there was no bundle to check against, or the $op was not one of the supported ones, we return access denied". That seems to indicate that it should have been doing a check on the entity, which it wasn't. My patch adds that check and also updates the comment to indicate that it returns access ignore not access denied.
My main concern at this point is whether or not this should be returning access ignore if we don't have an entity. Was it originally doing that but then changed later because of access issues? Or was the check intended and the comment written but the check not actually done?
I've tested visibility of our paragraphs for anon users and don't see any issues or errors.
Comment #5
nicolas bouteille commentedhad the same notice and error is gone with patch. thanks !
Comment #7
jstollerPatch committed to dev with minor code cleanup.