newbie

[nsf43]

Another "Newbie" issue...

Everything was working well until I was ready to attach to my new domain.  It is an "add-on" domain with Godaddy. It appears that osCommerce needs to be in a folder called "catalog", and my domain needs to point to a folder named sparkystreasure.com.  I set up a "sparksytreasure.com" folder and copied "catalog" into the domain folder.  Then I set the pointer to sparkystreasure.com/catalog.  I need to re-install oscommerce, I would presume, but neither Google nor Safari will access the new domain; rather it reverts to my primary domain. What am I doing wrong??

Also, I would love to see someone's store to see what the final look might be - not to copy anything!!

Thanks,

Nancy 

[♥JcMagpie]

The code can be in any folder or root it's up to you. Both sites look to be working fine, but you have one redirecting to another.

If you wish to see live sites then go to

https://sites.oscommerce.com/

and you can see a range of live site.

[Jack_mcs]

1 hour ago, nsf43 said:

it reverts to my primary domain. What am I doing wrong??

The shop is controlled by the configure.php file located in the includes directory (there is also one in admin). When you copy the files to a new location, you have to change the entries in the configure file to point to that location. You don't need to re-install the shop, unless you just want to or if you don't feel comfortable editing that file. If you can edit the file but run into problems, post it here (minus the lines at the bottom that have the login details) and someone will take a look.

[MrPhil]

If you're just starting out, you're best off leaving the store in its own catalog/ or shop/ directory, and not in the site root. That way, you can easily add other subsystems (e.g., a blog, a photo gallery) in their own directories, with some sort of "landing page" in the root to direct visitors to the appropriate area. Any subsystem can then be changed or removed without the risk of breaking something else in the site (as happens when a store or other subsystem is mixed in with root files), and you won't have the complications of having your blog's URLs pass through the store's .htaccess or vice-versa. Until you bring up other subsystems and a landing page, you can tell the server to silently (200 status code) rewrite an incoming URL to your root over to the catalog/ or shop/, in /.htaccess. That way, visitors don't have to remember to type in "catalog/", and when you do add other subsystems, bookmarks and search engine entries won't have to change.

[nsf43]

Thanks to all answers!  I am comfortable with the store being in the root of the site.  I have other domains for other "opportunities".  I looked for a configure  file, but failed, so I shall go fix them now and clear up my muddle.  I am a 55 year veteran of software engineering and I do, occasionally, get tangled with "new" versus "old" methods. Plus, in reading your footer, Phil, I realize that I didn't do the patches.  

[nsf43]

I have moved everything to the root and changed the configure.php files.  The database is working. The store seems to be working, but not the "admin".  It gets lost in "action_recorder.php" while trying to present the admin login screen.  Here is my admin changed config....

 define('HTTP_SERVER', ''); // eg, http://localhost or - https://localhost should not be NULL for productive servers
  define('HTTPS_SERVER', '');
  define('ENABLE_SSL', 'true');
  define('HTTP_COOKIE_DOMAIN', '');
  define('HTTPS_COOKIE_DOMAIN', '');
  define('HTTP_COOKIE_PATH', '');
  define('HTTPS_COOKIE_PATH', '');
  define('HTTP_CATALOG_SERVER', '');
  define('HTTPS_CATALOG_SERVER', '');
  define('ENABLE_SSL_CATALOG', 'true'); // secure webserver for catalog module
  define('DIR_FS_DOCUMENT_ROOT', $DOCUMENT_ROOT); // where your pages are located on the server. if $DOCUMENT_ROOT doesnt suit you, replace with your local path. (eg, /usr/local/apache/htdocs)
  define('DIR_WS_ADMIN', '/admin/');
  define('DIR_WS_HTTPS_ADMIN', '/admin/');
  define('DIR_FS_ADMIN', DIR_FS_DOCUMENT_ROOT . DIR_WS_ADMIN);
  define('DIR_WS_CATALOG', '');
  define('DIR_WS_HTTPS_CATALOG', '');
  define('DIR_FS_CATALOG', DIR_FS_DOCUMENT_ROOT . DIR_WS_CATALOG);
  define('DIR_WS_CATALOG_IMAGES', DIR_WS_CATALOG . 'images/');
  define('DIR_WS_CATALOG_LANGUAGES', DIR_WS_CATALOG . 'includes/languages/');
  define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/');
  define('DIR_FS_CATALOG_IMAGES', DIR_FS_CATALOG . 'images/');
  define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/');
  define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/');
  define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');
  define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');

Thanks!

[Jack_mcs]

You don't have anything set in it. In the least the first two settings are needed, though there are others.

[241]

define('HTTP_SERVER', 'http://yoursparkyname'); // eg, http://localhost or - https://localhost should not be NULL for productive servers
  define('HTTPS_SERVER', 'https://yoursparkyname');
  define('ENABLE_SSL', 'true');
  define('HTTP_COOKIE_DOMAIN', 'yoursparkyname');
  define('HTTPS_COOKIE_DOMAIN', 'yoursparkyname');
  define('HTTP_COOKIE_PATH', '/admin');
  define('HTTPS_COOKIE_PATH', '/admin');
  define('HTTP_CATALOG_SERVER', 'http://yoursparkyname');
  define('HTTPS_CATALOG_SERVER', 'https://yoursparkyname');
  define('ENABLE_SSL_CATALOG', 'true'); // secure webserver for catalog module
  define('DIR_FS_DOCUMENT_ROOT', $DOCUMENT_ROOT); // where your pages are located on the server. if $DOCUMENT_ROOT doesnt suit you, replace with your local path. (eg, /usr/local/apache/htdocs)
don't know this one you will need to get this yourself

I would also change the name of the admin directory and references to something only you know @nsf43

[ArtcoInc]

@241

If line 3 'ENABLE_SSL'  is true, than line 1 needs to change 'http:// ... '    to    'https:// ... '

(add the S to https)

M

[241]

@ArtcoInc I know maybe @nsf43 that info

[♥raiwa]

7 minutes ago, ArtcoInc said:

@241

If line 3 'ENABLE_SSL'  is true, than line 1 needs to change 'http:// ... '    to    'https:// ... '

(add the S to https)

M

Only if all shop pages shall be https. But you are right in the sense that this is recommended nowadays.