Open Closed

Audit logging is broken for Blazor Server Projects #2969


User avatar
0
jopperman@waltons.co.za created
  • ABP Framework version: v5.2.1
  • UI type: Blazor Server
  • DB provider: EF Core
  • Exception message and stack trace:
  • Steps to reproduce the issue: Create a Blazor Server project using the suite. Create a basic crud entity and enable auditing by adding the [Audited] tag to the class. Entity changes through swagger will log correctly. Changes through the Blazor UI do not.

As per the title and information above, a core feature of the ABP Commercial does not work. There seems to be very little priority to resolve this.


7 Answer(s)
  • User Avatar
    0
    gterdem created
    Support Team Senior .NET Developer

    Intercepting Blazor Page events issue is open for more than 1 year by Microsoft and it is directly related to it.

    We are also trying to figure out a different way to solve this problem however we are pretty limited on tools to use on Blazor side.

    You can also follow the progress at issue#11682.

  • User Avatar
    0
    jopperman@waltons.co.za created

    This wasn't an issue on < 5.2 of ABP

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    hi

    Can you try this?

    https://github.com/abpframework/abp/issues/11682#issuecomment-1059019021

  • User Avatar
    0
    jopperman@waltons.co.za created

    Created a fresh 5.2.1 Blazor Server project using the suite, getting "type or namespace AbpUowHubFilter not found"

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    hi

    Please remove AbpUowHubFilter and AbpAuditHubFilter to try

  • User Avatar
    0
    jopperman@waltons.co.za created

    Looks like that did the trick thank you! I will run some more testing over the coming days

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    Good news.

Made with ❤️ on ABP v8.2.0-preview Updated on March 25, 2024, 15:11