Comments

sourdrup created an issue. See original summary.

sourabh.singhal’s picture

Status: Active » Needs review
StatusFileSize
new433 bytes

Please find the patch attached. Please review this.
Thanks
Sourdrup

Status: Needs review » Needs work
sourabh.singhal’s picture

Status: Needs work » Needs review
StatusFileSize
new433 bytes

Since my last patch test was failed, I double checked, it is applying correctly, the changes works well so I am uploading a new patch file again. Please review

krina.addweb’s picture

Status: Needs review » Needs work

Patch failed.. When creating new term it should not redirect to term view page, only editing term should redirect to term view page.

sourabh.singhal’s picture

Status: Needs work » Needs review

Hi krina.soni,

Problem statement: I am facing a usability issue, do review my statement:
I am trying to edit term from term view page (/taxonomy/term/termid) i.e i am clicking on the "Edit" tab from this page. After Editing the term, when I click on Save, it doesn't redirect to taxonomy term view page. It seems like, this functionality needs to be fixed.

To reproduce this functionality you need to :

1. Add new term in vocabulary. (You are not redirected from this page)
2. Go to Term Listing page and click on the term name not the "edit" link.
3. You were redirected to the Term View page.
4. Now click on "Edit" tab on term view page which will redirect you to term edit page.
5. Now you click on "Save" button which will redirect you back to term view page which was not working earlier.

Thanks
Sourdrup

krina.addweb’s picture

Hi Sourabh,

You are absolutely right, this works fine for me as well. But the issue I am talking about is while creating new term. It should not redirected to term view page.Add time redirection works without patch but with patch it redirects me on view page. Please let me know if you need any clarification.

Thanks

sourabh.singhal’s picture

Thanks krina.soni,

For catching this, I have attached second patch for the same and in this I have fixed the bug of redirecting from term add page.

Sourdrup

krina.addweb’s picture

Status: Needs review » Reviewed & tested by the community

Hi Sourabh,

Now Patch works well as per the requirements.

Thanks

stefan.r’s picture

Does Drupal 8 have this issue as well? If yes, it needs to be fixed there first

sourabh.singhal’s picture

Hi stefan.r,

Yes you are correct, I have checked this issue in Drupal 8.2.3 and it exists in Drupal 8 also. I have prepared patch for the same. Please review.

Sourdrup

krina.addweb’s picture

Hello sourdrup,

Thanks! Your patch works well with Drupal 8.2.3.
Also Thanks @stefan.r

David_Rothstein’s picture

Version: 7.x-dev » 8.2.x-dev
Category: Support request » Bug report
Status: Reviewed & tested by the community » Needs review
Issue tags: +Needs backport to D7
David_Rothstein’s picture

By the way, nice job catching the fact that we want this redirect to be on the "edit" form only, not the "add" form. I definitely think that makes sense, since when adding taxonomy terms it is common to add a few at once.

wturrell’s picture

Assigned: sourabh.singhal » Unassigned
Status: Needs review » Needs work

Changing this to 'needs work' – to get it into core we first a patch name without -do-not-test, so it can be run on testbot.
@sourdrup - I'll also unassign the issue so there's a greater chance of others picking it up if you don't have time yourself (see Assigning Ownership docs)

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.

pk188’s picture

Status: Needs work » Needs review
StatusFileSize
new1.12 KB

Re rolled as #11 failed to apply. And fixed #15.

berdir’s picture

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

Needs tests. I don't understand why the path based edit check is necessary, this is already within the UPDATE case, where we know that we are updating a term?

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.

jeffam’s picture

Updating this patch for 9.x and adding a couple of tests.

jeffam’s picture

jeffam’s picture

StatusFileSize
new1.98 KB

Fixed the array syntax. That's what I get from cutting and pasting from a previous patch.

manojithape’s picture

Assigned: Unassigned » manojithape
manojithape’s picture

StatusFileSize
new16.92 KB

