Hello,
We observed that downgrading the backend packages did not solve the problem. It is solved after downgrading the Angular packages. It is reproducible with a fresh project as well. Anyway, you can get the logs at https://ufile.io/uo4y0w39 .
Best.
Thank you!
Hello again. You cannot reproduce because the whole content of "Emailing" tab on "Settings" page fits in the height of the page in your screencasts. In our case, we disabled the "Emailing" settings for tenants. "Settings" page directly shows the "Identity Management" tab and we face the scroll problem. Alternatively, please try resizing the window so vertical scroll bar shows up on "Settings" page.
I just updated abp cli to version 7.1.1, created a new project and saw the problem. You can find the yarn.lock file at https://pastebin.com/ag6A7sGN
It does not happen with every page pairs. Please try the pages I listed in the original post. Scroll to the bottom on the "Audit Logs" page, then go to "Settings" page.
Hello,
I see your points, fair enough. For future-this-feature-seekers, we will create a new solution with community edition, apply our solution and push it to a new repo at https://github.com/kkeld/CommunityNova . Deleted the repo, closed the question.
Best.
Hello again,
I guess there is a misunderstanding. We did not want you to implement anything for us. There are similar questions like [1], [2]. The usual flow we observed is that: customer asks a question, you ask for clarification, customer elaborates, you ask for sample code, customer gives sample code, you guide them through code. We just wanted to cut that piggy back by supplying a repo with minimal changes only related to the feature we are asking for. We tried explaining what we want and where we failed clearly. We were just expecting some guidance like you yourself requested your colleague and he did so for the issue at [3]. Since we could not get anything new for this question, would you consider amending our question token back?
Anyway, meanwhile we managed to get this working. We updated the repo at [4] in case someone else needs it, too.
