I'm almost ready to release my PHP-powered feedback form! Sorry for taking so long. I haven't been working on it that much.
So now my plans are to start writing again. Maybe take a break from developer work. Then, when I can work out a useful schedule or something like that, I can start coding Fights and Blood (the name of the game I'm thinking of making), while still writing for an hour. I limit the amount of time I'm on the computer because truthfully computer can be a waste of time when there's so much more to do.
And, do you know what I just thought would be cool? If I made another Save the Cave! Say, something like "catch the bandits" to continue the hardest game that I've ever made. Because in the description, it talks about how bandits have set a time bomb at the end of the cave. So where did the bandits go? If, by any chance, I start a sequel to Save the Cave, we'll find out.
I'm not promising any sequel.
A blog full of code tips for HTML, CSS, and JavaScript. Learn code problem solutions, website creating tips, and more.
Showing posts with label Form. Show all posts
Showing posts with label Form. Show all posts
Sunday, July 31, 2011
Friday, July 15, 2011
Tip of the Week
Do you have a submission email for sign-ups? So you can see the data by email? Do you require the people to send it in an email to you? Skip this!
PHP, a popular programming language, allows you to send emails directly from the script, as you may know. You should create a form with PHP that has the script to send you the email with the submission data. For example, if you want your visitors to sign up for a contest, all you have to do it make the script send an email to your submission email with the details of the data entered.
If you don't know how to do this yet in PHP or if you don't know any PHP, you can study it on many different sources. For simple tutorials, go to www.w3schools.com/php or to the PHP manual.
PHP, a popular programming language, allows you to send emails directly from the script, as you may know. You should create a form with PHP that has the script to send you the email with the submission data. For example, if you want your visitors to sign up for a contest, all you have to do it make the script send an email to your submission email with the details of the data entered.
If you don't know how to do this yet in PHP or if you don't know any PHP, you can study it on many different sources. For simple tutorials, go to www.w3schools.com/php or to the PHP manual.
Thursday, June 2, 2011
Tip of the Day
When to use "get" or "post"?
The "get" and "post" methods of a form control whether the results in a form should be URL encoded or not, as you may most likely know.
Use the "get" method when you want somebody to be able to do an action when it is URL encoded. Scripting can help. For example, if you created a search engine, you'd want to have the result URL encoded. For example:
www.example.com/search?searchword=themadcomputer
If you designed your coding so that "searchword" would be the word entered into the search box, anybody could search from the address bar or at your search box, and the contents of the variable "searchword" would be looked up with the engine. See what I'm saying? If the "searchword" variable read "yosemite", then it would be looking up the word "yosemite" and displaying results on that subject.
But now use the "post" method for sensitive data, like signup pages and email submissions. You don't want people to see the history and find something like "www.example.com/signup/signedup?username=themadcomputer&password=MypassWord12&email=someone@example.com" because then they'd know what the password was and could basically click on that URL and it would repeat the signup (basically, you'd actually want the page to validate results anyways). But see?
A very useful tip.
The "get" and "post" methods of a form control whether the results in a form should be URL encoded or not, as you may most likely know.
Use the "get" method when you want somebody to be able to do an action when it is URL encoded. Scripting can help. For example, if you created a search engine, you'd want to have the result URL encoded. For example:
www.example.com/search?searchword=themadcomputer
If you designed your coding so that "searchword" would be the word entered into the search box, anybody could search from the address bar or at your search box, and the contents of the variable "searchword" would be looked up with the engine. See what I'm saying? If the "searchword" variable read "yosemite", then it would be looking up the word "yosemite" and displaying results on that subject.
But now use the "post" method for sensitive data, like signup pages and email submissions. You don't want people to see the history and find something like "www.example.com/signup/signedup?username=themadcomputer&password=MypassWord12&email=someone@example.com" because then they'd know what the password was and could basically click on that URL and it would repeat the signup (basically, you'd actually want the page to validate results anyways). But see?
A very useful tip.
Subscribe to:
Posts (Atom)