Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v9.11.0 RTM] Client Dependency fails on Portals having a named Portal Directory #5326

Open
2 tasks done
BeniFreitag opened this issue Sep 30, 2022 · 3 comments
Open
2 tasks done

Comments

@BeniFreitag
Copy link
Contributor

Description of bug

On Portals having a Portal directory like /Portals/third Client Dependency fails as soon as Composite Files is enabled.

Steps to reproduce

  1. Go to Manager > Sites > Add New Site
  2. Select Site Type: Directory, Cange Directory to a named Directory, like Portals/third
  3. Create Site
  4. On the new Site, set Enable Composite Files to On
  5. All CSS and JavaScripts will not load anymore

Current behavior

Requests to CSS and JavaScript return http 404 Not Found.

Expected behavior

Requests to CSS and JavaScript should return http 200 with content.

Screenshots

image

Error information

Request like these return http 404:

  • GET /DependencyHandler.axd/08f74c46ae5b971972a0e14a6983dcb6/194/css
  • GET /DependencyHandler.axd/54765520a7ee40bb82780084b1f35010/194/js

Additional context

When the Portal Directory is Portals/[PortalID] (default, resulting to /Portals/1), the issue does not occur.

Affected version

  • 09.11.00 RTM

Affected browser

  • Chrome
@trouble2
Copy link

I'm seeing similar issues in DNN 9.11.0 when viewing the 404 page.
So after searching, I also found this related issue:
#4908

Seems to be something which is still active on 9.11.0 so my 404 page redirect to the xcilion skin rather then the skin it should show.,,,

@trouble2
Copy link

And perhaps also this issue:
#3999

@valadas valadas added this to the Future: Patch milestone Jan 18, 2023
@stale
Copy link

stale bot commented Jun 18, 2023

We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically.
If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!

@stale stale bot added the stale label Jun 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants