#29 also fixed our issue. All of our contextual links stopped rendering after moving to 10.2. Discovered that our custom theme .theme file had a space before the opening <?php.
Removing that space resulted in contextual/renderer ajax call to succeed rather than fail. With a successful ajax call the
Drupal.theme.contextualTrigger = function () {
return '<button class="trigger visually-hidden focusable" type="button"></button>';
};worked, giving us our buttons back.
Thank you for wording that another way. This makes a lot more sense now!
In our case, we have a custom login block with the button pointed to /saml/login
My next task will be to figure out how to make the button dynamic based on the current page so the button points to
/saml/login?destination=a
Appreciate the help!
Hello,
I have the same issue as g_miric, but not sure how they solved the issue given your response.
I've successfully used the login redirect url field to route users to a specific path after logging in, but I'm unsure how to make this dynamic and route to the page they were trying to visit.
For example:
1.user visits www.example.com/a
2. access restricted and presented with login
3. user successfully logs in and continues to www.example.com/a
Thanks for helping me understand!