Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

default skin install css and images not loading in browser

189 views
Skip to first unread message

Scott Bickford

unread,
Feb 5, 2016, 6:13:38 AM2/5/16
to support-...@lists.mozilla.org
I am finishing up a grueling install on RedHat 7 of Bugzilla 5.0.2.

On the default skin, the css files get ok in the browser, but the images do
not load in the browse.

On Fiddler, I can see a 200 status code on for example two
http://mybox/bugzilla/data/assets/2f5735cf3abd04bddc8e363a8613a9f5.css and
two js files.

There is nothing else after these two gets.

So, some content in one of them is :

#help { background: url(../../skins/standard/index/help.png)

That file is located in /var/www/html/bugzilla/data/assets

I was thinking of doing a symlink for /var/www/skins, but was wondering if
there's another way to fix this? I came across a link for someone else who
had similar problems, but it was with version 3.

Thorsten Schöning

unread,
Feb 5, 2016, 6:41:03 AM2/5/16
to support-...@lists.mozilla.org
Guten Tag Scott Bickford,
am Freitag, 5. Februar 2016 um 12:13 schrieben Sie:

> On Fiddler, I can see a 200 status code on for example two
> http://mybox/bugzilla/data/assets/2f5735cf3abd04bddc8e363a8613a9f5.css and
> two js files.

> There is nothing else after these two gets.

This sounds like there's some problem with the CSS itself in your env,
else the browser would at least issue requests for the images.

> #help { background: url(../../skins/standard/index/help.png)
> That file is located in /var/www/html/bugzilla/data/assets

> I was thinking of doing a symlink for /var/www/skins

But that would be the wrong path, /var/www/html/bugzilla/skins is the
proper path and that's exactly what the relative path in the css file
resolves to. Sounds like your web server setup is wrong.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning E-Mail: Thorsten....@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/

Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Scott Bickford

unread,
Feb 5, 2016, 8:52:25 AM2/5/16
to support-...@lists.mozilla.org
The mime types were missing from the httpd.conf. It seems that httpd.conf
references /etc/mime.types, but I am unsure of the format, so for now I
just put it in httpd.conf.

AddType text/css .css
AddType text/javascript .js


Thanks,

darrag...@adaptcentre.ie

unread,
Sep 13, 2018, 7:12:52 AM9/13/18
to
Hello,

I had the same issue on Oracle Linux.

I have solved by the following command

sudo mv /var/www/html/bugzilla/data/assets/.htaccess /var/www/html/bugzilla/data/assets/ORIG_htaccess

sudo systemctl restart httpd


Now all CSS and JS loads.

Regards,
Darragh

Thorsten Schöning

unread,
Sep 13, 2018, 8:15:46 AM9/13/18
to support-...@lists.mozilla.org
Guten Tag darrag...@adaptcentre.ie,
am Donnerstag, 13. September 2018 um 13:12 schrieben Sie:

> sudo mv /var/www/html/bugzilla/data/assets/.htaccess
> /var/www/html/bugzilla/data/assets/ORIG_htaccess

The file you have moved is recreated by checksetup.pl, so depending on
what your actual problem was, you might have worked around it only
temporarily. There have been problems in the past with updating
.htaccess-files, so run checksetup.pl now and see if things still work
with a newly generated file. If not, you further need to debug your
problem.

darrag...@adaptcentre.ie

unread,
Sep 13, 2018, 8:23:36 AM9/13/18
to
On Friday, February 5, 2016 at 11:13:38 AM UTC, Scott Bickford wrote:
Hello Thorsten,

Thanks for your response, I have moved checksetup.pl to a different name, to avoid any accidental executions of that script.

I could see originally it generated the .htaccess file. Now everything seems fine, I will repost if that status changes.

Cheers,

Thorsten Schöning

unread,
Sep 13, 2018, 8:53:11 AM9/13/18
to support-...@lists.mozilla.org
Guten Tag darrag...@adaptcentre.ie,
am Donnerstag, 13. September 2018 um 14:23 schrieben Sie:

> Thanks for your response, I have moved checksetup.pl to a different
> name, to avoid any accidental executions of that script.

Which is the wrong thing to do, because you are simply breaking
your Bugzilla further: Your renamed .htaccess e.g. cared about
security of that folder by disabling directory listings, which might
or might not be the case anymore. Additionally, checksetup.pl itself
is needed in case of template customizations, adding extensions and
for upgrades. So unless you plan to not fix any security bugs anymore,
you are going to execute it anyway and might or might not remember the
problem with the .htaccess at that time.

Darragh Blake

unread,
Sep 13, 2018, 9:45:16 AM9/13/18
to mozilla.supp...@googlegroups.com, support-...@lists.mozilla.org
Hello Thorsten,

Thanks for your response, I have moved checksetup.pl to a different name,
to avoid any accidental executions of that script.

I could see originally it generated the .htaccess file. Now everything
seems fine, I will repost if that status changes.

Cheers,
Darragh

On Thu, Sep 13, 2018 at 1:15 PM, Thorsten Schöning <tscho...@am-soft.de>
wrote:
--
Kind regards,

*Darragh Blake* | Software Development Engineer
ADAPT Centre
O'Reilly Building
Trinity College Dublin
Dublin 2 e: darrag...@adaptcentre.ie
Ireland www.adaptcentre.ie
<https://twitter.com/adaptcentre>
<https://www.facebook.com/ADAPTCentre?fref=ts>
<https://www.youtube.com/channel/UC9--qVutTtyLyhZCJR7rY5g>
<https://www.linkedin.com/company/adapt-centre>

Darragh Blake

unread,
Sep 13, 2018, 9:45:16 AM9/13/18
to mozilla.supp...@googlegroups.com, support-...@lists.mozilla.org
Hello,

Its only running on an internal machine on a private network, I wont
require updates. I only need Bugzilla for a couple of weeks, hence when I
am not spending time troubleshooting the bug.

Cheers,
Darragh

On Thu, Sep 13, 2018 at 1:52 PM, Thorsten Schöning <tscho...@am-soft.de>
wrote:
0 new messages