Activities of "EngincanV"

So maybe it was the "index" vs "Index" thing?

Yes, i think it was related with that. Because, it checks the default page and then pull the documentations.

One thing for you, there is something wrong with the styling of the header up in the left corner.

Yes, it seems there are styling problems when using the Docs module with Lepton theme. (It works great with Basic Theme) I'll create a new issue for that. Thanks.

To solve the ** ("HTTP Error 500.30 - ASP.NET Core app failed to start")** error, please add the following section to your appsettings.json file:

  "ElasticSearch": {
    "Url": "http://localhost:9200"
  },

I've cloned your repository (https://github.com/sturlath/Acme.MyProject) and try the docs module.

1. I've created a new project as below:

• Your index page is index.md instead of Index.md, so please change it in the form. (I mean default document name should be index for you.)

This naming might be the problem to prevent you to view your docs.

2. Then click the pull action for the project as in the below ss (you don't need to add records manually):

3. This should pull the index page for the English and for other pages. You can check from documents page from your admin panel.

4. Then you should be able to view the docs.

I hope it works for you.

Have you really tried doing this with my code (Github+insert records)?

Shouldn´t it show some documents on the document page if there are records in the database?

I don´t know what to do here... file new project + module installing + connecting to Github and getting data == not working

Yes, I've tried it and you can see the screenshots from this answer.

But I'll try it again and try to understand what is the problem you're facing with.

Again here is the data I got in the docs tables. Don´t you get 404?

No, I didn't get a 404 error after these steps.

Did you configure the DocsUiOptions as below?

Configure<DocsUiOptions>(options =>
{
    options.RoutePrefix = null;
});

If you didn't then you need to add the /documents route as a prefix to your URL. (/documents/en/abp/latest).

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.