Notification editor doesn't close when saving a draft about orchardcore HOT 13 CLOSED

@maksim-markin We understand that you created a type name "Global Notification" and this is not related to the notifications module (that was confusing so I prefer the state it).

My understanding of the issue is that the return url is lost when we switch languages, so publishing a new localized version won't go back to the content items page like when create a new content item does.

from orchardcore.

Thank you for submitting your first issue, awesome! 🚀 We're thrilled to receive your input. If you haven't completed the template yet, please take a moment to do so. This ensures that we fully understand your feature request or bug report. A core team member will review your issue and get back to you.

If you like Orchard Core, please star our repo and join our community channels.

from orchardcore.

@MikeAlhayek is this by design?

from orchardcore.

I am not sure. I did not design the culture feature

from orchardcore.

I thought it was notification-related. I will have a look then

from orchardcore.

This behavior actual with every content type not for only notification

from orchardcore.

Please another screenshot

from orchardcore.

1. Open Manage Content (type = page)
   

2. Edit some page (there is a returnUrl param) and change current localization
   

3. Localized version has been created (there is no returnUrl param)
   

4. After published, page doesn`t close
   

from orchardcore.

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

from orchardcore.

I kind of agree with the expectation, that we should return to the previous returnUrl value if there was one.

from orchardcore.

@maksim-markin We understand that you created a type name "Global Notification" and this is not related to the notifications module (that was confusing so I prefer the state it).

My understanding of the issue is that the return url is lost when we switch languages, so publishing a new localized version won't go back to the content items page like when create a new content item does.

This behavior actual with every content type not for only notification
See screens above

from orchardcore.

Related Pull Request: #16325

from orchardcore.

I unassigned myself while you started a PR

from orchardcore.