OK, I went ahead and generated a nice ajax-loader.gif and put it in 
app/assets/images, clobbed and re-precompiled assets, and no more errors.

So, thanks for all your help, but at least for now, I have the problem 
addressed.

Paul

On Thursday, May 14, 2015 at 10:26:16 PM UTC+7, [email protected] wrote:
>
> Wow, thanks for your thorough and painstaking reply. I do appreciate it.
>
> Notes below...
>
> On Thursday, May 14, 2015 at 6:22:32 PM UTC+7, Ignacio Huerta wrote:
>>
>> Hi Paul, 
>>
>> I have checked this, and I haven't been able to reproduce it with the 
>> same hobo/hobo_bootstrap versions in production mode. 
>>
>> If I look with Firebug, I'm seeing a compiled CSS file like this beings 
>> loaded: /assets/front-0d5a7dfd61d432ac4d1fa6a0a7b7ce0b.css 
>>
>
> Yes, my front page has a similar link. 
>
>>
>> Searching into this file for "ajax-loader", I find this piece of CSS: 
>> background:url(/assets/ajax-loader-5ba2a014bf17ca29b030deebd5a45451.gif) 
>>
>
> In my front-<digest>.css, the link is to:
>
>      
> background:url(/assets/ajax-loader-5ba2a014bf17ca29b030deebd5a45451.gif
>
> ... but there is no public/assets/ajax-* to be found, with or without the 
> digest. So my error message in the log is:
>
> I, [2015-05-14T21:56:13.309471 #37560]  INFO -- : Started GET 
> "/assets/ajax-loader-5ba2a014bf17ca29b030deebd5a45451.gif" for 127.0.0.1 at 
> 2015-05-14 21:56:13 +0700
> F, [2015-05-14T21:56:13.311433 #37560] FATAL -- : 
> ActionController::RoutingError (No route matches [GET] 
> "/assets/ajax-loader-5ba2a014bf17ca29b030deebd5a45451.gif"):
>
> So it seems that in your case the "asset fingerprinting" (adding the 
>> number to identify the asset) is not working. Can you check a few things 
>> to see if we find out where things are not working? 
>>
>> - Settings in config/environments/production.rb: 
>>   config.assets.compile = false 
>>   config.assets.digest = true 
>>
>
> Yep, confirmed those. 
>  
>
>> - You are precompiling your assets with "RAILS_ENV=production rake 
>> assets:precompile" 
>>
>
> Correct. 
>  
>
>> - Once precompiled, the compiled CSS file is in 
>> public/assets/front-0d5a7dfd61d432ac4d1fa6a0a7b7ce0b.css 
>>
>
> Yes, with a different digest of course.
>
> - When visiting the home page, the HTML contains a line like: 
>>   <link class="app-stylesheet" 
>> href="/assets/front-0d5a7dfd61d432ac4d1fa6a0a7b7ce0b.css" media="screen" 
>> rel="stylesheet"> 
>>
>  
> Yes mine is: 
>
>      <link class="app-stylesheet" 
> href="/assets/front-9bba951313df09b74b77547b97454d00.css" media="screen" 
> rel="stylesheet">
>
> ... and that file exists.
>
> The only other curious thing, which may only indicate the way Chrome 
> developer mode displays stuff, is that Chrome says that front-*.js 
> requested ajax-loader, not front-*.css. That may be nothing...
>
> Anyway, let me know if you have any thoughts. I can certainly find 
> ajax-loader files, and I guess if  I jam one into images, it will be 
> compiled. But I would llike to get to the root of the problem.
>
> Thanks again very much.
>
>  
>
>> Warm regards, 
>> Ignacio 
>>
>> El 13-05-2015 a las 09:22, [email protected] escribió: 
>> > Thanks for the quick response. It would be heartening to know that a 
>> > problem was not caused by my code! 
>> > 
>> > Here's a  gist of my Gemfile.lock 
>> > <https://gist.github.com/pauldavis/2fdbfc058ba644d667b2> 
>> > 
>> > It shows these versions: 
>> > 
>> >   hobo (= 2.1.1) 
>> >   hobo_bootstrap (= 2.1.1) 
>> > 
>> > When I look at what I think is the relevant source, I see that it uses 
>> > url(), rather than a hardcoded path, or the apparently correct 
>> asset_path. 
>> > 
>> > What's the best way to override that? 
>> > 
>> > Thanks! 
>> > 
>> > On Wednesday, May 13, 2015 at 1:24:50 PM UTC+7, Ignacio Huerta wrote: 
>> > 
>> >     Thanks for the report Paul! 
>> > 
>> >     It looks like somewhere we are using a bad path for these 2 assets. 
>> >     Probably, instead of using the Rails helper "asset_path" we are 
>> using a 
>> >     hardcoded "/assets/ajax-loader.gif". It works in development but 
>> not in 
>> >     production. 
>> > 
>> >     Can you tell me the version of the Hobo and hobo_bootstrap gems you 
>> are 
>> >     using? 
>> > 
>> >     Warm regards, 
>> >     Ignacio 
>> > 
>> >     El 12-05-2015 a las 16:09, [email protected] <javascript:> 
>> escribió: 
>> >     > I am seeing errors in production mode that I do not have in 
>> >     development mode. I don't think this is a Hobo problem, but I think 
>> >     Ignacio is quite familiar with the hobo_bootstrap code, so he or 
>> >     another helpful Hobo may have a quick suggestion. 
>> >     > 
>> >     > 
>> >     > *The error for ajax-loader.gif:* 
>> >     > 
>> >     > 
>> >     > I, [2015-05-12T20:52:55.065377 #35483]  INFO -- : Started GET 
>> >     "/assets/ajax-loader.gif" for 127.0.0.1 at 2015-05-12 20:52:55 
>> +0700 
>> >     > F, [2015-05-12T20:52:55.067207 #35483] FATAL -- : 
>> >     > ActionController::RoutingError (No route matches [GET] 
>> >     "/assets/ajax-loader.gif") 
>> >     > 
>> >     > 
>> >     > *And for glyphicons-halflings.png:* 
>> >     > 
>> >     > 
>> >     > I, [2015-05-12T20:52:55.068712 #35483]  INFO -- : Started GET 
>> >     "/assets/glyphicons-halflings.png" for 127.0.0.1 at 2015-05-12 
>> >     20:52:55 +0700 
>> >     > F, [2015-05-12T20:52:55.070491 #35483] FATAL -- : 
>> >     > ActionController::RoutingError (No route matches [GET] 
>> >     "/assets/glyphicons-halflings.png") 
>> >     > 
>> >     > 
>> >     > I don't know that I actually use these - everything operates fine 
>> >     - but the errors are clogging up my log files and making it hard to 
>> >     debug more serious problems. 
>> >     > 
>> >     > 
>> >     > A fuller version of the log files, in production mode, including 
>> the 
>> >     > problem: 
>> >     > 
>> >     >      http://pastie.org/10184475 
>> >     > 
>> >     > I jam those files into public/assets but they would obvs. be 
>> >     overwritten 
>> >     > on teh next assets:clobber, so that's not a great solution. 
>> >     > 
>> >     >  Thanks for any insight. 
>> >     > 
>> >     > Paul 
>> >     > 
>> >     > -- 
>> >     > You received this message because you are subscribed to the 
>> Google 
>> >     > Groups "Hobo Users" group. 
>> >     > To unsubscribe from this group and stop receiving emails from it, 
>> >     send 
>> >     > an email to [email protected] <javascript:> 
>> >     > <mailto:[email protected] <javascript:>>. 
>> >     > To post to this group, send email to [email protected] 
>> >     <javascript:> 
>> >     > <mailto:[email protected] <javascript:>>. 
>> >     > Visit this group at http://groups.google.com/group/hobousers 
>> >     <http://groups.google.com/group/hobousers>. 
>> >     > For more options, visit https://groups.google.com/d/optout 
>> >     <https://groups.google.com/d/optout>. 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> > Groups "Hobo Users" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> > an email to [email protected] 
>> > <mailto:[email protected]>. 
>> > To post to this group, send email to [email protected] 
>> > <mailto:[email protected]>. 
>> > Visit this group at http://groups.google.com/group/hobousers. 
>> > For more options, visit https://groups.google.com/d/optout. 
>>
>

-- 
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/d/optout.

Reply via email to