I'm glad to hear that. Feel free to create a new issue if you have further questions.
Hi,
I understand your problem now. Yes, when we apply this method, it does not work as expected, sorry for the misdirection. The reason why it doesn't work is that these localization keys come from IdentityResource in ABP's Identity module. So we need to override these localization keys there. This article explains how to do this, you can easily do it by following the article. However, if you have any problems, don't hesitate to ask.
You can also do this via UI as shown in the picture below:
Hi,
Can you send your application to berkan.sasmaz@volosoft.com so I can reproduce your problem?
Hi,
As a result of the information you provided, I was able to reproduce the problem. I will create an internal issue regarding the problem. I will ask you to fix it manually until the issue is resolved. Thank you for your patience.
Closing the issue. Feel free to create a new issue if you have further questions.
Hi,
Looks interesting, please share your solution via email (to support@abp.io with ticket number) if possible, so we can resolve your issue faster.
Sorry for the late reply. I will try to check your solution later today.
Alright, but simply posting a link doesn’t really justify deducting a credit from my ticket budget—especially since we ended up finding a different solution.
I’m processing a refund for your ticket. Normally, even if we only shared a helpful link, it would still count as a support interaction and reduce your ticket balance. Since we aim to assist with every request, and many questions tend to be similar, we try to respond efficiently — even if the solution is already available elsewhere. We appreciate your understanding.
Closing the issue. Feel free to create a new issue if you have further questions.
Hi,
CreatorId and DeletorId are auto-filled using ICurrentUser during HTTP requests. However, in distributed event handling, events are processed asynchronously in another microservice without the original HTTP context, so ICurrentUser data isn’t available, leaving these fields null. I suggest adding CreatorId and DeletorId to the ETO object when publishing the event and then setting them in the event handler as follows:
test.CreatorId = eventData.Entity.CreatorId;
test.DeleterId = eventData.Entity.DeleterId;
Records are deleted after they are published to the event bus. However, if you want to test this, you can test it by setting send to false as below:
This is expected behavior. We disable IsSendingEnabled to show that data is actually written to the Outbox table. Because when the event is published, the record is deleted from the Outbox table and you cannot see it when this process happens very quickly.