In the spirit of @jenlampton's "put things where users expect to find them" move, once #1262 is implemented, we should have it so that:
1. These tabs reflect the current setting. Something along the lines of "Comments are currently [closed|hidden]
for the [content_type_name]
content type.".
2. Either provide a link to the configure page and jump to the "Comment settings" tab (/admin/structure/types/manage/page#edit-comment
) ...but then we'd need to figure a way to redirect the user back to the "Comment fields" or the "Comment display" tabs where they originally came from.
3. ...or open those settings (content type comment settings) in a modal so that the user does not have to leave the page they are at in the first place.
GitHub Issue #:
1274
Recent comments
Hi I added the 2 additional settings in settings.php, did a restart - and the error disappeared! Thanks for the support! (but the issues with the conversion still remain .....
Problem with utf8mb4 Format when importing database
With JQuery, simple and fast. Or put all possible links in one menu, and hide unnecessary with CSS mediaquery.
Different primary menus depending on the viewport size?
I wonder if what is happening here is the default database settings are for utf8mb4 if the database server supports it. In settings.php or settings.local.php if that's where you put your...
Problem with utf8mb4 Format when importing database