- Issue created by @nvandijk
- 🇨🇭Switzerland saschaeggi Zurich
You can opt-out for those pages, see https://git.drupalcode.org/project/gin/-/blob/5.0.x/gin.api.php?ref_type...
Cheers!
- 🇳🇱Netherlands nvandijk
Hi saschaeggi,
I tried to use your method of using the hook for a different problem, however the sticky buttons still show up because I'm trying this for a node bundle form. They are still activated in the
GinContentFormHelper
as it is a content form with actions.This bundle uses a workflow, so does not use the standard
$includes = ['save', 'submit', 'preview'];
buttons as defined ingin_form_after_build
. For the workflow buttons module there is even a patch for ensuring that the buttons are visible in Gin, I feel like this should not be mandatory for modules that might possibly be used in a installation that uses Gin. I feel that this should be the responsibility of the installation that combines modules with Gin, but the ability to configure this should be facilitated by Gin itself. A hook to modify the $includes for a form could be a solution for example.This means that no button is initially visible and all of them are hidden behind the more_actions menu, even when using the
hook_gin_ignore_sticky_form_actions
.Could you tell me if there is also a way to override the includes or something that might resolve the issues I am facing now?
I saw issue https://www.drupal.org/project/gin/issues/3488050 🐛 Uncaught TypeError: formActions is null on a form that is trying not to use Gin form modifications Active relates to this as well. Please let me know if this is more suited there.