Explore >> Select a destination
|
You are here 
|
tenderlovemaking.com | ||
| | | | |
kevinjmurphy.com
|
|
| | | | | Why is our Rails app returning different HTTP status codes in different versions of Rails? Learn some tips and tricks for navigating a large ruby code base in this post. | |
| | | | |
tekin.co.uk
|
|
| | | | | A short post on a technique you can use to see what is using your Rails app's ActiveRecord connections. | |
| | | | |
willj.net
|
|
| | | | | Using Ruby on Rails logger block syntax can save you object allocations in the Ruby VM, and CPU time, I show you how to use it and the difference using it can make | |
| | | | |
blog.carlana.net
|
|
| | | The other day, I was reading a website about some historical documents, when I saw that it had an error message on top: Screenshot from the site Some quick searching online for the error message revealed that it was caused by a mismatch between the site's versions of PHP and WordPress. Older versions of WordPress had a bug in the switch statement of a certain localization component, and later versions of PHP dump a warning about this bug out to the end user HTML. When I came back to the site a few days later, it had been fixed. The ultimate reason for my seeing for the error message as a random reader is that PHP has too many ways to deal with errors: Builtin PHP functions, and therefore any PHP project, have a whole range of error handling mechanisms - erro... | ||
