github-migration
/
rack-livereload
1
0
Fork 0
Code Issues 11 Pull Requests 4 Packages Projects Releases Wiki Activity

Livereload Doesn't Reload Better_Errors gem Error Page #51

New Issue
Closed
opened 2013-12-10 22:04:25 +00:00 by demisx · 6 comments
demisx commented 2013-12-10 22:04:25 +00:00 (Migrated from github.com)
Copy Link

Hi,
Livereload works fine except when an error page from better_errors gem is shown. When that happens, I need to manually hit Command+R to reload a page. I've already posted this on guard-livereload gem page, but then realized that reloading is handled via rack-livereload. Not sure where exactly to report this issue.

Thanks.

Hi, Livereload works fine except when an error page from better_errors gem is shown. When that happens, I need to manually hit Command+R to reload a page. I've already posted this on guard-livereload gem page, but then realized that reloading is handled via rack-livereload. Not sure where exactly to report this issue. Thanks.
demisx commented 2013-12-11 16:21:45 +00:00 (Migrated from github.com)
Copy Link

This issue was solved by placing the Rack::LiveReload above the BetterErrors::Middleware one in the middleware stack via changing this line in development.rb from default

config.middleware.use Rack::LiveReload

to

config.middleware.insert_before Rack::Lock, Rack::LiveReload

Let me know if I should update README with this and create a new PR

This issue was solved by placing the Rack::LiveReload above the BetterErrors::Middleware one in the middleware stack via changing this line in development.rb from default ``` config.middleware.use Rack::LiveReload ``` to ``` config.middleware.insert_before Rack::Lock, Rack::LiveReload ``` Let me know if I should update README with this and create a new PR
ni-ka commented 2014-02-23 01:14:11 +00:00 (Migrated from github.com)
Copy Link

Works great, thanks for that

Works great, thanks for that
MichaelSp commented 2014-02-26 15:17:58 +00:00 (Migrated from github.com)
Copy Link

Works here, too.
Took me some time to google that.
So I'd recommend to leave a hint in the README.

Works here, too. Took me some time to google that. So I'd recommend to leave a hint in the README.
gerrywastaken commented 2016-03-16 10:59:16 +00:00 (Migrated from github.com)
Copy Link

@johnbintz Any chance of getting this change into the Readme? Will submit a pull request if it's helpful.

@johnbintz Any chance of getting this change into the Readme? Will submit a pull request if it's helpful.
gerrywastaken commented 2016-03-16 12:34:57 +00:00 (Migrated from github.com)
Copy Link

Thank you @johnbintz :)

Thank you @johnbintz :)
lserman commented 2016-11-22 16:28:20 +00:00 (Migrated from github.com)
Copy Link

Rack::Lock is no longer used by Rails. Has anyone found a new solution?

`Rack::Lock` is no longer used by Rails. Has anyone found a new solution?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
meganemura/add-homepage-url
nathanhoel/master
refactor
turbolinks_fix
fix-deadlocks-maybe
v0.3.16
v0.3.15
v0.3.14
v0.3.13
v0.3.12
v0.3.11
v0.3.10
v0.3.9
v0.3.8
v0.3.6
v0.3.5
v0.3.4
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.1
v0.2.0
v0.1.0
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: github-migration/rack-livereload#51
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?