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

ResourceLocator can not find a web root (root: /var/snap/nextcloud/20007/nextcloud/extra-apps/breezedark, file: index.php/css/breezedark/e4f6-98be-server.css?v=0008b43623c11f070e05fc2eff232fe7, webRoot: , throw: true) #107

Closed
hackeresq opened this issue Apr 7, 2020 · 3 comments
Labels

Comments

@hackeresq
Copy link

hackeresq commented Apr 7, 2020

Describe the bug
This error is logged when the theme is enabled.

ResourceLocator can not find a web root (root: /var/snap/nextcloud/20007/nextcloud/extra-apps/breezedark, file: index.php/css/breezedark/e4f6-98be-server.css?v=0008b43623c11f070e05fc2eff232fe7, webRoot: , throw: true)

To Reproduce
Steps to reproduce the behavior:

  1. enable the theme
  2. check nextcloud.log

Expected behavior
No error logged.

Screenshots
available upon request

Setup (please complete the following information):

  • Nextcloud version: 17.0.5
  • Theme version 17.0.5
  • Browser and browser version Microsoft Edge Version 79.0.309.65 (Official build) (64-bit)

Additional context
Using the latest stable snap for nextcloud on Ubuntu.

@hackeresq hackeresq added the bug label Apr 7, 2020
@mwalbeck
Copy link
Owner

mwalbeck commented Apr 7, 2020

Hi,

I've looked a bit into this, and from what I can see it seems to be an upstream issue nextcloud/server#13556. It is of course made much worse using this theme, as the stylesheet is loaded on every page compared to other apps, where it is only when you use them. Looking through the different issues on this, I haven't been able to find a workaround/fix that I can implement on my side.

@hackeresq
Copy link
Author

That's frustrating. But thanks for looking in to it. I'll close this issue.

Any ideas what needs to be fixed in the core server app to eliminate this? Seems like it's not recognizing resources outside of the webroot.

@mwalbeck
Copy link
Owner

mwalbeck commented Apr 7, 2020

Better handling of symlinks for resources, seems to be what's needed. One part of the fix is made and waiting to be included into NC19, but it doesn't seem like there is a proper fix for the symlink part yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants