Problem/Motivation

The 'Add forum' and 'Add container' forms refer to term instead of forum:

Proposed resolution

Update the form element descriptions to correctly refer to 'Forum' / 'Container'.

Remaining tasks

  1. Write a patch
  2. Review

User interface changes

Form element descriptions on 'Add forum'/'Add container' correctly refer to 'Forum' / 'Container' respectively.

API changes

None

CommentFileSizeAuthor
#82 2453495-82.patch6.25 KBsahil.goyal
#78 2453495-78.patch6.23 KB_utsavsharma
#78 interdiff_77-78.txt1.3 KB_utsavsharma
#77 2453495-77.patch6.25 KBsahil.goyal
#76 2453495-76.patch6.28 KBsahil.goyal
#75 reroll_diff_61-75.txt5.29 KBsahil.goyal
#75 2453495-75.patch6.26 KBsahil.goyal
#64 DuplicateIssuefixed.png21.16 KBakashkrishnan01
#64 AddContainer.png14.62 KBakashkrishnan01
#64 AddForum.png13.83 KBakashkrishnan01
#61 interdiff.txt750 bytesMunavijayalakshmi
#61 add_forum_container-2453495-61.patch6.1 KBMunavijayalakshmi
#56 add_forum_container-2453495-56.patch6.1 KBSolthun
#51 add_forum_container-2453495-51.patch6.18 KBakashkrishnan01
#48 add_forum_container-2453495-48.patch6.17 KBakashkrishnan01
#42 add_forum_container-2453495-42.patch6.2 KBrosinegrean
#42 interdiff-35-42.txt796 bytesrosinegrean
#38 2453495-before2.png14.75 KBWinthropian
#38 2453495-before.png14.46 KBWinthropian
#38 2453495-after.png15.1 KBWinthropian
#38 2453495-after2.png15.24 KBWinthropian
#35 add_forum_container-2453495-35.patch6.26 KBKetan Harit
#29 Selection_003.png27.46 KBquietone
#29 Selection_002.png29.52 KBquietone
#28 add_forum_container-2453495-28.patch6.25 KBhussainweb
#23 interdiff-2453495-14-23.txt1.08 KBmglaman
#23 add_forum_container-2453495-23.patch6.29 KBmglaman
#16 after_patch.png55.63 KBShivam Agarwal
#14 alter_forum_container_form_alter_fields_solution_2453495-14.patch6.33 KBShivam Agarwal
#14 reproduce_bug_alter_forum_container_form-alter_fields-2453495-14.patch7.22 KBShivam Agarwal
#13 interdiff-2453495-10-12.txt7.43 KBdpopdan
#12 interdiff-2453495-10-12.txt504.46 KBdpopdan
#12 forum_add_alter-2453495-12.patch6.24 KBdpopdan
#10 forum_add_alter-2453495-10.patch13.29 KBdpopdan
#10 interdiff-2453495-7-10.txt11.67 KBdpopdan
#7 forum_add_alter-2453495-7.patch3.58 KBrosinegrean
#7 interdiff-4-7.patch1.7 KBrosinegrean
#4 forum_add_alter-2453495-4.patch2.51 KBdpopdan
#3 forum_add_alter-2453495-3.patch1.36 KBrosinegrean
forum-container-terms.png71.24 KBidebr
forum-terms.png73.06 KBidebr
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

rosinegrean’s picture

Assigned: Unassigned » rosinegrean
larowlan’s picture

We already have a form alter here, so just need to expand what it is doing, and the tests

rosinegrean’s picture

Status: Active » Needs review
FileSize
1.36 KB

Altering the weight description is easy, but for example we already have in ForumForm.php :

    // Set the title and description of the name field.
    $form['name']['#title'] = $this->t('Forum name');
    $form['name']['#description'] = $this->t('Short but meaningful name for this collection of threaded discussions.');
    // Change the description.
    $form['description']['#description'] = $this->t('Description and guidelines for discussions within this forum.');

which are not working anymore. They all come from the baseFieldDefinition of the taxonomy term entity and I don't know what would be the cleaner way to alter this.

dpopdan’s picture

Fixed the basefield titles and descriptions.

dpopdan’s picture

Status: Needs review » Needs work
dpopdan’s picture

Status: Needs work » Needs review
rosinegrean’s picture

Thanks @dpopdan, if this is the solution, then it must be added in the ContainerForm.php as well

The last submitted patch, 7: interdiff-4-7.patch, failed testing.

idebr’s picture

Status: Needs review » Needs work
Issue tags: +Needs tests

@prics @dpopdan Thanks for working on this issue! The new form fields look great, just two points left:

  1. +++ b/core/modules/forum/src/Form/ContainerForm.php
    @@ -29,13 +29,11 @@ public function form(array $form, FormStateInterface $form_state) {
    -    // Alternate description for the container parent.
    -    $form['parent'][0]['#description'] = $this->t('Containers are usually placed at the top (root) level, but may also be placed inside another container or forum.');
    
    @@ -48,4 +46,15 @@ public function buildEntity(array $form, FormStateInterface $form_state) {
    +    $this->entity->get('description')->getDataDefinition()->setDescription('Containers are usually placed at the top (root) level, but may also be placed inside another container or forum.');
    

    The old description was for the 'parent' field and does apply to the container description.

  2. @larowlan mentions in #2 mentions we should expand our tests to make sure this behavior is preserved.
dpopdan’s picture

Status: Needs work » Needs review
FileSize
11.67 KB
13.29 KB

I added some tests and made some refractoring on \Drupal\forum\Tests\ForumTest because it violated the coding standars very bad. I also changed the description for the parent field.

larowlan’s picture

+++ b/core/modules/forum/src/Tests/ForumTest.php
@@ -113,11 +120,11 @@ protected function setUp() {
+  protected function testForum() {

@@ -247,7 +262,7 @@ function testForum() {
+  protected function testAddOrphanTopic() {

@@ -347,12 +362,16 @@ private function doAdminTests($user) {
+  protected function editForumVocabulary() {

@@ -387,15 +406,15 @@ function editForumVocabulary() {
+  protected function createForum($type, $parent = 0) {

@@ -436,10 +455,10 @@ function createForum($type, $parent = 0) {
+  protected function deleteForum($tid) {

@@ -475,7 +494,7 @@ private function doBasicTests($user, $admin) {
+  protected function testForumWithNewPost() {

@@ -511,13 +530,13 @@ function testForumWithNewPost() {
+  protected function createForumTopic($forum, $container = FALSE) {

this needs to be public. Can you revert the coding standards changes and file a new issue (post the link here). Will make it easier to review this and as a bonus, you'll get an extra commit mention. Put me down to review the other issue.

dpopdan’s picture

Wrong interdiff, sorry . The good one in the next comment.

dpopdan’s picture

FileSize
7.43 KB
Shivam Agarwal’s picture

I am uploading two patches one with name contains reproduce which reproduce the problem if already solved and another patch which contains name as solution is patch to resolve that bug.

Shivam Agarwal’s picture

FileSize
55.63 KB

Here is the screenshot of interface after applying patch.

rosinegrean’s picture

@Shivam Agarwal, I don't understand what you did in #14
@larowlan the patch in #12 looks good for me

Shivam Agarwal’s picture

@prics #17 my first patch which failed in testing was created in order to reproduce the problem in case it is rectified on someone's localhost so as to understand where the actual problem was. Second patch is the solution of the problem i.e. the main motive for which issue was created for. I hope that is meaningful now.

larowlan’s picture

  1. +++ b/core/modules/forum/src/Form/ForumForm.php
    @@ -38,15 +38,10 @@ public function form(array $form, FormStateInterface $form_state) {
    +    $form['weight']['#description'] = $this->t('Forums are displayed in ascending order by weight.Forums are displayed in ascending order by weight.');
    

    Any reason why we don't do this one in prepareEntity too?

  2. +++ b/core/modules/forum/src/Tests/ForumTest.php
    @@ -670,4 +674,34 @@ private function generateForumTopics() {
    +      default:
    

    No need for the default

dpopdan’s picture

@larowlan the description for the weight is hardcoded from TermForm, it doesn't came from the entity.

$form['relations']['weight'] = array(
      '#type' => 'textfield',
      '#title' => $this->t('Weight'),
      '#size' => 6,
      '#default_value' => $term->getWeight(),
      '#description' => $this->t('Terms are displayed in ascending order by weight.'),
      '#required' => TRUE,
    );

The same thing is on $form['parent']. So, I think that is OK.

notmike’s picture

I verified that the patch does what it is supposed to, but it adds a tab instead of a space in ForumTestphp at the start of line 355, and it adds an extra space at the end of line 358.

larowlan’s picture

Status: Needs review » Needs work

Based on last review

mglaman’s picture

Status: Needs work » Needs review
FileSize
6.29 KB
1.08 KB
+++ b/core/modules/forum/src/Tests/ForumTest.php
@@ -341,8 +341,13 @@ private function doAdminTests($user) {
+	 // Test for forum specific descriptions and labels.
++    $this->verifyForumForm('forum');
++    // Test for container specific descriptions and labels.
++    $this->verifyForumForm('container');  ¶
...
+

Updated patch to fix tab, space, and extra +'s (noted in #21)

Pinolo’s picture

Tests are failing for the Forums (tested also with clean HEAD).
Failure should be unrelated to the patched code (seems to be about forum topic creation).

Here's the test report.

$ php core/scripts/run-tests.sh --class "Drupal\forum\Tests\ForumTest::testForum"

Drupal test run
---------------

Tests to be run:
  - Drupal\forum\Tests\ForumTest::testForum

Test run started:
  Friday, September 25, 2015 - 13:47

Test summary
------------


Fatal error: Call to a member function id() on boolean in core/modules/forum/src/Tests/ForumTest.php on line 560

Call Stack:
    0.0038     531328   1. {main}() core/scripts/run-tests.sh:0
    1.1101   17534888   2. simpletest_script_run_one_test() core/scripts/run-tests.sh:44
    1.1200   19145520   3. Drupal\simpletest\TestBase->run() core/scripts/run-tests.sh:658
   37.6016   59970600   4. Drupal\forum\Tests\ForumTest->testForum() core/modules/simpletest/src/TestBase.php:1023
   37.9739   60936032   5. Drupal\forum\Tests\ForumTest->generateForumTopics() core/modules/forum/src/Tests/ForumTest.php:158
   37.9740   60936600   6. Drupal\forum\Tests\ForumTest->createForumTopic() core/modules/forum/src/Tests/ForumTest.php:678

FATAL Drupal\forum\Tests\ForumTest::testForum: test runner returned a non-zero error code (255).
- Found database prefix 'simpletest119866' for test ID 1.
[25-Sep-2015 13:48:33 Europe/Rome] PHP Fatal error:  Call to a member function id() on boolean in core/modules/forum/src/Tests/ForumTest.php on line 560
[25-Sep-2015 13:48:33 Europe/Rome] PHP Stack trace:
[25-Sep-2015 13:48:33 Europe/Rome] PHP   1. {main}() core/scripts/run-tests.sh:0
[25-Sep-2015 13:48:33 Europe/Rome] PHP   2. simpletest_script_run_one_test() core/scripts/run-tests.sh:44
[25-Sep-2015 13:48:33 Europe/Rome] PHP   3. Drupal\simpletest\TestBase->run() core/scripts/run-tests.sh:658
[25-Sep-2015 13:48:33 Europe/Rome] PHP   4. Drupal\forum\Tests\ForumTest->testForum() core/modules/simpletest/src/TestBase.php:1023
[25-Sep-2015 13:48:33 Europe/Rome] PHP   5. Drupal\forum\Tests\ForumTest->generateForumTopics() core/modules/forum/src/Tests/ForumTest.php:158
[25-Sep-2015 13:48:33 Europe/Rome] PHP   6. Drupal\forum\Tests\ForumTest->createForumTopic() core/modules/forum/src/Tests/ForumTest.php:678

- Removed test site directory.
- Removed 52 leftover tables.

Test run duration: 38 sec

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

quietone’s picture

Assigned: rosinegrean » Unassigned
Status: Needs review » Needs work
Issue tags: +Needs reroll

Patch doesn't apply to 8.2.x. Setting to unassigned since this hasn't been touched for about one year.

hussainweb’s picture

Status: Needs work » Needs review
Issue tags: -Needs Review, -Needs reroll
FileSize
6.25 KB

Rerolling the patch in #23. Removing 'Needs Review' tag as it was vague.

Done in a live webinar on Drupal contributions.

quietone’s picture

FileSize
29.52 KB
27.46 KB

Thanks. Applied that patch and found 'Forums are displayed in ascending order by weight.' is duplicated on screen. Screen shots follow.

And found a few things.

  1. +++ b/core/modules/forum/src/Form/ContainerForm.php
    @@ -23,14 +23,10 @@ public function form(array $form, FormStateInterface $form_state) {
    +     $this->forumFormType = $this->t('forum container');
    +   // Update the description.
    

    Indentation errors/

  2. +++ b/core/modules/forum/src/Form/ContainerForm.php
    @@ -42,5 +38,24 @@ public function buildEntity(array $form, FormStateInterface $form_state) {
    +  }
    +  /**
    

    Blank link needed here, I think.

  3. +++ b/core/modules/forum/src/Form/ForumForm.php
    @@ -33,15 +33,11 @@ public function form(array $form, FormStateInterface $form_state) {
    +// But update the description.
    
    @@ -164,5 +160,16 @@ protected function forumParentSelect($tid, $title) {
       }
    +  /**
    

    Indentation

  4. +++ b/core/modules/forum/src/Form/ForumForm.php
    @@ -164,5 +160,16 @@ protected function forumParentSelect($tid, $title) {
       }
    +  /**
    

    Blank line.

Screenshots after applying patch in #28

quietone’s picture

Status: Needs review » Needs work

Settings to NW.

larowlan’s picture

Looking good - couple of minor observations

  1. +++ b/core/modules/forum/src/Form/ForumForm.php
    @@ -33,15 +33,11 @@ public function form(array $form, FormStateInterface $form_state) {
    +// But update the description.
    

    nit, indent is wrong

  2. +++ b/core/modules/forum/src/Tests/ForumTest.php
    @@ -686,4 +690,32 @@ private function generateForumTopics() {
    +  protected function verifyForumForm($type) {
    

    this feels like it should be two different methods, verifyForumForm and verifyContainerForm - thoughts?

MaskyS’s picture

Assigned: Unassigned » MaskyS

Will try to work on this so assigning this to myself :)

MaskyS’s picture

Assigned: MaskyS » Unassigned
Ketan Harit’s picture

Assigned: Unassigned » Ketan Harit
Ketan Harit’s picture

Status: Needs work » Needs review
FileSize
6.26 KB
Ketan Harit’s picture

Assigned: Ketan Harit » Unassigned
Winthropian’s picture

I am looking at this as part of SprintWeekend2017

Winthropian’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
15.24 KB
15.1 KB
14.46 KB
14.75 KB

Tested in 8.2 and looks good.

Add Forum before

Add Forum after

Add Container before

Add Container after

tstoeckler’s picture

Status: Reviewed & tested by the community » Needs review
  1. +++ b/core/modules/forum/src/Form/ContainerForm.php
    @@ -23,14 +23,10 @@ public function form(array $form, FormStateInterface $form_state) {
         $form = parent::form($form, $form_state, $taxonomy_term);
    +     $this->forumFormType = $this->t('forum container');
    +   // Update the description.
    +    $form['weight']['#description'] = $this->t('Containers are displayed in ascending order by weight.');
    

    The alignment is wrong here, these should all line up.

  2. +++ b/core/modules/forum/src/Form/ContainerForm.php
    @@ -42,5 +38,24 @@ public function buildEntity(array $form, FormStateInterface $form_state) {
    +    $this->entity->get('name')->getDataDefinition()->setLabel('Container name');
    +    $this->entity->get('name')->getDataDefinition()->setDescription('Short but meaningful name for this collection of related forums.');
    

    This is the first time that we are changing base field definitions in a form and I don't think it's really a good idea. Is there absolutely no way we can do this by actually altering the form array?

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

rosinegrean’s picture

Assigned: Unassigned » rosinegrean
rosinegrean’s picture

Hello,

Fixed the alignment.

For the base field definitions, i don't know of another solution.
So we leave it like this ?
Thanks,

larowlan’s picture

rosinegrean’s picture

So after 2 yers this issue was created, it was merged in another issue created last week ?

larowlan’s picture

Yeah, that's what I'm trying to ascertain.

What I think has happened, is that issue appears to be 'fixed' based on the commit message, but actually, the commit message refers to the wrong issue, and the patch is for something else.

I'm going to close the other one as a duplicate.

larowlan’s picture

Closed the other one and left a tell for lauriii to confirm it was just an issue number mismatch

darius.restivan’s picture

The problem seems to be resolved. Can we change the status into RTBC ?

akashkrishnan01’s picture

patch #42 not applying with my core files. So, I have rerolled this patch with my version.

akashkrishnan01’s picture

Status: Needs review » Needs work

The last submitted patch, 48: add_forum_container-2453495-48.patch, failed testing.

akashkrishnan01’s picture

Rerolled patch with proper coding standard

akashkrishnan01’s picture

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 51: add_forum_container-2453495-51.patch, failed testing.

rosinegrean’s picture

Assigned: akashkrishnan01 » rosinegrean
Issue tags: +DCTransylvania

It looks like you are adding the verifyForumForm() method into the ForumForm class and not the FormFormTest class.
Because the method is not in the test class, the tests fail with "Call to undefined method ..."
I will take a look at it.

Solthun’s picture

Assigned: rosinegrean » Solthun
Solthun’s picture

Re-rolled patch.
Original name field descriptions were not even showing up anymore.
Now all seems to be working fine.

Solthun’s picture

Assigned: Solthun » Unassigned
Status: Needs work » Needs review
quietone’s picture

Found two small things.

+++ b/core/modules/forum/src/Form/ContainerForm.php
@@ -43,4 +39,23 @@ public function buildEntity(array $form, FormStateInterface $form_state) {
+  }
+  /**

Needs a blank line after the method.

+++ b/core/modules/forum/src/Form/ForumForm.php
@@ -165,4 +160,17 @@ protected function forumParentSelect($tid, $title) {
+

Remove extra blank line.

quietone’s picture

Status: Needs review » Needs work
Munavijayalakshmi’s picture

Assigned: Unassigned » Munavijayalakshmi
Munavijayalakshmi’s picture

Assigned: Munavijayalakshmi » Unassigned
Status: Needs work » Needs review
FileSize
6.1 KB
750 bytes

Made changes as per the comment #58. Applying the patch, please review.

akashkrishnan01’s picture

Munavijayalakshmi, thanks for your patch. I have reviewed this patch and seems working, moreover, the duplicate string issue has also been fixed.

quietone’s picture

@akashkrishnan, thanks for review. Can you explain what you mean by 'seems working'? I'm wondering if there is something you are not sure about? Did you install the patch and look at the addforum page? If you did, can you add a screenshot to confirm that this patch fixes the issue?

akashkrishnan01’s picture

FileSize
13.83 KB
14.62 KB
21.16 KB

add_forum_container-2453495-61.patch successfully applied and the issues are fixed now, here I have uploaded a few screenshots showing the fixed areas.

akashkrishnan01’s picture

Status: Needs review » Reviewed & tested by the community
tstoeckler’s picture

Status: Reviewed & tested by the community » Needs work

So my point 2. in #39 was never addressed as far as I can tell. I am going to take a stronger stance now and say that we definitely should not be altering the property definitions at runtime. Let's just override the form directly where we need to.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

sahil.goyal’s picture

As seen that #61 is no longer compatible with the current version so Reroll the patch for the version 9.4.x and attaching the reroll_diff file for the same.

sahil.goyal’s picture

Refactoring the CCF erros at above patch

sahil.goyal’s picture

FileSize
6.25 KB

Sorry, As my PHPCS is not working on my local so i address the fixes manually though

_utsavsharma’s picture

Fixed CCF for #77.
Please review.

_utsavsharma’s picture

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 78: 2453495-78.patch, failed testing. View results

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

sahil.goyal’s picture

quietone’s picture

Status: Needs work » Postponed

Forum is approved for removal. See #1898812: [policy] Deprecate forum module for removal in Drupal 11

This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.

It will be moved to the contributed extension once the Drupal 11 branch is open.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.