Quidam Posted June 21, 2003 Posted June 21, 2003 We have a client who wanted to seperate sites to use the same catalog database. In order to make it happen, we pulled out the store-specific text items from the database and made them hardcoded defines in application_top. So the two sites can share a database and just have different defines in application_top. The code that resides on the secure site, though, didn't get updated- partly due to the fact that both sites also share the secure site's code. So STORE_NAME was showing up on the login page. I was told to just move one of the application_top files over- doesn't matter if for the secure site the name is for the other store, just as long as it isn't STORE_NAME. Well, I did that, but STORE_NAME is still showing up. The change works on the nonsecure site, but not on the secure site and I'm at a bit of a loss as to why. Any help on the matter would be greatly appreciated. Here's the modified portion of application_top: // set the application parameters (can be modified through the administration tool) $configuration_query = tep_db_query('select configuration_key as cfgKey, configuration_value as cfgValue from ' . TABLE_CONFIGURATION . ''); while ($configuration = tep_db_fetch_array($configuration_query)) { define($configuration['cfgKey'], $configuration['cfgValue']); } // Hardcoded store constants for stores to share a db define(STORE_NAME, "QuickSilver Records!!"); define(STORE_OWNER, "QuickSilver Records?!"); define(STORE_OWNER_EMAIL_ADDRESS, "[email protected]"); define(EMAIL_FROM, "QuickSilver Records <[email protected]>"); define(SEND_EXTRA_ORDER_EMAILS_TO, "Quicksilver <[email protected]>"); define(STORE_NAME_ADDRESS, "QuickSilver Records 31312 Via Colinas Road, Suite 107 Westlake Village, CA 91362-3905 800-233-2880"); define(STORE_ORIGIN_ZIP, "91362-3905");
Recommended Posts
Archived
This topic is now archived and is closed to further replies.