Hello, I have investigated this problem by the following the same pattern. Your problem should have occurred only for
@abp/ng.feature-managementpackage depending on the optional package selection. Also, thank you for reporting the related deprecations. These issues will be resolved by the next release where you can find details here.Hi,
Thanks for looking into this. Good to know there will be a general fix coming but will that also fix the deprecated packages warnings? At least they remained for the solution we did as mentioned above. It seems that a fix for that is already in the /dev branch but for whatever reason never made it into 8.3
Please refund ticket as this is now a confirmed bug.
Thanks.
Sure, I will refund your ticket and the deprecations will also be resolved.
Hello, I have investigated this problem by the following the same pattern. Your problem should have occurred only for @abp/ng.feature-management package depending on the optional package selection. Also, thank you for reporting the related deprecations. These issues will be resolved by the next release where you can find details here.
I wish this could have helped you, but it seems that there’s an aspect of the configuration that I’m not fully knowledgeable about to resolve the issue. From what I understand of your setup, it appears that the problem is not on our side. I understand that the proposed change affects the redirection to the login page in a passive tab after logging off in the active tab, and I apologize for any inconvenience this may cause.
Hello, I believe I had reproduced the same problem. The issue might be related to this condition event.newValue === null as can be seen in the record.
Hello, I have also been checking by following the steps that you have provided during the conversation. However, I could not reproduce any of the findings.
So, my first question would be whether you just want to overcome the network errors. If this is the case, you should be checking your service functionalities since we do not trigger anything extra among these processes. At this point, I want to remind you the fact that we send two different requests for connect/revocat to revoke both tokens as being access and refresh. If this is not your case and you just want to redirect user to the login or home page, that is discussable.
Also here is what I experience while logging out as you have explained.
Hello, thank you for reporting this problem of extra alert, and it will be fixed with the next patch release. You can follow the releases through this page.
Hello, if you do not want to use CSS override to hide the settings, you can utilize the component replacement as in this documentation. You can also get a reference to sustain this approach from this explanation.
There is no problem. It is my duty to check and respond. However, the MVC project should also handle it in the same way.
Actually, it should behave in the same way as you can see in this recording https://drive.google.com/file/d/14XC2Ay4W7Af5qMHDn3xzGV7xgfS82XVw/view
Merhaba, yaşadığınız sorunu kendi tarafımda tekrarlayamadım, ancak hata lokalizasyon tarafından geldiği için başka bir implementasyon ile ilgili olabilir.
Eğer amacınız sadece yetkilendirme ile ilgili değişiklikleri yönetmekse bu dökümana göz atmanızı öneriyorum. Aynı zamanda giriş sayfasını özelleştirmek isterseniz buradaki adımları takip edebilirsiniz.
