\/admin\/panels_ipe\/variant\/panelizer_default\/\*node:\d:.*:.*\/admin\/structure\/(panelizer\/edit|panels\/panelizer\.wizard).*\/entity-browser\/(modal|iframe)\/(image_browser|media_browser).*\/media\/add.*\/admin\/structure\/workbench-moderation\/.*\/admin\/content\/(scheduled-update|scheduled_update).*
Captures interations with the In Place Editor which is used to create and customize Layouts:
- general: /admin/panels_ipe/variant/panelizer_default//
- regex: /admin/panels_ipe/variant/panelizer_default/*node:\d:.:.
Captures interactions with building Panelizer layouts:
- general: /admin/structure/panelizer/edit/* or /admin/structure/panels/panelizer.wizard/*
- regex: /admin/structure/(panelizer/edit|panels/panelizer.wizard).*
Layout note1:
Panelizer layout building is generally performed once by a Site Builder so we
expect these numbers to be low.
Captures interactions with the Media Library:
- General: /entity_browser//
- regex: /entity-browser/(modal|iframe)/(image_browser|media_browser).*
Captures direct media creation:
- General: /media/add/*
- regex: /media/add.*
Captures interactions for workflow state CRUD:
- General: /admin/structure/workbench-moderation/*
- regex: /admin/structure/workbench-moderation/.*
Captures bulk entity transition scheduling:
- General /admin/content/scheduled-update/* or /admin/content/scheduled_update/*
- regex: /admin/content/(scheduled-update|scheduled_update).*
Workflow note1:
The Workflow state CRUD interactions are generally performed once by the Site
Builder. Transitioning individual peices of content should be much more common,
but we don't have a way of isolating URLs that were state transitions.
Workflow note2:
Bulk entity scheduling is suspected to be less popular than individual
scheduling. But we don't have a way of isolating URLs that were used to schedule
individual transitions.