description.html.twig

Contains the text of the field_permission_example explanation/description page

Available variables:

  • admin_link: The translated link pointing to the administer permissions page.

File

modules/field_permission_example/templates/description.html.twig

View source
  1. {#
  2. /**
  3. * @file
  4. * Contains the text of the field_permission_example explanation/description page
  5. *
  6. * Available variables:
  7. * - admin_link: The translated link pointing to the administer permissions page.
  8. */
  9. #}
  10. {% set edit_content_types = path('entity.node_type.collection') %}
  11. {% trans %}
  12. <p>The Field Permission Example module shows how you can restrict view and edit
  13. permissions within your field implementation. It adds a new field type called
  14. Fieldnote. Fieldnotes appear as simple text boxes on the create/edit form, and
  15. as sticky notes when viewed. By 'sticky note' we mean 'Post-It Note' but that's
  16. a trademarked term.</p>
  17. <p>To see this field in action, <a href={{ edit_content_types }}>add it to a
  18. content type</a> or user profile. Go to the permissions page ({{admin_link}})
  19. and look at the 'Field Permission Example' section. This allows you to change
  20. which roles can see and edit Fieldnote fields.</p>
  21. <p>Creating different users with different capabilities will let you see these
  22. behaviors in action. Fieldnote helpfully displays a message telling you which
  23. permissions it is trying to resolve for the current field/user combination.</p>
  24. <p>Definitely look through the code to see various implementation details.</p>
  25. {% endtrans %}