librelist archives

Re: [nesta] Theme fonts and style not picking up

From:

Tommaso Patrizi

Date:

2011-10-27 @ 10:16

And here is another strange thing, it is trying to find an old theme painter
which now is no longer in my themes directory:

174.122.137.112 - - [27/Oct/2011:06:09:45 -0400] "GET
/painter/stylesheets/fonts/Quicksand_Book-webfont.svg HTTP/1.1" 404 1510 "
http://ethandune.org/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8)
AppleWebKit/534.50 (KHTML, like Gecko) Version/5.1 Safari/534.50"

Tommaso

On Thu, Oct 27, 2011 at 11:05 AM, Tommaso Patrizi <tommasop@gmail.com>wrote:

> Looking into the nginx logs I have
>
> 174.122.137.112 - - [27/Oct/2011:05:03:13 -0400] "GET /css/master.css
> HTTP/1.1" 200 5504 "http://ethandune.org/" "Mozilla/5.0 (Macintosh; Intel
> Mac OS X 10_6_8) AppleWebKit/534.50 (KHTML, like Gecko) Version/5.1
> Safari/534.50"
>
> This is strange because in my theme layout I have:
>
> %link{:href => "/stylesheets/site.css", :media => "screen", :rel =>
> "stylesheet", :type => "text/css"}
>
> Tommaso
>
>
> On Tue, Oct 25, 2011 at 9:38 PM, Tommaso Patrizi <tommasop@gmail.com>wrote:
>
>> Here is my definition I think it should be best practice:
>>
>> @font-face {
>>     font-family: 'QuicksandBoldOblique';
>>     src:
>> url('/nesta-matic/stylesheets/fonts/Quicksand_Bold_Oblique-webfont.eot');
>>     src:
>> url('/nesta-matic/stylesheets/fonts/Quicksand_Bold_Oblique-webfont.eot?#iefix')
>> format('embedded-opentype'),
>>
>>  url('/nesta-matic/stylesheets/fonts/Quicksand_Bold_Oblique-webfont.woff')
>> format('woff'),
>>
>>  url('/nesta-matic/stylesheets/fonts/Quicksand_Bold_Oblique-webfont.ttf')
>> format('truetype'),
>>
>>  
url('/nesta-matic/stylesheets/fonts/Quicksand_Bold_Oblique-webfont.svg#QuicksandBoldOblique')
>> format('svg');
>>     font-weight: normal;
>>     font-style: normal;
>>
>> }
>>
>> Tommaso
>>
>> On Tue, Oct 25, 2011 at 4:54 PM, Stefan Goodchild <me@stefangoodchild.com
>> > wrote:
>>
>>> On 25 Oct 2011, at 15:45, Tommaso Patrizi wrote:
>>>
>>> > src: url('/nesta-matic/stylesheets/fonts/Quicksand_Light-webfont.eot');
>>>
>>> I've had problems in the past with embedding fonts and versions of Ruby
>>> due to the difference in dealing with UTF8 in SASS files. 1.8 works fine by
>>> default, 1.9 needs some configuration.
>>>
>>> Are you using the best practice way of embedding all the different
>>> formats? eg.
>>>
>>> @font-face {
>>>    font-family: 'CloisterBlackLight';
>>>    src: url('CloisterBlack-webfont.eot');
>>>    src: url('CloisterBlack-webfont.eot?#iefix')
>>> format('embedded-opentype'),
>>>         url('CloisterBlack-webfont.woff') format('woff'),
>>>         url('CloisterBlack-webfont.ttf') format('truetype'),
>>>         url('CloisterBlack-webfont.svg#CloisterBlackLight')
>>> format('svg');
>>>    font-weight: normal;
>>>    font-style: normal;
>>> }
>>>
>>> Rgds, Stefan
>>>
>>
>>
>>
>> --
>> IN OBSCURO MIRANDA RELUCENT
>>
>
>
>
> --
> IN OBSCURO MIRANDA RELUCENT
>



-- 
IN OBSCURO MIRANDA RELUCENT

On 27 Oct 2011, at 11:16, Tommaso Patrizi wrote:

> And here is another strange thing, it is trying to find an old theme 
painter which now is no longer in my themes directory

Is there any chance you copied an app.rb file from painter, to make your 
new theme? If so, check the Rack::Static config…

Unfortunately not here is my app.rb:

