That was once fixed in D7 #1432078: If view is empty "Save" button is still visible but not ported to D8+.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | weight-empty-view-3226688-2.patch | 508 bytes | chi |
That was once fixed in D7 #1432078: If view is empty "Save" button is still visible but not ported to D8+.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | weight-empty-view-3226688-2.patch | 508 bytes | chi |
Comments
Comment #2
chi commentedComment #3
chi commentedI am not sure if this is the best way to fix this. We could probably check how other contrib modules handle this.
Comment #4
darvanenThis removes all actions associated with a view, which may remove buttons provided by other (contrib/custom) modules that are still useful when there are no results. I don't know of any, but implementing this would be a case of the module reaching beyond the boundaries of its own logic.
I suggest that instead we open a core issue requesting that this part of ViewsFormMainForm::buildForm pays attention to a return value to determine if a form is actually required in the circumstances:
Thoughts?
Comment #5
anybodyAgree with #4. The #access=FALSE should only apply on the button from weight module.