Closed (cannot reproduce)
Project:
Openlayers
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Jun 2011 at 08:44 UTC
Updated:
31 Dec 2015 at 13:54 UTC
Jump to comment: Most recent
Comments
Comment #1
hectorplus commentedSame here:
Reporst > Top Page Not Found
theme/default/style.css
Comment #2
xurizaemonThis is in profiles/managingnews/libraries/openlayers/OpenLayers.js -
this.theme=OpenLayers._getScriptLocation()+'theme/default/style.css';Comment #3
tran_tien commentedsame here, but i do not using this module ??
Comment #4
xurizaemon@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.Comment #5
sainzu commentedSo, is it safe to simply remove that line from the OpenLayers.js file? What is the recommended resolution?
Comment #5.0
sainzu commentedUpdated issue summary.
Comment #6
basvredelingThis 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".
Comment #7
basvredelingIt 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?
Comment #8
m.stentaIs 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.