[17.0] mig web chatter position - #2895
Closed
tva-subteno-it wants to merge 16 commits into
Closed
tva-subteno-it wants to merge 16 commits into
tva-subteno-it wants to merge 16 commits into
Conversation
mailing module - Because the chatter in mass mailing form view lie under a notebook tab, if user choose sided chatter, it will disappear
Contributor
|
Could you fix precommit errors ? |
Author
|
Hello everyone, this PR was created because the other PR (#2893) was not ready. But I think it is now. So if anyone of you has the opportunity to do so, can you go check this one out, for the code review, and merge it when ready? |
Member
|
Superseded by #2893. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This a fork from 2833
I know there is another PR currently opened (2893) but this one doesn't seem to work. On the other hand, the original PR (2833) was working fine. So not knowing why the second one was created, and being in the urge to migrate this module for a customer, I'm opening this PR and letting you decide which one works best for you.