Closed (fixed)
Project:
Webform
Version:
6.3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
14 Nov 2024 at 15:48 UTC
Updated:
2 Apr 2026 at 13:19 UTC
Jump to comment: Most recent
The webform overview is accessible with the access webform overview permission. But the filter and the bulk operations on that overview are only available with the administer webform permission. The downside of that is, it grants far too many permissions to a user who only wants to filter webforms on the overview or needs to get access to archive, etc.
Introduce a new permission administer webform overview which can be granted to roles that should not have full admin permission but need access to those filters and bulk operations.
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
jurgenhaasComment #4
jrockowitz commentedThis enhancement makes sense, we just need to add a little test coverage to \Drupal\Tests\webform\Functional\WebformListBuilderTest
Comment #5
jrockowitz commentedIf tests pass this can be RTBC
Comment #7
jrockowitz commentedComment #9
glynster commentedOn a project the update failed for us
Error:
The only way we could resolve it was to update to
This could be an isolated issue as several other projects did not have this issue.
Comment #11
jrockowitz commented@glynster Thank you for posting something so quickly. I hadn't tested the update which contained a very dumb mistake.
I committed the fix. @see https://git.drupalcode.org/project/webform/-/commit/03af82986c566e137426...
Comment #15
dimilias commentedI do not want to reopen the issue but just log something here just if somebody else runs across it.
This update broke our update path because it is using the API to update a role entity before config sync.
In our case, we had a rest plugin that we installed in the website and later removed it. At the same time, we updated webform.
One of our roles, which has the admin flag set to true, but no permissions assigned (because it gets all permissions) was attempted to be updated.
Now, I understand this might be quite an edge case, but since we removed the rest configuration, and along we removed the plugin as well, but because this is trying to update the role before configuration update (we are using
drush deploy), Drupal started gathering all permissions and threw a PluginNotFoundException.For anyone that might run across this, you may either use an update hook to remove the configuration prior to the update or you can commit a patch to first check for the role being admin or having no permissions.
Examples for both:
Or, submitting a patch (not very optimal at this point unless you provide a different update entirely):
The later solution is not preferred because 1, our case was very specific to admin roles, and 2, someone for some reason might still appoint (by mistake) permissions to that role too.
Comment #16
dpiSame as @dimilias, trying to do an all in one D10.5->D11.2 upgrade with 6.3.0-beta7 in the mix.
Im getting:
Like various other update paths in the same file, I think we need to update
webform_update_8648to also useconfigFactory'slistAllandgetEditableinstead of by entity API's.Comment #18
dpiPushed MR811 with proposed change.
Comment #19
dpiCreated #3582749: Fix direct use of entities in upgrade path for above.