- Issue created by @eduardo morales alberti
- 🇪🇸Spain jonhattan Plasencia
I think the module should not depend on other "ui" modules. It may be a stopper for people to choose using it.
IMO the fix here should be one of both:
* Try and provide the same functionality without requiring views ui
* Provide this functionality only when views ui is enabled. Otherwise show a notice such as "Enable views ui module in order to see X report" If the problem comes from "https://git.drupalcode.org/project/xray_audit/-/blob/1.x/src/Plugin/xray..." (Link Url generation), $Link->getUrl()->access() can be checked to avoid that error at time of rendering. Besides that will manage that user has access to xray report but has not to edit views.
To check just use:
new \Drupal\core\Url('<front>')->access(); = true > new \Drupal\core\Url('noexists')->access(); = false
- 🇮🇳India sourav_paul Kolkata
sourav_paul → changed the visibility of the branch 3479320-add-views-ui to hidden.
- 🇮🇳India sourav_paul Kolkata
Thanks @jonhattan & @crzdev for your suggestions.
I've fixed the issue..
sharing ss:
- 🇪🇸Spain lpeidro Madrid
Hello sourav_paul
Thank you very much for your contribution. If you do not mind I have modified it lightly.
The message about enable the module Views UI is showed as a Drupal message to avoid repeat the same message in every row:
Best regards.
-
lpeidro →
committed 4293b0ed on 1.x authored by
sourav_paul →
Issue #3479320: Fixed views report error.
-
lpeidro →
committed 4293b0ed on 1.x authored by
sourav_paul →
Automatically closed - issue fixed for 2 weeks with no activity.