Confirmed, sprockets-rails 3 broke the compatibility of some things.
I'll try to fix it, or add a dependency from Hobo to the 2.3.3 version ASAP.

Thanks for the workaround!


El 13-01-2016 a las 22:25, Tim Griffin escribió:
> This appears to get around the problem: 
> 
> Downgrading from sprockets-rails 3.x.x to 2.3.3 has resolved the issue
> with routing for front.css and front.js. 
> 
> I put my hobo version back to 2.2.4 and added this to my Gemfile:
> 
> gem 'sprockets-rails', '2.3.3'
> 
> Tim
> 
> On Wednesday, January 13, 2016 at 4:03:01 PM UTC-5, Tim Griffin wrote:
> 
>     I'm not so sure Hobo is at fault here. 
> 
>     I've downgraded my app back to Hobo 2.2.3, run a /bundle update/,
>     and run the server with /bundle exec rails s thin/, and still see
>     grief loading front.css and front.js. 
> 
>     So, it is a recently-updated asset-pipeline component that is failing?
> 
>     T
> 
> 
>     On Wednesday, January 13, 2016 at 3:56:07 PM UTC-5, Tim Griffin wrote:
> 
>         I confirm I'm also seeing the same thing in an application I'm
>         upgrade from Hobo 2.2.3 to Hobo 2.2.4.
> 
>         ActionController::RoutingError (No route matches [GET]
>         "/stylesheets/front.css"):
>           actionpack (4.2.4)
>         lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
> 
>         In addition, I'm seeing references to image assets failing route
>         references as well:
> 
>         ActionController::RoutingError (No route matches [GET]
>         "/images/nu.png")
> 
>         Tim
> 
> 
>         On Wednesday, January 13, 2016 at 5:43:04 AM UTC-5, Ibon
>         Castilla wrote:
> 
>             Hi Johannes,
> 
>             It's really weird, we are here seeing the same thing: both
>             front.css and front.js are not loading properly. We are
>             trying to debug it but no results so far.
> 
>             Best regards, Ibon.
> 
>             El martes, 12 de enero de 2016, 17:36:12 (UTC+1), Johannes
>             Vanderknyff escribió:
> 
>                 Hello,
> 
>                 This is likely a newbie question.
> 
>                 Have been trying to do an install of Hobo... and getting
>                 an error.
> 
>                 Have tried on both the turnkey linux - ruby on rails
>                 appliance, which has ruby 2.1.5p273, rails 4.2.5as well
>                 as on Fedora 23, with ruby 2.2.4p230 and Rails 4.2.5
> 
>                 In both cases, the site comes up, but the stylesheet and
>                 the javascript for "front" is failing to load:
> 
>                  ActionController::RoutingError (No route matches [GET]
>                 "/javascripts/front.js")
> 
>                 and
>                  
>                  ActionController::RoutingError (No route matches [GET]
>                 "/stylesheets/front.css")
> 
>                 I have a feeling something should be added to the
>                 application/routes.rb files, but am not sure what in
>                 order to have rails grab these resources.
> 
>                 NOTE: this is a clean install of
>                  gem install hobo
>                  hobo new thingybob
> 
>                 and accepting the standard defaults...
> 
>                 Thanks,
>                 Johannes
> 
> -- 
> 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 https://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 https://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/d/optout.

Reply via email to