I'm seeing a lot of 404s in the logs - all for the page [domain]/theme/default/style.css

Comments

hectorplus’s picture

Same here:

Reporst > Top Page Not Found
theme/default/style.css

xurizaemon’s picture

Status: Active » Needs work

This is in profiles/managingnews/libraries/openlayers/OpenLayers.js -

this.theme=OpenLayers._getScriptLocation()+'theme/default/style.css';

tran_tien’s picture

same here, but i do not using this module ??

xurizaemon’s picture

@tran_tien, are you using OpenLayers? If not, then although the symptoms may be the same it's unlikely this is the same issue you're having.

It may be that this is a JS issue in OpenLayers (theme/default/style.css is actually a CSS from OpenLayers, not a Drupal theme CSS).

Possible also that OpenLayers._getScriptLocation() is befuddled by Drupal CSS aggregation.

sainzu’s picture

So, is it safe to simply remove that line from the OpenLayers.js file? What is the recommended resolution?

sainzu’s picture

Issue summary: View changes

Updated issue summary.

basvredeling’s picture

Project: Managing News » Openlayers
Version: 6.x-1.2 » 7.x-3.x-dev
Issue summary: View changes

This is an OpenLayers issue... (and applies to 7.x-2.x still)

@sainzu It's not a solution to simply remove that line from the openlayers library. The bigger issue here is that the script location is relative to the drupal root if you use css aggregation. And I believe it shouldn't even be loaded by default if you use the "dark theme".

basvredeling’s picture

It could be related to this issue:
https://github.com/openlayers/openlayers/issues/1067

Short recap:
If you enable the overview map behavior, the theme of the main map is set, but the theme of the overview map is not properly inherited or disabled. Hence the autoloaded $script_uri/theme/default/style.css
Now, this only happens to me if I enable JS aggregation. Any one can confirm this?

m.stenta’s picture

Status: Needs work » Closed (cannot reproduce)

Is this still an issue in the 7.x-3.x branch? I've never seen this error. Please reopen (and/or move to the 7.x-2.x queue) if you're still experiencing it.