What is the html code for a sign up box on your website?

Question

What is the html code for a sign up box on your website?

Answer 1

if you want to have someone log in it's a bit more involved than just slapping a couple of tags on your page and going. To do user login you need at least three distinct elements. The first is code to handle user input (your user name and password) see below:



start with a form (more on action and method in a minute)

throw in a text input for user id:



User ID:



Password:



and then a submit button to send the results off to whatever's going to process the input

Next you need something to that distinguishes correct username and password from bogus entries. This can get fairly involved and is beyond the scope of a single reply, so I'll just list a few options:



use PHP to parse the input

use Perl to parse the input

use Javascript to parse the input (not smart)



then you need somewhere to store usernames and passwords, likewise this can get complicated.

-save username and pw information to a file (xml, text, whatever), not the best idea but it does work in a pinch.



-save username and pw information in a database (much better, but you have to have access to a database server like MySQL.



-hardcode user names and passwords into your web pages (really really stupid, anyone who's clever enough to view source has immediate access to your entire list of usernames and passwords, and note using stupid javascript tricks to obfuscate this stuff does NOT work, so don't bother trying)



Good luck and I suggest w3cschools online tutorials on web coding if you need more information about html/xhtml. Good luck!

Answer 2

It uses the

tag, as in..

But you have to have a program on the webserver to recieve the user's info and keep track of her.

Answer 3

for the box itself its just



To actually do anything with it you will need a back end system like PHP or ASP. If you are using a log in system you will also need a database on the back end such as MySQL to hold the log in information.

Answer 4

Errrrr.... it's more than simple HTML code. You'll need some other languages as well. I had to create an entire login/logout session on a mock e-commerce site I built last quarter. I used php. It would be nice if it were easier.



PHP and MySQL are very useful. If you're going to start using these, I recommend learning a bit from the Visual Quickstart Guides (cheap books that last long, look nice, and are VERY well organized). Also, download and implement phpmyadmin.

Answer 5

you need to learn php and mysql

Answer 6

There isn't one.



H(yper)T(ext)M(arkup)L(anguage) is designed to provide a way for a web site to control (more or less, for the browser need not follow every format instruction) the display of text and images on the browser window.



H(yper)T(ext)T(ransfer)P(rotocol), on the other hand, does have provisions for tansmitting data in both directions. The 404 error you see every so often is an HTTP error announcement. but all it does is transmit data back in specific formats.



Interactivity on Web pages is done outside both of these. The usual methods are



*JavaScript (a sort of scripting laguage for browser control that has little to do with Java; the official name nowadays is ECMAScript. Anyway; most browsers support it inherently), or



*Java (a full language, intended to have limited capabilities on your computer, by design; it's called the 'sandbox' . It's a write-once, run-anywhere language which requires a Java Virtual Machine to be installed to actualy run the program on the local machine. JVMs for various operating systems and CPUs and as browser plug-ins are available from Sun Microsystems (who control the Java design) at no charge, and under different names from others, though no longer from Microsoft who lost the lawsuit with Sun), or



*for Windows systems only, ActiveX (a specification for programlets which can be written in most any langauge. They can do anything at all on your computer when they run and are a secuirty risk. Which is why Microsoft provides a publisher certification as a way of preventing tampering with them before downloading).



The Web site can download a little program with a page, wirtten any of these, which has been written to put up a box, ask for some information, and send the information back to the Web site.



========

at the other end



From the Web site's perspective, downloading the program is only one of the things one must get right. The data, when it comes back from the remote browser, must be processed, to exclude garbage data, to block malicious code and malformed data, to vet what seems to be acceptable, and if it passes all these tests, to store the data someplace.



* Java can be used on the server side (some such programs are called 'beans' -- it's harmless, probably, but was likely funny the first time), or



* in most any programming language using the C(ommon)G(ateway)I(nterface) scheme, or



* using any of several server-side scripting languages such as P(ersonal)H(ome)P(ages), or A(ctive)S(erver)P(ages) (for Windows only), etc. Your Web server software will include, or can accomodate, one or more of these. Apache works well with PHP, Microsoft's Internet Information Server includes ASP.



Most of the time, the data that's accepted will have to be stored as well, and that probably means a database of some kind. The S(tructured)O(uery)n(anguage) interface to databases is widely used.



* On Windows systems this can be SQLServer, Microsoft's version of Sybase's SQL database, or



*MySQL from Sweden, or



*Oracle, or



*Postgres, or...



Oracle and SQLServer are commercial software, and you can buy a support license for some versions of MySQL as well. Another option is Cache, a rather different database system, which has its own programming language, and is available, in some versions and for some purposes, at no cost. SleepyCatSoftware offers another, the Berkeley database, which is also free in some versions for some uses. There are numerous choices, some of them no cost. they vary in quality, support (ie, bug fixes by the developers), documentation, and so on.



===============

complications



The interactions among these aspects of running a Web site are not always simple nor obvious. There are issues of



*data coherence (this is often called 'transactional integrity' and involves the hardware, the language used, the Web server software, and whatever database you're using),

* speed of processing of asynchronously delivered data (more of a problem with high traffic sites than low traffic sites),



*coping with a failure,



*failover to a backup system,



*data synchronization between the backup systems,



*power failure protection (UPSes, power conditioning, standby generators, ...),



* operating system interrupt handling schemes, and so on.



You may not need to worry about some of these issues, but...



Good luck.