-
- 65 Posts
If it were my choice I’d do a check for this issue and present an error notice on the manager home page... similar to if you have globals on.... Maybe distinguish it somewhat from the other errors by making it a version incompatibility notice or something with a different color or put a border around it or something. Could be a standard way to notify people that a setting is not properly configured (which should only happen during an upgrade, but would be useful regardless).
This would avoid the mistake of changing people’s settings (in case they have customized things) but would notify them of the issue. If they are savvy enough to customize things to where they don’t want to see this notice every time they log in, then they can go and comment out this notice in the code... or you could make a preference to not show notices.
-
- 4,205 Posts
Each server will have it’s own path. You can see your base path in the phpinfo() output (Reports > System Info). Look for the DOCUMENT_ROOT.
I got it.
I needed to add the path with /assets at the end to Resource Path field in Interface & Features settings.