Activities of "EngincanV"

Can you change the version parameter to a specific version (like 1.0) instead of the latest and try again? Also please set the route prefix to null, if you haven't set yet.

This is just uploaded code from your zip files so I can´t set the prefix route there. But I have followed your instructions to the letter there.

I have this project on GitHub but I can´t access the Admin URL (https://localhost:44370/Docs/Admin/Projects)

I followed the module instructions for this project (see url) but can´t seem to access the admin projects endpoint so I can´t try it out. Shouldn´t it be just https://localhost:44370/Docs/Admin/Projects just like the one from the zip?

Hi, as far as I see your project doesn't contain the admin projects. So to reach the Docs/Admin/Projects route you need to add the Volo.Docs.Admin.Web project to your web project:

typeof(DocsAdminWebModule)

and other admin projects to your corresponding projects.

Documents get pulled but still 404

I seem to have managed to pulled in the documents but they are just not showing I just get 404

Can you change the version parameter to a specific version (like 1.0) instead of the latest and try again? Also please set the route prefix to null, if you haven't set yet.

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

Can you check the steps that I've written in this comment and check with your configurations? It should work because I've created a repository with the same structure as yours to provide you with better information about the integration of the Docs module.

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.