Hmm... I need to find out myself. I don't know what is the right answer. I'll do some Googling and get back to you if I discover an useful answer. You should email the people at iPage as they probably could answer your iPage question..
Yes...but then i'll not only be sharing the customers across both stores, but also the products. Each store has a different set of products and the two should not have shared access to the products of the other..
I need 2 stores, with different databases, but shared access of the customers..
Perhaps a guru could confirm or deny this thinking:.
If my orig database was created with no table prefix's, and I create a second set of tables in the same database with, say, the prefix no2_, could I modify the files that deal with customer access, such as account.php, create_account.php, account_history.php, etc to query the 'customers' table instead of the 'no2_customers' table?.
I'm thinking that instead of using, just as one example.
Tep_db_query("update "TABLE_CUSTOMERS_INFO" set customers_info ...etc".
I could change all instances ofTABLE_CUSTOMERS to specifically query TABLE `customers` (using the right syntax of course)..
Am I on the right track at ALL?..
I'm not much of a php person, but i'm starting to catch on how programming works..
The solution below would keep the products seperate, yet keep the customers the same..
Your should be able to create a seperate php file that copies all the customers and customer related info into the 2nd database... for 2 stores you'd need to make 2 files, one for each way....
Copyway1st.php would copy #1 customer info to #2 database.
Copyway2nd.php would copy #2 customer info to #1 database.
Then I believe on the create account page, where it calls the confirmation page, right before that you could call the correct php file, to copy the current information over to the 2nd database. So then if they instantly switch to the other store, they would already have an account..
From what I know of php, it should only be probably 10 lines of code or less for all the changes. Hope this helps get you in the right direction..
I'm sure that would work, it sounds feasible, but have you ever heard the phrase.
"Teach an old dog new tricks".
Teejaycom < old dog..
That's 10 lines for me to totally mess up the syntax...
If you have both stores on the same server.
Have them in different directorys Store #1 / Store #2.
And change in database change the customer define in store #2 to store #1.
That way you would not have to make a file..
The multi stores contribution may do that, not sure, if not, you would have to create a second set of tables dealing with products, etc with a different prefix yet try to keep the customer related info at a default prefix both apps could talk with..
Be easier to just copy the customer info from the backup and restore onto the new site...
I think that's kinda what I was suggesting in my second post in this thread....I think..
Yeah...it does, I thought of that....but I got about a way thru the readme...and I was going..."Oh. My. GAWD!!!!".
Have you READ the readme for that sucker????.
I'd thought of that too, and that would work....for existing customers (but still require a double login). However, new customers would not get added from one store to the other until I checked the sites...and unless I did that CONSTANTLY, the customer info would not get shared immediately between stores, so a customer who registers at one store, could go to the next one and find that store has no record for them..
I think I'm going to have to take a very......VERY deep breath, and tackle the multistores mod..
It looks like that is the only way I am going to get what I need. I hope. Unless djgizmo wants to write those copying files for me? heh.
Thanx for the responses guys..
This post has been edited by.
: 14 September 2004, 13:28..
Keep us up to date teejay..
I'm gonna have to do something similar to what you're doing eventually...
I have an exisitng iPage site running for my wife..
We have just obtained a supplier of products that, while they compliment her existing product line, for various resons are not able to be handled in the same manner (basically, different shipping requirements)..
I want to set up another store on a subdomain of the same site. It will not share the products of the main store, but only sell the products of the new supplier..
But I want to be able to allow customers from the main store, to shop at the sub-store without having to create a new account for it. Asking them to log in again (but with the same username) is not a problem..
Is there a way to allow the sub-store to access the main stores customer login information? Carts would not be shared between stores..
Appreciate any help...
Can you not set the database connection to be the same as your wifes store then you are using the same database?.