You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know how much of an issue this is, but the Glyphicons Halflings paths in corporate.css are pointing to a non-existent location (../fonts/bootstrap/ rather than ../fonts/) - presumably a throwback to earlier iterations of e107.
I'm including this CSS file via themes.php on one particular page, and was wondering why my Apache error.log file was full of debug messages from my index page. It seems that when the browser accesses corporate.css, and attempts to reach the Halflings files, my web server responds to this "miss" by serving up the default site page. But this might be unique to my configuration, I haven't probed very far into the what and how.
The text was updated successfully, but these errors were encountered:
Moc
added
type: bug
A problem that should not be happening
and removed
status: testing required
Someone needs to confirm this issue's existence and write a test to prevent the fix from regressing.
labels
Nov 26, 2019
I don't know how much of an issue this is, but the Glyphicons Halflings paths in corporate.css are pointing to a non-existent location (../fonts/bootstrap/ rather than ../fonts/) - presumably a throwback to earlier iterations of e107.
I'm including this CSS file via themes.php on one particular page, and was wondering why my Apache error.log file was full of debug messages from my index page. It seems that when the browser accesses corporate.css, and attempts to reach the Halflings files, my web server responds to this "miss" by serving up the default site page. But this might be unique to my configuration, I haven't probed very far into the what and how.
The text was updated successfully, but these errors were encountered: