Oscommerce - STS 4.5.2 & Category Template modification

For experienced Oscommerce Coders ONLY - give examples. I have a heavily modified Oscommerce cart and installed STS version 4.5.8 and am running into trouble getting category specific [login to view URL] pages to work becuase my [login to view URL] urls don't contact cPath (and I don't want it to because of duplicate content issues). The problem: For example: I have a product numbered 100 which is placed in category 20 and it should make the [login to view URL] page to use the template [login to view URL] because of the STS template system. The problem: My URLs don't contact cPath information (and I don't want them to as I said for duplicate product issues)so I assume the page can't figure out the cPath to use. If I add the cPath to the url (for example: [login to view URL] the template pulls the [login to view URL] template in and works great but as I said I don't want to change it from the current url which is only [login to view URL] What I think would work to fix this without adding cPath to the URL would be to add a field into the Products table called cPath in the database and then put add the category manual to make sure each product has a master category. (for example in the product table I'd add a field called cPath and then add "20" to the product with product id "100". I can do this part on my own. The thing I need modified is the [login to view URL] or STS file (I think it would be [login to view URL] )or some other file (you'd know better than me) to fuction the same as it doesn currently but to check the database for the cPath instead of looking at to the URL for this info. I've attached some of the files I think would be affected but you know best. note we cannot allow for FTP access because of we don't have a test environment so it is very important that the person we accept's understands how to do this on a generic installation. Thanks ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform All browsers PHP Linux server Oscommerce MS2.2