How do I find location of inline css?

Hello;
I am using firebug. It used to tell me which css file and line number when inspecting an element. With this template it just tells me inline:#. Is there a way to locate the exact css file and line number?

Hi

Can You please show me about which element are You talking about?

I have the same problem

Firebug doesn't show the location of css file to edit. it shows a #number but don't know whats CSS correspond to this number

in the attached screenshot i select the logo and firebug doesn't show the css asociated

I attached a screenshot

I don't have this problem with other templates opened in the same browser sesion on local host too

Thanks

Hi

Can You please show me about which element are You talking about?

You have the same problem with the DEMO template you can check there. Firebug doesn't show the css rute

I think its a template bug

Hi

This is because of css compression. A solution for that is to not looking for a right file, but simply overwrite the value in override.css file (please remember that You need to allow using of this file in template settings). This way, all changes will be separated from rest of the template and it will be much easier to keep template up to date.

Hello,

Please, how can I disable this css compression?
It's very uncomfortable for me as I need to do particular changes in the css files.

Please, could you explain how to come back to a "normal css files visibility"?
Thanks
Philippe

HI

All You need to do is to disable CSS compression in template settings. If You have used any plugin (none with such functionality is comming along with a template), disable it as well. In some cases this is managed by server so than You need to ask hosting provider for help.

All You need to do is to disable CSS compression in template settings.

Well... Fine, but where can I disable css compression?
It is already disabled in the template parameters!
I've tried to enable it to be sure (I was thinking the on/off button was reversed) but nothing changed.
I don't know what else to do... Even with a fresh install with gk_league_news_quickstart_J!25.zip the problem is there!

So I really think there is a bug within the template for that css compression selection.

Philippe

Hi

Show me Your site. I'll check if compression is being used at all.

Here it is:
http://ffsweb01.a51.fr/

And a fresh one installed from the quickstart:
http://aap.a51.fr/

And a totally other one on the same server with another template and no css compression (showing there is no pb with th server):
http://od.a51.fr/

Hi

In code I can see files are being loaded separately so no compression activated on site. Than it got to be comming from Your server settings, but send me an access to http://ffsweb01.a51.fr/ so I'll confirm it.

Hi Theitbite,
Done by PM.
Thanks

Hi

I haven't recived an access nither via PM or mail. Can You resend it ?

Resent via email.
Is it ok?

Hi

I got it now. Unfortunately I was mistaken. I've been checking my copy which was not the latest version. Now I can see that this behaviour is directly comming from template. I've already asked programmers how to disable it. Will let You know as soon as the answer.

Hi

It was a bug. Here is what programmer told me:

I've got the problem, prefixfree is included twice - probably one copy was not removed after development process, for fix please open file head.php and remove line 78 :

Code: Select all

$this->API->addJS($this->API->URLtemplate() . '/js/prefixfree.js');

To avoid fatal error please also replace line 34

Code: Select all

$this->addJS($this->API->URLtemplate() . '/js/prefixfree.js');

to

Code: Select all

$this->API->addJS($this->API->URLtemplate() . '/js/prefixfree.js');

Thanks for the fix!

And for those (I don't think I'm alone) not familiar with gavick files location, here is the path for the file mentioned by the development team:
templates/gk_league_news/layouts/blocks/head.php

Hope it helps!
Philippe

Hi

Och, yes sorry. The message from programmer was for so I was supposed to tell You the whole path. Sorry for that one more time.