/explore
|
You are here 
|
linksort.com | ||
| | | | |
markphelps.me
Mark Phelps' blog |
|
| | | | | ||
| | | | |
alnvdl.github.io
A bit of history, a bit of atonement, a bit of shameless self-promotion. |
|
| | | | | ||
| | | | |
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... |
|
| | | | | ||
| | | | |
lanie.dev
So you want to parse a form. You have your handler, and you're getting data passed in through the request. 1 2 3 4 5 package example func Login(w http.ResponseWriter, r *http.Request) { // hi (: } The next step is to parse the form on the request. 1 2 3 4 5 6 func Login(w http.ResponseWriter, r *http.Request) { var err error if err := r. |
|
| | | |||
