Activities of "EngincanV"

Unfortunately, I cannot share the source code, but I'll try to describe what I've found out.

I've revealed that the issue happens when I am trying to modify HttpContext response stream. I have to return custom JSON response when my application throws an exception. For this goal, the middleware has been created. It analyzes HttpContext response headers and replaces this response stream - when an exception happens - with custom JSON response. The middleware uses IAuditingManager to collect the information about errors.

Do you have any idea how modifying HttpContext response stream may affect IAuditLogRepository logic?

Hi, actually it shouldn't affect the repository, but I'll check and write you back asap.

@EngincanV yes we acknowledge that these things can happen and are trying to await patiently fot the patch.

So could you let us know if the patch shippes today or tomorrow so we can do some planning around it?

Like I have stated we are just stuck and can’t move to production because of this so its critical to be getting it soon.

Thank you

We'll start to release today, thanks for your patience.

Best Regards.

Hi again and sorry for the late response, I've created a repository and go with the same structure as yours.

• Here is my project form:

I've used "Branches" as my Github Version Provider source, instead of "Releases". See my rel-1.0 branch So your root URL should be -> "https://github.com/Ibeinni/docs/tree/{version}/" and main website url should be -> "/"

• I've also set some configuration in my web project as below:

        Configure<DocsElasticSearchOptions>(options =>
        {
            options.Enable = true;
        });
        
        Configure<DocsUiOptions>(options =>
        {
            options.RoutePrefix = null; //it need to be null otherwise documents prefix is added the url
            options.ShowProjectsCombobox = false;
        });

Enabling ElasticSearch is optional, however, it's good for full-text search, so maybe you also want to enable it. I've also set route-prefix as null because otherwise "documents" prefix is added to the URL.

Then I opened the admin project and pull documents from there. Then I could successfully see my document text on the website.

Hi @EngincanV have you had time to create this repository?

Hi, sorry for the late response. I'll create a new repository and share the necessary steps with you to integrate with Docs Module during the day.

Hi @Sturla, we are sorry for that and we are aware of it's a bad experience for you but it was caused by the obfuscation process while releasing and it was almost impossible to find the problem at that stage. We've addressed the problem and fixed it but we need to release a new version (5.3.1) and we'll release it asap. Sorry for this kind of problem and thanks for your patience.

Did this but not working.

Sorry to hear that. I guess there is nothing we can do (except excluding the cms-kit-pro module) at this point. Please wait for v5.3.1, we'll release it soon.

This error was caused after the obfuscation process when released the v5.3.0. To fix this problem, maybe you can try to disable the polls feature by using the GlobalFeatures :

GlobalFeatureManager.Instance.Modules.CmsKitPro(cmsKitPro =>
{
    cmsKitPro.Disable<PollsFeature>();
});

@EngincanV you got something else for me to try out?

I'll create a repository and try to integrate it with the docs module and share the steps with you.

We've fixed this problem and it will be available with v5.3.1.

This issue can be reproduced when you are trying to save some error (the exception which happens in your application). Have you reproduced this case?

Yes, I tried in that case but couldn't reproduce the problem. If it's possible can you share your class that implements the IAuditingStore?