atfatmc/AdamuSw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Load the log viewer script from the path it is actually served on

Browse Source 
The admin panel sets StaticWebAssetBasePath to _content/<assembly>, so the
colocated module is served as
/_content/MUnique.OpenMU.Web.AdminPanel/Pages/LogFiles.razor.js. The import
asked for "./Pages/LogFiles.razor.js", which resolves against the page url
/logfiles and answers 404. The failure is caught and logged, so the viewer
still renders - it just never scrolls itself.

Build the path from the assembly name the way ThemeSelector and MapEditor
already do.
This commit is contained in:
Acentech Dev
2026-08-13 09:13:56 +03:00
parent 233ad41f6b
commit d60aad7d2f
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/Web/AdminPanel/Pages/LogFiles.razor
View File

@@ -143,6 +143,11 @@
private const int LiveUpdateIntervalMs = 2000;
private const string TerminalElementId = "log-terminal";
// The admin panel publishes its static web assets under _content/<assembly>, so a path relative
// to the page url ("./Pages/...") does not resolve. Mirrors ThemeSelector and MapEditor.
private static readonly string JsModulePath =
$"./_content/{typeof(LogFiles).Assembly.GetName().Name}/Pages/{nameof(LogFiles)}.razor.js";
private readonly List<FileInfo> _files = new();
private FileInfo? _selectedFile;
private long _lastFileLength;
@@ -187,7 +192,7 @@
{
try
{
this._jsModule = await this.JSRuntime.InvokeAsync<IJSObjectReference>("import", "./Pages/LogFiles.razor.js");
this._jsModule = await this.JSRuntime.InvokeAsync<IJSObjectReference>("import", JsModulePath);
}
catch (JSException ex)
{