removing fields in sign up form

[hetster]

what can i safely remove from the sign up form?

is there anything that is database dependant or a primary key etc.

 

basicaly all i want is first name...last name..email addy. i dont need any further info as paypal will be doing all the payments which requires them to fill out a shipping form anyway. no point doing it twice. once on my site then to repeat the steps on paypals page.

with just first name..last name and email i can match the orders from paypal with the ones in my admins page

 

but i'm sure i read somewhere that country was needed by the DB so i need to know which ones i can safely remove. i have found the fields to remove but dont want to till someone tells me if its safe to do so without messing the whole shop up.

 

ty in advance

[kgt]

Any of the fields marked with a red star are required, and there's code that checks to make sure these fields are filled out. In addition to removing the fields, you will need to remove the code that handles this.

 

As far as I know, the only field that should really be required is country, since that is used with formatting. You would want to keep state/province as well if you have tax or shipping that depends on the zone.

[hetster]

no can remove the check from the java field checking module as well.

 

i know how to completely remove the fields and checks. its which the database relies on i need to know. which is the primary/secondary/composite key etc..if i delete 1 of those then DB wont function as it should.

 

and i dont need tax and state etc i'm in UK so basicaly just need a way of matching the order to the paypal form without messing the DB up.

 

and i know its off subject but is there a way of making United Kingdom the base field for country drop down selection if it is indeed needed for DB

 

 

or if anyone is familiar with PWA then how can i remove them from them and leave the rest of the sign up intact

[kgt]

It's not too difficult to look at the database schema to determine which fields are used to comprise keys. Not sure why you see that as being a problem.

 

I think you're a little off by assuming the database is the only thing that will give you a fit. OSCommerce assumes that data like Country exist for a customer, as well as an address for the checkout procedure. That's really where your biggest headache is going to be - getting the code to work with the data the way you want. For example, Country is not needed by the database - it's needed by the code.

[hetster]

i am using pwa as checkout i know from bitter experience that shoppers would rather go for express checkout than sign up to a web site just to purchase a single item. thats why i only want a way of matching the orders to the ones that come from paypal.

 

they have to fill out full shipping address and names etc in paypal so absolutely no need to do it twice.

 

i want the DB to function properly for the catalogue and not the customer but if there is a compositte key that is in the catalogue from the customer tables i think it will throw the whole site and DB off.

 

all i need to know is if i can remove ALL fields except for first name...last name..email address without messing the whole store up