Skip to content
This repository has been archived by the owner on Nov 3, 2024. It is now read-only.

Commit

Permalink
added know issues section
Browse files Browse the repository at this point in the history
  • Loading branch information
Valdis Iljuconoks committed Oct 22, 2024
1 parent f1dadaf commit c072a84
Showing 1 changed file with 29 additions and 3 deletions.
32 changes: 29 additions & 3 deletions docs/getting-started-adminui.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,11 +2,12 @@

## Install Package

```
```powershell
> dotnet add package LocalizationProvider.AdminUI.AspNetCore
```

## Configure Services
## Configure Provider

For Minimal API syntax use following set of configuration as your starting point to get AdminUI up & running.

```csharp
Expand Down Expand Up @@ -53,7 +54,7 @@ public class Startup
services
.AddControllersWithViews()
.AddMvcLocalization();

services.AddRazorPages();
services.AddRouting();

Expand Down Expand Up @@ -187,3 +188,28 @@ services
_.AccessPolicyOptions = builder => builder.AddRequirements(...);
});
```

# Known Issues

## Admin UI Returns 404

If accessing AdminUI (by default `/localization-admin`) you get 404, check if you have added Razor page mapping.

```csharp
services.AddRazorPages();

app.MapRazorPages();
```

## Static Files are Missing

Ref: [#213](https://github.com/valdisiljuconoks/localization-provider-opti/issues/213).

Solution is to add static web assets configuration.

```csharp
.ConfigureWebHostDefaults(webBuilder =>
{
webBuilder.UseStaticWebAssets();
});
```

0 comments on commit c072a84

Please sign in to comment.