# Use the app.rb file to load Ruby code, modify or extend the models, or
# do whatever else you fancy when the theme is loaded.

module Nesta
  class App
    # Uncomment the Rack::Static line below if your theme has assets
    # (i.e images or JavaScript).
    #
    # Put your assets in themes/nesta-matic/public/nesta-matic.
    #
    use Rack::Static, :urls => ["/nesta-matic"], :root =>
"themes/nesta-matic/public"

    helpers do
      # Add new helpers here.
      def load_snippet(file)
         File.new(file).read if File.exist? file
      end
    end

    # Add new routes here.
    get "/stylesheets/:sheet.css" do
      content_type "text/css", :charset => "utf-8"
      cache scss(params[:sheet].to_sym)
    end
  end
end

On Thu, Oct 27, 2011 at 12:19 PM, Graham Ashton <graham@effectif.com> wrote:

> On 27 Oct 2011, at 11:16, Tommaso Patrizi wrote:
>
> > And here is another strange thing, it is trying to find an old theme
> painter which now is no longer in my themes directory
>
> Is there any chance you copied an app.rb file from painter, to make your
> new theme? If so, check the Rack::Static config…
>



-- 
IN OBSCURO MIRANDA RELUCENT

On 27 Oct 2011, at 11:22, Tommaso Patrizi wrote:

> Unfortunately not

So if you grep your code for "painter" and don't find it, doesn't that 
point the finger at your deployed app?

Could there be a Ruby process hanging around that didn't get restarted?

Graham, thanks so much for your support and for nesta.

I searched my project for painter and there is no longer any reference to
it.

I completely redeployed the app.

I also tried restarting both nginx and passenger on my deployment machine
and also restarted the virtual server.

Still the same result.

Tommaso

On Thu, Oct 27, 2011 at 1:38 PM, Graham Ashton <graham@effectif.com> wrote:

> On 27 Oct 2011, at 11:22, Tommaso Patrizi wrote:
>
> > Unfortunately not
>
> So if you grep your code for "painter" and don't find it, doesn't that
> point the finger at your deployed app?
>
> Could there be a Ruby process hanging around that didn't get restarted?
>



-- 
IN OBSCURO MIRANDA RELUCENT

On 27 Oct 2011, at 12:53, Tommaso Patrizi wrote:

> I completely redeployed the app.
> 
> I also tried restarting both nginx and passenger on my deployment 
machine and also restarted the virtual server.
> 
> Still the same result.

If you've still got "painter" getting requested it must be coming from 
somewhere. It's not in the Nesta gem (I just grepped v0.9.11 to be sure).

Are you sure that the request for the URL containing "painter" came from a
browser that was loading a fresh page on your site, and that CSS 
referencing it hasn't been cached?

What's the public URL of the site? We could check whether other people's 
browsers make a request for anything containing "painter".

Just a further explanation, in the server logs
after searching for painter in the end
it serves the default css/master.css

Tommaso

On Thursday, October 27, 2011, Graham Ashton <graham@effectif.com> wrote:
> On 27 Oct 2011, at 12:53, Tommaso Patrizi wrote:
>
>> I completely redeployed the app.
>>
>> I also tried restarting both nginx and passenger on my deployment machine
and also restarted the virtual server.
>>
>> Still the same result.
>
> If you've still got "painter" getting requested it must be coming from
somewhere. It's not in the Nesta gem (I just grepped v0.9.11 to be sure).
>
> Are you sure that the request for the URL containing "painter" came from a
browser that was loading a fresh page on your site, and that CSS referencing
it hasn't been cached?
>
> What's the public URL of the site? We could check whether other people's
browsers make a request for anything containing "painter".
>

-- 
IN OBSCURO MIRANDA RELUCENT

You should view-source in your browser to see if/where in the page this is
coming from--that might give you a hint.

