I believe that if you disable SQL revisions for a node type in admin/config/system/field_sql_norevisions/field_sql_norevisions_entity_settings that 2 things should happen that do not yet happen now:

- when editing a node of a node type that has SQL revisions disabled, the 'Revision information' part should not be shown here (you should check and do a hook_form_alter to set $form['revision_information']['#access'] = FALSE;)

- when editing a content type, the section 'Content revisions' should either not be shown, or should only display a message like 'Revisions are disabled for this content type by SQL Revisions module'. With a link to admin/config/system/field_sql_norevisions/field_sql_norevisions_entity_settings

Comments

pwaterz’s picture

pwaterz CreditAttribution: pwaterz commented

I am not opposed this. Patches are welcome.

The reason I didn't do this in the past was because this module focuses on revision at the entity level, rather than a specific entity it self, like nodes. Nodes are a special case that have custom revision settings.

geek-merlin’s picture

geek-merlin
they/omg
Primary language German
Location Freiburg, Germany
CreditAttribution: geek-merlin commented

This makes sense.