@RobertIger the families of the hostages are hurting so bad in Israel. Would be great if we can get them into @DisneyParks. How can we make that happen?
@fbinegotiator Saw your masterclass and read your book. Am a big believer in your tactics and practices. Are you currently involved in negotiation consulting or just training? Have a situation where good negotiation would mean the difference for literally hundreds. #BringThemHome
@facan@PeterMindenhall@bing I have the same problem. @bing banned my site for nothing. When I use the inspector I am told that the site can be indexed and appear on Bing. @facan what can I do to resolve this? It's killing me!
@taylorotwell I am probably nowhere in the league of the smart minds at Laravel, but if I can ever contribute, I am always more than willing. Thanks again!
@taylorotwell Ah. OK that was the unclear bit. I'll make that change going forward. Hey, thanks for giving me a little of your time, and thanks for all the hard work you have put into Laravel. It has been a real pleasure to use!
@taylorotwell So then one is not meant to implement the report() method in Handler.php anymore? If you add in a public method of "report" as was the old behavior, it seems to trample the custom exception report() method.
@taylorotwell Here is the repo I made. https://t.co/YBPtVCUvKf
If you uncomment the report() method in the handler, the report() in the custom exception doesn't fire.
@taylorotwell I can recreate it. If the handler has the report method, it hits the handler and not the custom exception. If the report method is not present on the handler, it then hits the custom exception report method. The docs made me think the opposite, that the handler was a fallback.