Skip to content

[Bug]: Resource manager stopped loading after 9.13 upgrade #5862

@enfJoao

Description

@enfJoao

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

Resource manager does not load after upgrading a 9.11 install to 9.13.

Steps to reproduce?

  1. Open any page with resource manager module.

Current Behavior

No response

Expected Behavior

No response

Relevant log output

Uncaught ReferenceError: Sys is not defined
    <anonymous> https://a.b.pt/DependencyHandler.axd/4441d4162baee209bf0fce4aefed650d/257/js:361
    <anonymous> https://a.b.pt/DependencyHandler.axd/4441d4162baee209bf0fce4aefed650d/257/js:361
js:361:2071
GET
https://a.b.pt/DesktopModules/ResourceManager/Scripts/dnn-resource-manager/p-d40a4dd7.entry.js

Loading module from “https://a.b.pt/DesktopModules/ResourceManager/Scripts/dnn-resource-manager/p-d40a4dd7.entry.js” was blocked because of a disallowed MIME type (“text/html”).
File-Management
Loading failed for the module with source “https://a.b.pt/DesktopModules/ResourceManager/Scripts/dnn-resource-manager/p-d40a4dd7.entry.js”. File-Management:238:117
TypeError: error loading dynamically imported module: https://a.b.pt/DesktopModules/ResourceManager/Scripts/dnn-resource-manager/p-d40a4dd7.entry.js undefined p-7f611392.js:1:10722
Uncaught (in promise) TypeError: can't access property "isProxied", o is undefined
    rt p-7f611392.js:1
    ut p-7f611392.js:1
    connectedCallback p-7f611392.js:1
    jmp p-7f611392.js:1
    connectedCallback p-7f611392.js:1
    dt p-7f611392.js:1
    dt p-7f611392.js:1
    <anonymous> patch-browser.js:65
    promise callback* patch-browser.js:65
p-7f611392.js:1:8676
Some cookies are misusing the recommended “SameSite“ attribute 13
Source map error: Error: request failed with status 404
Resource URL: https://a.b.pt/DesktopModules/ResourceManager/Scripts/dnn-resource-manager/p-7f611392.js
Source Map URL: p-7f611392.js.map

Anything else?

No response

Affected Versions

9.13.0 (latest release)

What browsers are you seeing the problem on?

Firefox

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions