-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Views field "Comment: Edit link" call to comment_access() always returns false #5883
Comments
Hi @alanmels. Thanks much for reporting! I followed the steps:
I don't see anything in the log. Is there a step missing? Do you have to place the block somewhere and then try to access it? |
OK, I found the issue. However, it'd be good to fix this. |
PR provided: backdrop/backdrop#4270 Please test! |
@argiepiano, you'll see the log if everything is turned on /admin/config/development/logging Thanks for confirming my finding. I know it's just a comment, but since it's flooding the log page would be still nice to get this fixed. |
Thanks for the quick fix. I've tested PR and it works as expected - the log page is no more flooded with the reported comments. It's ready to be committed from my perspective, however one could suggest that once this is being dealt to improve other related issues such as:
|
@alanmels, I believe you are misunderstanding the way So, in my view, it's best not to change the user-facing text, nor the name of the handler. This last one would require many changes in the code in several places. If this works for you, please mark it so with the "works for me" label. |
Thanks for the explanation. I agree with your arguments. I've just approved backdrop/backdrop#4270 (review), but I don't think I have enough privileges to mark this issue with "works for me" label. At least I don't see such option anywhere on my end. |
The "works for me" label should be applied here - not in the PR. It's on top of this screen, under "Labels". Marking the PR as "approved" doesn't mean anything in the Backdrop community |
@argiepiano, once again, I do not I have enough privileges to use labels here. Per https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels
I do not have write access. |
My apologies |
To quote from https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels#applying-a-label
So I believe I do not have triage access to the repository either. I'm not sure if I should apply for it or if Backdrop gods will just magically give it to me. I'm totally ok without such access, though. |
Code reviewed. The one-word change looks good to me. Removed the "needs testing" label based on @kiamlaluno's WFM label and previous comments. |
Thanks folks! A nice easy fix. Sorry this took so long to pull in. I've merged backdrop/backdrop#4270 into 1.x and 1.26.x. Thanks @argiepiano, @alanmels, @bugfolder, and @kiamlaluno! |
Description of the bug
If you use the same test view given in #5882 and just add
Comment: Edit link (Edit link)
link field as shown below:then the website logs starts filled in with the reported comments in title.
Additional information
It's not an error or even a notice, but just a comment:
However, still (1) it is not pleasant at all that the log gets quickly flooded with the same comment if your website is actively using the corresponding views page/block. And then (2) this message is caused not by some kind of contributed module, but core itself. See https://github.com/backdrop/backdrop/blob/7cc9968d3c1f8885a9d126668b1a8c0766b8e3d6/core/modules/comment/comment.module#L1508 :
I'm not sure how to tackle this issue as there is simply no such operation as
Comment: Update link
, but there isComment: Edit link
.The text was updated successfully, but these errors were encountered: