after assets compiled locally bootstrap drop-down list does not work, no errors seen

[Javix]

As advised at Heroku (https://devcenter.heroku.com/articles/rails-asset-pipeline), I modified the config settings in application.rb file:

config.assets.initialize_on_precompile=false

then compiled assets locally:

RAILS_ENV=production bundle exec rake assets:precompile

then pushed it to the git:

git add public/assets
git commit -m "vendor compiled assets"

The application was deplyed without problems and works fine at Heroku.

The problem is that it does not work properly in development (locally). For example, the bootstrap drop-dwpn list for user settings does not work any more, no errors in the browser console. Other features seem to work as needed. Any idea ?

Thank you.

[Jordon Bedwell]

On Mon, Apr 22, 2013 at 5:06 AM, Javix <s.ca...@gmail.com> wrote:

The application was deplyed without problems and works fine at Heroku.

The problem is that it does not work properly in development (locally). For example, the bootstrap drop-dwpn list for user settings does not work any more, no errors in the browser console. Other features seem to work as needed. Any idea ?

Caching.

[Serguei Cambour]

Thank you Jordon for the reply. I just removed the assets folder created inside 'public', removed all the cookies and cache data from the browser and reworked. Is there another solution to avoid to delete the assets folder after compilation?

Regards

--
You received this message because you are subscribed to a topic in the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rubyonrails-talk/pe_qcMO4zoc/unsubscribe?hl=en-US.
To unsubscribe from this group and all its topics, send an email to rubyonrails-ta...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jordon Bedwell]

On Mon, Apr 22, 2013 at 5:22 AM, Serguei Cambour <s.ca...@gmail.com> wrote:

On 22 Apr 2013, at 12:16, Jordon Bedwell <envy...@gmail.com> wrote:

On Mon, Apr 22, 2013 at 5:06 AM, Javix <s.ca...@gmail.com> wrote:

The application was deplyed without problems and works fine at Heroku.

The problem is that it does not work properly in development (locally). For example, the bootstrap drop-dwpn list for user settings does not work any more, no errors in the browser console. Other features seem to work as needed. Any idea ?

Caching.

Thank you Jordon for the reply. I just removed the assets folder created inside 'public', removed all the cookies and cache data from the browser and reworked. Is there another solution to avoid to delete the assets folder after compilation?

`config.serve_static_assets = false` in your development.rb

[Serguei Cambour]

Awesome! It works great. Thanks a lot!

Cheers