At the time of applying patch#26 on the drupal 9.1.x dev version getting an error and not able to apply the patch. Please refer attached error screenshot.

manojithape’s picture

Assigned: manojithape » Unassigned
Status: Needs review » Needs work
dhirendra.mishra’s picture

Status: Needs work » Needs review
StatusFileSize
new1.98 KB

Hopefully this attached patch will be useful

vikashsoni’s picture

StatusFileSize
new21.44 KB
new49.49 KB

I tried to apply these patches but getting error for reference sharing screenshot

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

Drupal 9.1.10 (June 4, 2021) and Drupal 9.2.10 (November 24, 2021) were the last bugfix releases of those minor version series. Drupal 9 bug reports should be targeted for the 9.3.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

jeffam’s picture

StatusFileSize
new1.96 KB

Here's a patch for 9.3.x

quietone’s picture

Status: Needs review » Closed (cannot reproduce)
Issue tags: -taxonomy terms +Bug Smash Initiative

I tested this on 9.3.x, standard install and when editing a taxonomy term, clicking save, I return to the the term list page. Just to be sure I understood the problem I applied the patch and edited and saved a term. I was again sent to the term list page. The patch does not change the current behavior.

A reminder to anyone working on older patches is to reproduce the problem first. If it can't be reproduced then explain what you did in a comment and close it as cannot reproduce. Lets put our collective efforts into problems that still exist.

Closing as cannot reproduce.

shortspoken’s picture

Status: Closed (cannot reproduce) » Fixed

@quietone: I can reproduce the described problem. The difference lies in a small but important detail: from where you click the edit button.

As @sourabh.singhal describes it, its about the term view page ('/taxonomy/term/[tid]') where "edit" is clicked. Like you would edit a node in frontend via the edit tab. The expected behaviour when you click save would be to return to the view/full page where you clicked "edit" (as it is with nodes).

But when doing so with a taxonomy term, you click save but you stay on the edit form with success message that the term has been updated.
Yay! But please take me back to the view page. ;)

I can confirm that the patch from #33 leads to the desired behaviour.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

quietone’s picture

Status: Closed (fixed) » Needs review

@shortspoken, thanks for the explanation. I retested on 9.5.x, this time correctly, and did reproduce the problem.

Setting back to NR.

asha nair’s picture

StatusFileSize
new726.26 KB

Applied patch #33 in 9.5.x successfully. The patch fixes the issue. Adding screen recording for reference

Manibharathi E R’s picture

StatusFileSize
new155.52 KB
new70.62 KB

Patch #33 Applied and tested successfully on Drupal 9.5.x.

Steps to reproduce:
1. Create a new term in the Vocabulary.
2. Open the term page and click the edit page. Screen will be redirect to the term edit page.
3. Now save the edit form. Screen not redirect to the Term page.
4. Apply the Patch and try to save the edit form screen will be redirect to the term View page.

Before-Patch:
Before-Patch

After=Patch:
After-patch

ameymudras’s picture

Status: Needs review » Reviewed & tested by the community

Tested on Drupal 9.5.x

- Issue summary is clear and was able to reproduce the issue
- The patch #33 applies cleanly
- After applying the patch the redirect works as expected. Not adding a before after patch coz #39 already has provided it
- Test is included
- No issues seen in the code

Moving to RTBC

  • catch committed 4a5ae1c on 10.0.x
    Issue #2826592 by sourabh.singhal, jeffam, dhirendra.mishra, pk188,...
  • catch committed fa7f5a0 on 10.1.x
    Issue #2826592 by sourabh.singhal, jeffam, dhirendra.mishra, pk188,...
  • catch committed c581259 on 9.5.x
    Issue #2826592 by sourabh.singhal, jeffam, dhirendra.mishra, pk188,...
catch’s picture

Version: 9.3.x-dev » 9.5.x-dev
Status: Reviewed & tested by the community » Fixed

Committed/pushed to 10.1.x, cherry-picked to 10.0.x and 9.5.x, thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.