Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Follow-up to #2264915: Drupal 8 port
Problem/Motivation
The current issue summaries how things goes in the port of Simplify module to D8.
Proposed resolution
- D8 port maitainer (Dom.) will update issue summary with remaining tasks and follow up.
- Eventual contributers can suggest porting patches in separated child issues of this META.
- Eventual D8 users can comment this META to suggest new features.
Remaining tasks (to be completed)
A/ Drupal 8 Core form simplication.
- Interface port: convert the UI to D8 forms.
- Functional port: convert the simplication mecanism.
Simplify node form according to global settings and "per content-type" settings.Simplify comment form according to global settings and "per comment-type" settings.Simplify taxonomy form according to global settings and "per vocabulary" settings.Simplify user form according to global settings.Simplify custom block form according to global settings and "per block-type"settings.
B/ Drupal 8 custom module UI simplication.
Support Domain access.- Support No index.
- Support Metatag.
Support URL redirects.Support XML sitemap.- Support Book module (now in D8 Core) to simplify Book outline for nodes depending on content-type.
Support Content translation module (now in D8 Core) to simplify Site language.- Support ECK (#2669530: Support for hiding ECK entity creation form text format selection fields.)
C/ Simplify module refactoring.
- Remove all non OOP code except for the various hook_form_alter. Those are not planned to be OOP in 8.0.x
- Remove simplification configuration per types. Use ThirdPartySettings saving instead.
Comments
Comment #1
Dom. CreditAttribution: Dom. commentedGlobal settings page is now available at :
/admin/config/user-interface/simplify
Functionnal test associated is named : GlobalSettingsTest.
Comment #2
Dom. CreditAttribution: Dom. commented"Per content-type" node settings form is now available at content-type admin page :
/admin/structure/types/manage/
Functionnal test associated is named : PerContentTypeSettingsTest.
Comment #3
Dom. CreditAttribution: Dom. commented"Per vocabulary" taxonomy settings form is now available at vocabulary admin page:
/admin/structure/taxonomy/manage/
Functionnal test associated is named : PerTaxonomySettingsTest
Comment #4
Dom. CreditAttribution: Dom. commentedComment #5
Dom. CreditAttribution: Dom. commentedComment #6
Dom. CreditAttribution: Dom. commented"Per comment-type" settings form is now available at comment-type admin page:
/admin/structure/comment/
Functionnal test associated is named : PerCommentTypeSettingsTest
Comment #7
Dom. CreditAttribution: Dom. commentedNode edit form is now simplified according to global or customer "per content-type" settings.
Comment #8
Dom. CreditAttribution: Dom. commentedUser edit form is now simplified according to global or customer "per content-type" settings.
Comment #9
Dom. CreditAttribution: Dom. commentedComment #10
Dom. CreditAttribution: Dom. commented"Add custom block" form is now simplified according to global or customer "per block-type" settings.
Comment #11
Dom. CreditAttribution: Dom. commented"Comment" form is now simplified according to global or custom "per comment-type" settings.
Comment #12
Dom. CreditAttribution: Dom. commented"Add/Edit term" form is now simplified according to global or custom "per vocabulary" settings.
Comment #13
Dom. CreditAttribution: Dom. commentedComment #14
MartinMa CreditAttribution: MartinMa as a volunteer commentedHi Dom! This is just an important module for me, so I would love to animate You for doing the next issues ...
Comment #15
Dom. CreditAttribution: Dom. commentedHi Martin !
Which part of this module do you need that is not yet implemented on the D8 version ? Is it "just" about updating it, or also dev some other functionnalities ?
Comment #16
MartinMa CreditAttribution: MartinMa as a volunteer commentedHi Dom, thanks for your answer (just was filling up the website meanwhile with the content of the old one).
There is only one important thing i am mission: i want to have different sets for different user roles. advanced users /special users like editors shold have some options more than common users.
at the moment i dont have "editors" on my website, but if there are some helping me, it would be usefull to give them some more rights.
It would also be great to hide specific fields of the content types (this is also something another modul seems to offer, to have this in one modul would be great).
Comment #17
Dom. CreditAttribution: Dom. commentedComment #18
AlexBorsody CreditAttribution: AlexBorsody commentedWhen I hide fields I do not see view hidden fields option even as admin and with permissions correct.
Comment #19
Dom. CreditAttribution: Dom. commented'View hidden fields options' ? You mean the permission at /admin/people/permissions ?
Or do you still see the supposed hidden field as an admin ?
I don't really understand the issue, please be more specific.
Comment #20
AlexBorsody CreditAttribution: AlexBorsody commentedForget it I think it's another issue these are hidden on my form not sure why on some nodes URL alias is hidden on some it's not, of the same content type. Even as admin. I don't think it's related to this module.
Comment #21
kevinquillen CreditAttribution: kevinquillen at Velir commentedIs this currently compatible with 8.2.x?
Comment #23
Dom. CreditAttribution: Dom. commentedComment #24
Dom. CreditAttribution: Dom. commented