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

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/assetsgit 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.

On Mon, Apr 22, 2013 at 5:06 AM, Javix [email protected] 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.

On 22 Apr 2013, at 12:16, Jordon B. [email protected] wrote:

On Mon, Apr 22, 2013 at 5:06 AM, Javix [email protected] 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?

Regards

On Mon, Apr 22, 2013 at 5:22 AM, Serguei C.
[email protected]wrote:

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

On 22 Apr 2013, at 12:53, Jordon B. [email protected] wrote:

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

Awesome! It works great. Thanks a lot!

Cheers