I suggest to check only the access, there could be websites where unpublished content is accessible for anonymous. Additionally, in the near future we can support other roles scan (e.g., for intranets with authenticated users), that way the code will be compatible.
omarlopesino → credited gedur → .
Drupal core 10.3+ is only supported
After testing it with real data, I have found some use cases where the taxonomy terms are found as access-denied because a view is detected instead of the taxonomy term itself (see image)
Fixed, please check!
gedur → created an issue. See original summary → .
eduardo morales alberti → credited gedur → .
Great idea, please find it done in the latest commit.
Please check!
It would be great if we could simulate the request but not do it so it keeps internal, so we avoid involving other layers like CDN or so
Probably having a subtype, and the possibility to ignore them by config is the way to go.
Auto references on pages with several anchors could increase database size dramatically, and probably the information provided is no as important as if the node is analyzed (user has access) it is proof that the self-reference link works also.
I suggest only to include the dependency of views_data_export and not the ones this module requires unless we are using them explicitly
Is there any current limitation or extra effort to keep the compatibility with Drupal 9?
In case not, I suggest extending the compatibility as this module is useful for migration planning from Drupal 9 to 10/11
penyaskito → credited GeduR → .
I suggest facing this in multiple steps, the first one will be to be able to select the database (when there are multiple configured on the settings file), I imagine something like a select field on the top.
In the first approach I will suggest to cover only the same version of Drupal the module is covering right now, so we can cover things like:
- Migrations from D8 to D9 or D10
- Migrations from other Drupal sites (d8-d10), that wants to be merged or checked
- Remote instances databases
- Multisite sites where I want to see other sites from one instance
Note there are just examples of just allowing selecting the database and supporting the same version it helps in several use cases.
Next steps will be to progressively support other Drupal versions and even other CMS (new specific issues)
What do you think?
That's precisely what I imagined.
I suggest adding a link at the end of each view mode like "See example" that redirects to the canonical page or opens in a modal.
In case it is a modal (e.g. a paragraph) it should display a link to the entity that contains the element so you can see it also in context.
The entities displayed should be random, so I get different visualizations to help me to understand.
GeduR → created an issue. See original summary → .