Also to debug things that aren't loading, in addition to the above, use 
your browser's debug facilities to see what resources are being requested 
and what response the server is returning. (For instance, if some CSS 
isn't showing up, that will tell you whether the issue is that it's not 
being requested, or if it's being requested and not being served.) I know 
that at least Safari and Firefox have good tools for this.

JEff

On Oct 27, 2011, at 10:34 AM, Tommaso Patrizi <tommasop@gmail.com> wrote:

> Just a further explanation, in the server logs
> after searching for painter in the end
> it serves the default css/master.css
> 
> Tommaso
> 
> On Thursday, October 27, 2011, Graham Ashton <graham@effectif.com> wrote:
> > On 27 Oct 2011, at 12:53, Tommaso Patrizi wrote:
> >
> >> I completely redeployed the app.
> >>
> >> I also tried restarting both nginx and passenger on my deployment 
machine and also restarted the virtual server.
> >>
> >> Still the same result.
> >
> > If you've still got "painter" getting requested it must be coming from
somewhere. It's not in the Nesta gem (I just grepped v0.9.11 to be sure).
> >
> > Are you sure that the request for the URL containing "painter" came 
from a browser that was loading a fresh page on your site, and that CSS 
referencing it hasn't been cached?
> >
> > What's the public URL of the site? We could check whether other 
people's browsers make a request for anything containing "painter".
> >
> 
> -- 
> IN OBSCURO MIRANDA RELUCENT

Last email on this subject, I swear and thank you for your patience.

When using a clean firefox with firebug the only thing is the css/master.css
call.
The calls to painter paths were from the nginx access.log

Do you have a working code of a nesta site with an enabled theme so that I
can compare the situations?

Thanks in advance

Tommaso

On Thu, Oct 27, 2011 at 7:44 PM, Jeff Clites <jclites@mac.com> wrote:

> You should view-source in your browser to see if/where in the page this is
> coming from--that might give you a hint.
>
> Also to debug things that aren't loading, in addition to the above, use
> your browser's debug facilities to see what resources are being requested
> and what response the server is returning. (For instance, if some CSS isn't
> showing up, that will tell you whether the issue is that it's not being
> requested, or if it's being requested and not being served.) I know that at
> least Safari and Firefox have good tools for this.
>
> JEff
>
> On Oct 27, 2011, at 10:34 AM, Tommaso Patrizi <tommasop@gmail.com> wrote:
>
> Just a further explanation, in the server logs
> after searching for painter in the end
> it serves the default css/master.css
>
> Tommaso
>
> On Thursday, Octobe r 27, 2011, Graham Ashton < <graham@effectif.com>
> graham@effectif.com> wrote:
> > On 27 Oct 2011, at 12:53, Tommaso Patrizi wrote:
> >
> >> I completely redeployed the app.
> >>
> >> I also tried restarting both nginx and passenger on my deployment
> machine and also restarted the virtual server.
> >>
> >> Still the same result.
> >
> > If you've still got "painter" getting requested it must be coming from
> somewhere. It's not in the Nesta gem (I just grepped v0.9.11 to be sure).
> >
> > Are you sure that the request for the URL containing "painter" came from
> a browser that was loading a fresh page on your site, and that CSS
> referencing it hasn't been cached?
> >
> > What's the public URL of the site? We could check whether other people's
> browsers make a request for anything containing "painter".
> >
>
> --
> IN OBSCURO MIRANDA RELUCENT
>
>


-- 
IN OBSCURO MIRANDA RELUCENT

On 28 Oct 2011, at 09:50, Tommaso Patrizi wrote:

> Do you have a working code of a nesta site with an enabled theme so that
I can compare the situations?

Not one where the source is publicly visible, no.

You can make one yourself like this though:

$ nesta new theme-test
$ cd theme-test
$ nesta demo:content
$ nesta theme:install git://github.com/gma/nesta-theme-slate.git
$ nesta theme:enable slate
$ shotgun config.ru

Cheers,
Graham

Hi Graham,
it's

http://ethandune.org

I'll made a check with other browsers.

T

On Thursday, October 27, 2011, Graham Ashton <graham@effectif.com> wrote:
> On 27 Oct 2011, at 12:53, Tommaso Patrizi wrote:
>
>> I completely redeployed the app.
>>
>> I also tried restarting both nginx and passenger on my deployment machine
and also restarted the virtual server.
>>
>> Still the same result.
>
> If you've still got "painter" getting requested it must be coming from
somewhere. It's not in the Nesta gem (I just grepped v0.9.11 to be sure).
>
> Are you sure that the request for the URL containing "painter" came from a
browser that was loading a fresh page on your site, and that CSS referencing
it hasn't been cached?
>
> What's the public URL of the site? We could check whether other people's
browsers make a request for anything containing "painter".
>

-- 
IN OBSCURO MIRANDA RELUCENT