Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Admin vs catalog/admin


baalwww

Recommended Posts

Posted

I have a general question about design. Why is so much of root/catalog/admin duplicated in root/admin? It takes forever to add contributions. Is this intentional, or did I so something wrong during installation? I've had contributions that have instructed me to change catalog/admin, only to find that the changes do nothing unless I make the same changes in admin.

Posted

The catalog is a directory that many shops are installed in. It may not exist on your setup. It refers to the directory that holds your shop. So if you have a catalog directory and it says to change a file in catalog/admin, that's what you should do. If you don't have a catalog directory, then you treat the instructions as saying to make changes to admin.

 

Jack

Support Links:

For Hire: Contact me for anything you need help with for your shop: upgrading, hosting, repairs, code written, etc.

All of My Addons

Get the latest versions of my addons

Recommended SEO Addons

Posted
The catalog is a directory that many shops are installed in. It may not exist on your setup. It refers to the directory that holds your shop. So if you have a catalog directory and it says to change a file in catalog/admin, that's what you should do. If you don't have a catalog directory, then you treat the instructions as saying to make changes to admin.

 

Jack

I do have /catalog, and a shop in it, but I noticed that when following instructions to add a contribution and changing files in /catalog/admin, the changes dont appear in my store unless I also make them in the same files in admin. I'm 'entering' the store after making the changes by clicking the Online Catalog link at top of screen. Is this somehow invoking /admin and not /catalog/admin maybe?

Posted

The way osCommerce comes in the standard distribution, the admin folder is a subfolder of catalog, so you would have /catalog for your store and /catalog/admin for admin. You are free to rearrange this and it seems you have done so, but incompletely. If you have done away with the /catalog folder, so your store is at the top level of your site, your admin area would be /admin. You can (and I say should) rename the admin folder to something else to make it obvious when idiots try to break into your admin panel (and trust me, they do try...)

 

It sounds to me as if you have duplicated your files unnecessarily. Pick one or the other and delete the one you don't want.

Posted

Yeah, I guess i ended up with duplication, but it surely wasnt intentional :-) OK, so is it really just a matter of deleting one...instinct tells me there is a setting somewhere that tells oscommerce to look at root/admin, especially given that it seems to ignore catalog/admin. I'd like to kill admin, but will its simply not being there anymore cause oscommerce to look in the right place?

Posted

I'm not sure what you mean about killing admin. If you mean deleting it, you can't do that. You have to have an admin section of your shop so you can set all of the setings, add products and the like.

 

Jack

Support Links:

For Hire: Contact me for anything you need help with for your shop: upgrading, hosting, repairs, code written, etc.

All of My Addons

Get the latest versions of my addons

Recommended SEO Addons

Posted

Sure, but I have TWO. Right now, /root/admin has the attention of most or all of oscommerce, while /root/catalog/admin does not. I'd like to have /root/catalog/admin be it, and then get rid of the other.

Posted

The path locations for the admin files are recorded in the admin/includes/configure.php file.

 

As for which one actually gets entered into when you login to your admin, that is determined by the URL you enter to access it.

 

If the URL looks something like:

 

www.yoursite.com/admin/index.php or www.yoursite.com/admin/

 

then you are using the one in /root/admin.

 

If the URL looks something like:

 

www.yoursite.com/catalog/admin/index.php or www.yoursite.com/catalog/admin/

 

then you are using the files in /root/catalog/admin/

 

Before deleting one or the other, make a backup copy of the one you are going to delete, just in case it has any modifications that the other one didn't that you don't remember until later.

 

hth

Rule #1: Without exception, backup your database and files before making any changes to your files or database.

Rule #2: Make sure there are no exceptions to Rule #1.

Posted

OK, i changed the entry for fs_admin in that from /admin to /catalog/admin, but when I go to /mydomain/catalog/admin, all the links on the admin panel point to /admin, not /catalog/admin. It seems to me, that for /catalog to be able to find /admin/includes/configure.php, something must tell it where to look for admin... i.e. it cant look in a file in admin for the location of admin. I've been looking, but can't find which file contains the definition of where admin is to be found.

Posted
OK, i changed the entry for fs_admin in that from /admin to /catalog/admin, but when I go to /mydomain/catalog/admin, all the links on the admin panel point to /admin, not /catalog/admin. It seems to me, that for /catalog to be able to find /admin/includes/configure.php, something must tell it where to look for admin... i.e. it cant look in a file in admin for the location of admin. I've been looking, but can't find which file contains the definition of where admin is to be found.

 

in /catalog/admin/includes/configure.php update the entries for both

 

define('DIR_FS_ADMIN'

 

define('DIR_WS_ADMIN'

 

to reflect the new file locations. Then to access the admin in the new location be sure your browser is pointed to the new location of admin folder.

 

None of the catalog files need (nor should be allowed) to access the admin files.

Rule #1: Without exception, backup your database and files before making any changes to your files or database.

Rule #2: Make sure there are no exceptions to Rule #1.

Posted

1. I changed the name of the /catalog/admin directory to /catalog/stuff

2. I changed /catalog/stuff/includes/configure.php lines to read

define('DIR_WS_ADMIN', '/catalog/stuff/');

define('DIR_FS_ADMIN', DIR_FS_DOCUMENT_ROOT, DIR_WS_ADMIN);

 

When i point browser at whatever.com/catalog/stuff I get the panel, but when I hover mouse over Configuration or Administration and look at link on bottom of screen, I see whatever.com/admin, not whatever.com/catalog/stuff

Posted
1. I changed the name of the /catalog/admin directory to /catalog/stuff

2. I changed /catalog/stuff/includes/configure.php lines to read

define('DIR_WS_ADMIN', '/catalog/stuff/');

define('DIR_FS_ADMIN', DIR_FS_DOCUMENT_ROOT, DIR_WS_ADMIN);

 

When i point browser at whatever.com/catalog/stuff I get the panel, but when I hover mouse over Configuration or Administration and look at link on bottom of screen, I see whatever.com/admin, not whatever.com/catalog/stuff

 

I use absolute file paths so I am not 100% sure but the syntax in your second line doesn't look right. Try replacing

 

define('DIR_FS_ADMIN', DIR_FS_DOCUMENT_ROOT, DIR_WS_ADMIN);

 

with

 

define('DIR_FS_ADMIN', DIR_FS_DOCUMENT_ROOT . DIR_WS_ADMIN);

 

Note the period and spaces instead of the comma.

 

 

Beyond that, I don't know.

Rule #1: Without exception, backup your database and files before making any changes to your files or database.

Rule #2: Make sure there are no exceptions to Rule #1.

Posted

Well, it turns out that in additoin to admin/includes/configure.php, to have all the links on the panel reflect the new admin location, one must also change ./includes/local/configure.php

Posted
Well, it turns out that in additoin to admin/includes/configure.php, to have all the links on the panel reflect the new admin location, one must also change ./includes/local/configure.php
Ahh! That secondary configure.php file is not used in a stock install. It is primarily used during development to test out settings without corrupting the primary file. As long as everything is working now, you are probably best to leave it alone, but theoretically you could merge any setting in the secondary file into the primary and then delete the secondary file. (make a backup copy first if you do that)

Rule #1: Without exception, backup your database and files before making any changes to your files or database.

Rule #2: Make sure there are no exceptions to Rule #1.

Posted

Oh! Ya never know when you're hoster is kind enough to provide a "click here" to install...makes life simple...usually hehe. Thanks Mike et al. I have 350 different items coming in crates next week, and I might be ready!

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...