h2oguyofnh

This may help: http://www.oscommerce.com/forums/index.php?showtopic=95929&hl=

I'm quite sure it's not the right path. The images directory is close to the root of the store. I think product_info.php is also. Now on some stores, not including my live one, I see a question mark after the product_info.php in the url but on my stores I see a forward slash. Is this any help? My live store is wellwaterproducts.com which is a near-stock install. This seems to work.

I'm still struggling with product pages. see http://www.chriskofer.com/wwp2/ and click a product. All images go away. Not some, but all images. Any input valued! STS_VERSION=[2.01] OSC_VERSION=[osCommerce 2.2-MS2]

Though that would seem to be an answer, I think that there is more to it. I am working on this and only my products_info.php seems to generate corrupted image links.

I have been working with this contrib on my practice store and reading the official support thread. It seems to be a brilliant contribution to the community but I am a finding out that it seems to be happiest with a clean installation of OSC. Anybody maintaining a list of known conflicts? If so post the answer here. Otherwise share what you know. Maybe this should be in official support thread but that's over 100 pages long so far and getting hard to browse. Personally, I have an issue now (12/7/2005) at my practice store ( http://www.chriskofer.com/wwp2 ) where product_info.php does not show images though any other pages seem to work. example: http://www.chriskofer.com/wwp2/product_inf...products_id/147 has image issues where http://chriskofer.com/wwp2/index.php does not . I thought that perhaps a contrib that I tried which altered the title of the page was the culprit but I installed the original catalog/product_info.php page and that has not done it Any input on how to more effectively render the products page would be appreciated. ck

You should be able to bring in html formatted material. ck

You may have changed the product model numbers. That seems to be the field by which ep recognizes products. Personally, I would wish for the option to keep the product, even with a changed model number, paired with it's id number that osc uses for it's purposes.

Would it be reasonable to state that sts has difficulty with some of the other contrib's? At my test site chriskofer.com/wwp2 it seems to be rendering most pages okay-until you get to products page. I think I have a contrib that changes the title of the page to the product name. Could this be a source of problems? ck

Things are getting closer at my practice store: http://www.chriskofer.com/wwp2/ The width formatting I used in Golive on the left column seems messed up: it gets wider than the 135 pixels that I thought I specified. Also, when you choose a product, the images go to pieces. (eg http://www.chriskofer.com/wwp2/product_inf...products_id/147 ) . While we're at it, perhaps I can get some idea why the table on that page looks so poorly formatted. This may be fundamental to css vs html but I thought it would look better (see the source code). I also seem to have lost my formatting for this contrib (Page Editor): http://www.oscommerce.com/community/contributions,2841 It used to show extra static pages in the information box. Do I need to hack the info box for sts to make this work? Thanks so much in advance. ck

I went back to the stock, or near-stock, layout without sts. I think that I may have caused problems because I was using a modified right column and wasn't applying sts correctly. I can see the value of this product but need to learn more. ck

It seems easy to install and modify. I am trying to figure out why I got these results. The concept is great and others seem to be able to use it successfully.

Funky output: see http://chriskofer.com/wwp2/ just installed sts 2.01, any idea of what went wrong? Using default template. I tried writing my own with Golive and it got even worse. ck

I had the same arrangement. I just created a /catalog/temp directory at root level with permissions set to 777. This seemed to get things moving. Hope this helps.

Though EP is a blessing, there is something to be said for managing your data locally. In other words, don't dump excess info into your EP export file. Find a way to "tag" existing products prior the export, though they can be kept in your local db. Once again, I'd like to work directly with the item#'s that osc uses.

I'd like the variable that designates the product to be the osc product number. Or so I think.... This allows us to change product descriptions without messing up links.