buttons not showing

[jlyman]

Using 2.2RC2

 

Buttons not showing, apparently not being accessed under catalog/includes/languages/english/images/buttons. This is not a new install but it is a re-install from back-ups that had worked just fine in the past.

 

I did check to be sure that button image files are in place (and re-copied those from back-up again). I have no trouble with other images showing up on the pages, so the problem seems to be with the particular buttons directory (tried changing language configuration, also...no help). I tried to rename and delete the .htaccess files under /catalog, and /catalog/includes ...but that had no effect. I believe that I have all of the files permissions set corretly (files no higher than 644, files no higher than 755...configure.php files at 444).

 

Because the osCommerce files and directories should be OK from back-ups that worked before, etc., this seems to be some sort of permissions or .htaccess security issue with my server, but the ISP folks won't help with osCommerce.

[KDM]

Using 2.2RC2

 

Buttons not showing, apparently not being accessed under catalog/includes/languages/english/images/buttons. This is not a new install but it is a re-install from back-ups that had worked just fine in the past.

 

I did check to be sure that button image files are in place (and re-copied those from back-up again). I have no trouble with other images showing up on the pages, so the problem seems to be with the particular buttons directory (tried changing language configuration, also...no help). I tried to rename and delete the .htaccess files under /catalog, and /catalog/includes ...but that had no effect. I believe that I have all of the files permissions set corretly (files no higher than 644, files no higher than 755...configure.php files at 444).

 

Because the osCommerce files and directories should be OK from back-ups that worked before, etc., this seems to be some sort of permissions or .htaccess security issue with my server, but the ISP folks won't help with osCommerce.

 

Have you checked your log file. If anything is not being found, then there should be some kind of error message there.

[jlyman]

Have you checked your log file. If anything is not being found, then there should be some kind of error message there.

 

which log file, and where is it ? ..not sure that I was logging in osC. Here's image of osC config setting for "Logging" :

 

 

My server has a logging file, but when I searched that very long file text (unformatted...not sure how to view it), I did not see any "error" string. I did try setting osC Logging [store page parse time] to "true", but I didn't see that it created the specified logging file directory or any log file (did I miss something) ?

 

FYI, here's an image of the osC shopping cart page that shows an example of how my osC buttons appear with image placeholders and text. You can see that various other images and a PayPal button are showing just fine :

 

[KDM]

which log file, and where is it ? ..not sure that I was logging in osC. Here's image of osC config setting for "Logging" :

 

 

My server has a logging file, but when I searched that very long file text (unformatted...not sure how to view it), I did not see any "error" string. I did try setting osC Logging [store page parse time] to "true", but I didn't see that it created the specified logging file directory or any log file (did I miss something) ?

 

 

Your log setting indicate that your log file is in the tmp folder of your main directory: catalog/tmp/

 

Assuming you have access to CPanel you should be able to look at your error logs there.

 

 

FYI, here's an image of the osC shopping cart page that shows an example of how my osC buttons appear with image placeholders and text. You can see that various other images and a PayPal button are showing just fine :

 

 

Right click your image button and highlight and click either properties or image info depending on your browser that should tell you where osCommerce is looking for the image. Check that location and see if the image is there.

example; catalog/includes/languages/english/images/buttons/button_continue_shopping.gif

[jlyman]

Thanks for your effort, KDM...my osCommerce directory tree has NO /tmp file anywhere, which I what I meant when I said that I tried to implement logging and found nothing created for it...no directly, no file.

 

I had checked the button properties from the web pages, and see nothing wrong with the web page pointer or the files in the proper directory. This is why I think that it might be a permissions or security problem of some sort. Can't see anything wrong with permissions, but I'm not as familiar with the .htaccess settings to scrutinize those properly.

 

However, there is a difference in the pointers between other images, such as :

 

https://jlymanco.ipower.com//osCommerce/catalog/images/table_background_login.gif'>https://jlymanco.ipower.com//osCommerce/catalog/images/table_background_login.gif

 

...and the osC buttons, pointing to :

 

https://jlymanco.ipower.com/home/users/web/b2055/ipw.jlymanco/public_html/osCommerce/catalog/includes/languages/english/images/buttons/button_continue.gif

 

...unless the "//" in the first pointer is meant to reference the additional string in the second pointer (?)

[KDM]

Thanks for your effort, KDM...my osCommerce directory tree has NO /tmp file anywhere, which I what I meant when I said that I tried to implement logging and found nothing created for it...no directly, no file.

 

I had checked the button properties from the web pages, and see nothing wrong with the web page pointer or the files in the proper directory. This is why I think that it might be a permissions or security problem of some sort. Can't see anything wrong with permissions, but I'm not as familiar with the .htaccess settings to scrutinize those properly.

 

I'm not sure what you mean by "...unless the "//" in the first pointer is meant to reference the additional string in the second pointer".

 

I think we are talking about the same thing. This is what I see.

 

I checked your website at this page:

Evapo-rust

 

This is the review button location:

review button

 

 

Your other image locations are referenced with something like this:

another image link

 

Notice that in the image that is showing there hsd an extra forward slash between .com and osCommerce.

It's not there on the button image, perhaps (and I'm not sure) this could be the problem.

More times than not it is something small that makes a difference.

[♥kymation]

Both of those links are wrong. The double slash is caused by an error in your configuration file. The incorrect path to the buttons is caused by a different error in your configuration file. Go fix the errors in /include/configure.php. Post that code here (without the database part) if you can't figure it out.

 

Regards

Jim

[KDM]

Both of those links are wrong. The double slash is caused by an error in your configuration file. The incorrect path to the buttons is caused by a different error in your configuration file. Go fix the errors in /include/configure.php. Post that code here (without the database part) if you can't figure it out.

 

Regards

Jim

 

 

Jim,

 

You of course are right the configuration file is where the path is set and I'm pretty sure that will be the problem.

Just strange that it finds the images on the path with double slashes.

Anyway thanks for a hand on this.

[jlyman]

Here are my osC config files with the various paths. You can see that the paths are mixed with and without the ".../home/users/web/b2055..." string and without it (?) :

 

catalog/admin/includes/configure.php

<?php

define('HTTP_SERVER', 'http://jlyman.com');

define('HTTP_CATALOG_SERVER', 'http://jlyman.com');

define('HTTPS_CATALOG_SERVER', 'http://jlyman.com');

define('ENABLE_SSL_CATALOG', 'false');

define('DIR_FS_DOCUMENT_ROOT', '/home/users/web/b2055/ipw.jlymanco/public_html/osCommerce/catalog/');

define('DIR_WS_ADMIN', '/osCommerce/catalog/admin/');

define('DIR_FS_ADMIN', '/home/users/web/b2055/ipw.jlymanco/public_html/osCommerce/catalog/admin/');

define('DIR_WS_CATALOG', '/osCommerce/catalog/');

define('DIR_FS_CATALOG', '/home/users/web/b2055/ipw.jlymanco/public_html/osCommerce/catalog/');

define('DIR_WS_IMAGES', 'images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_CATALOG_IMAGES', DIR_WS_CATALOG . 'images/');

define('DIR_WS_INCLUDES', 'includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');

define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');

define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');

define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');

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('DB_SERVER', 'jlymanco.ipowermysql.com');

define('DB_SERVER_USERNAME', 'xxxxxx');

define('DB_SERVER_PASSWORD', 'xxxxxxxxxx');

define('DB_DATABASE', 'xxxxxxxxxx');

define('USE_PCONNECT', 'false');

define('STORE_SESSIONS', 'mysql');

?>

 

 

catalog/includes/configure.php

 

<?php

define('HTTP_SERVER', 'https://jlymanco.ipower.com/');

define('HTTPS_SERVER', 'https://jlymanco.ipower.com/');

define('ENABLE_SSL', true);

define('HTTP_COOKIE_DOMAIN', 'jlymanco.ipower.com');

define('HTTPS_COOKIE_DOMAIN', 'jlymanco.ipower.com');

define('HTTP_COOKIE_PATH', '/osCommerce/catalog/');

define('HTTPS_COOKIE_PATH', '/osCommerce/catalog/');

define('DIR_WS_HTTP_CATALOG', '/osCommerce/catalog/');

define('DIR_WS_HTTPS_CATALOG', '/osCommerce/catalog/');

define('DIR_WS_IMAGES', 'images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_INCLUDES', '/home/users/web/b2055/ipw.jlymanco/public_html/osCommerce/catalog/includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');

define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');

define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');

define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');

 

define('DIR_WS_DOWNLOAD_PUBLIC', 'pub/');

define('DIR_FS_CATALOG', '/home/users/web/b2055/ipw.jlymanco/public_html/osCommerce/catalog/');

define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');

define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');

 

define('DB_SERVER', 'jlymanco.ipowermysql.com');

define('DB_SERVER_USERNAME', 'xxxxxxx');

define('DB_SERVER_PASSWORD', 'xxxxxxxxxx');

define('DB_DATABASE', 'xxxxxxxxxx');

define('USE_PCONNECT', 'false');

define('STORE_SESSIONS', 'mysql');

?>

[♥kymation]

I see that you have the catalog side set up for SSL and the admin the opposite. This will not work. I made both sides SSL; change it if you don't have a cert installed.

 

Admin side:

<?php
define('HTTP_SERVER', 'http://jlyman.com');
define('HTTP_CATALOG_SERVER', 'http://jlyman.com');
define('HTTPS_CATALOG_SERVER', 'https://jlyman.com');
define('ENABLE_SSL_CATALOG', true);
define('DIR_FS_DOCUMENT_ROOT', '/home/users/web/b2055/ipw.jlymanco/public_html/');
define('DIR_WS_ADMIN', '/osCommerce/catalog/admin/');
define('DIR_FS_ADMIN', '/home/users/web/b2055/ipw.jlymanco/public_html/osCommerce/catalog/admin/');
define('DIR_WS_CATALOG', '/osCommerce/catalog/');
define('DIR_FS_CATALOG', DIR_FS_DOCUMENT_ROOT . '/osCommerce/catalog/');
// Remainder the same

 

Catalog side:

<?php
define('HTTP_SERVER', 'http://jlyman.com');
define('HTTPS_SERVER', 'https://jlyman.com');
define('ENABLE_SSL', true);
define('HTTP_COOKIE_DOMAIN', 'jlyman.com');
define('HTTPS_COOKIE_DOMAIN', 'jlyman.com');
define('HTTP_COOKIE_PATH', '/osCommerce/catalog/');
define('HTTPS_COOKIE_PATH', '/osCommerce/catalog/');
define('DIR_WS_HTTP_CATALOG', '/osCommerce/catalog/');
define('DIR_WS_HTTPS_CATALOG', '/osCommerce/catalog/');
define('DIR_WS_IMAGES', 'images/');
define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');
define('DIR_WS_INCLUDES', 'includes/');
// Remainder the same

 

Security note: Once you have this working, change the name of your admin folder and the same in these two files.

 

Regards

Jim

 

Edit: typo.

[satish]

define('DIR_FS_DOCUMENT_ROOT', '/home/**************************/'); letting people know this adds to your risk.

 

 

 

 

Satish

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

[jlyman]

define('DIR_FS_DOCUMENT_ROOT', '/home/**************************/'); letting people know this adds to your risk.

 

Satish

 

 

...a number of comments & questions here about this :

 

1) recommended path changes above by kymantion, 5/9, didn't work for me. Specifically, the line #10 change in /admin/includes/configure.php

define('DIR_FS_CATALOG', DIR_FS_DOCUMENT_ROOT . '/osCommerce/catalog/');

[♥kymation]

This will not work if:

1. DIR_FS_DOCUMENT_ROOT is not correctly defined.

2. Your store is not installed in /osCommerce/catalog/

 

Regards

Jim

[jlyman]

...a number of comments & questions here about this :

 

1) recommended path changes above by kymantion, 5/9, didn't work for me. Specifically, the line #10 change in /admin/includes/configure.php

define('DIR_FS_CATALOG', DIR_FS_DOCUMENT_ROOT . '/osCommerce/catalog/');

 

...accidentally entered unfinished reply...continuing here...

1) (cont'd)....and the change in /includes/configure.php line #13 to

define('DIR_WS_INCLUDES', 'includes/');

 

The basic problem seems to be with the path " .../home/users/web/b2055/ipw.jlymanco/public_html/osCommerce/catalog..." . File/images there cannot be directly accessed with the path entered into a broswer address, so there is some kind of permissions/security issue I think. I checked the path validity on the server, so that is OK.

 

The ISP support finally chimed in and "...corrected the 'DIR_WS_INCLUDES' path in your configuration file '/osCommerce/catalog/includes/configure.php', " . I'm not sure where that change was made, and here are the present configurations :

 

.../catalog/admin/includes/configure.php

 

<?php

define('HTTP_SERVER', 'http://jlyman.com');

define('HTTP_CATALOG_SERVER', 'http://jlyman.com');

define('HTTPS_CATALOG_SERVER', 'https://jlyman.com');

define('ENABLE_SSL_CATALOG', 'true');

define('DIR_FS_DOCUMENT_ROOT', '/home/users/web/b2055/ipw.jlymanco/public_html/');

define('DIR_WS_ADMIN', '/osCommerce/catalog/adminJLI/');

define('DIR_FS_ADMIN', '/home/users/web/b2055/ipw.jlymanco/public_html/osCommerce/catalog/adminJLI/');

define('DIR_WS_CATALOG', '/osCommerce/catalog/');

define('DIR_FS_CATALOG', DIR_FS_DOCUMENT_ROOT . '/osCommerce/catalog/');

define('DIR_WS_IMAGES', 'images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_CATALOG_IMAGES', DIR_WS_CATALOG . 'images/');

define('DIR_WS_INCLUDES', 'includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');

define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');

define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');

define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');

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/');

 

 

.../catalog/includes/configure.php

 

<?php

define('HTTP_SERVER', 'https://jlymanco.ipower.com/');

define('HTTPS_SERVER', 'https://jlymanco.ipower.com/');

define('ENABLE_SSL', true);

define('HTTP_COOKIE_DOMAIN', 'jlymanco.ipower.com');

define('HTTPS_COOKIE_DOMAIN', 'jlymanco.ipower.com');

define('HTTP_COOKIE_PATH', '/osCommerce/catalog/');

define('HTTPS_COOKIE_PATH', '/osCommerce/catalog/');

define('DIR_WS_HTTP_CATALOG', '/osCommerce/catalog/');

define('DIR_WS_HTTPS_CATALOG', '/osCommerce/catalog/');

define('DIR_WS_IMAGES', 'images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_INCLUDES', 'includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');

define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');

define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');

define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');

 

 

Can anyone explain the difference between the two different paths in these config files that start either with '/home/users/web/b2055/ipw.jlymanco/public_html/osCommerce/catalog.. versus '/osCommerce/catalog... ??? Research shows that config files normally contain these two different types of paths. While my osC shows the buttons now, I'm not sure that the ISP's "fix" is appropriate. I haven't seen other problems with programs or files directed from the '/home/users/web/b2055...' paths, but can't say I've gone through all of the programs in detail to check it.

 

And what is the difference between the variables defined for 'DIR_WS_...' versus 'DIR_FS_...' ???

 

 

 

Before my ISP's fix, I notices that checking "view image info" from my browser on the osC pages with missing buttons had showed thumbs of all of the page images that were directed from the '/osCommerce/catalog...' paths and also identified them as GIF files, while the buttons directed from '/home/users/web/b2055...' path and not showing were identified as "text/html" files (though the GIF files were properly placed in the file structure...I even FTP re-wrote them as binaries). Don't understand while the brower identified the page buttons as text/html files, unless that was a default because the page didn't have access to the button images.

 

My system as originally configured had been working just fine, so don't know why any of these button problems occurred in the first place. Now I'm concerned about whether the ISP fix is appropriate, though it seems to work.

 

 

2) FYI I do operate with custom-named admin file...didn't show that here, though

 

3) please explain more about the last posting

" define('DIR_FS_DOCUMENT_ROOT', '/home/**************************/'); letting people know this adds to your risk."

[♥kymation]

DIR_WS_... constants are filesystem links. They are used to find a file based on the path from the server root to the file.

 

DIR_FS_... constants are webserver links. They are used to find a web page based on the path from the location the URL points to (public_html in your case.)

 

Your ISP is worng. None of these paths should ever contain a filename, and the includes directory is referenced from DIR_WS_HTTP_CATALOG and should not include that path.

 

Regards

Jim

[KDM]

...a number of comments & questions here about this :

 

1) recommended path changes above by kymantion, 5/9, didn't work for me. Specifically, the line #10 change in /admin/includes/configure.php

define('DIR_FS_CATALOG', DIR_FS_DOCUMENT_ROOT . '/osCommerce/catalog/');

 

Do you have the define line above after:

define('DIR_FS_DOCUMENT_ROOT', '/home/users/web/b2055/ipw.jlymanco/public_html/');

 

If the define in question is after it, the system will read the path as:

/home/users/web/b2055/ipw.jlymanco/public_html//osCommerce/catalog//osCommerce/catalog/

 

else you would have this as the path:

/osCommerce/catalog/

We know this would never work. A value must be in "DIR_FS_DOCUMENT_ROOT" first.

 

 

This is also where your double forward slash is coming from, with few exceptions my define varibles in configure.php has no leading forward slash since they all have trailing forward slash. If you have them at both ends you will have double slashes when you concatenate them. You should never see this, that is why I questioned the double slashes in my comments.

 

Here is an example of some of my define varibles:

 

 define('DIR_FS_DOCUMENT_ROOT', '/xxxx/xxxxx/xxxxxxxxx/xxxx/xxx/');  
 define('DIR_WS_ADMIN', '/admin/');
 define('DIR_FS_ADMIN', '/xxxxx/xxxxxx/xxxxxxxx/xxxx/xxx/admin/');
 define('DIR_WS_CATALOG', '/');
 define('DIR_FS_CATALOG', DIR_FS_DOCUMENT_ROOT . '/');
 define('DIR_WS_IMAGES', 'images/');
 define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');
 define('DIR_WS_CATALOG_IMAGES', DIR_WS_CATALOG . 'images/');
 define('DIR_WS_INCLUDES', 'includes/');
 define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');
 define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');

 

Notice that each defined varible that references another define varible is always after that defined varible.

[FuelCellsEtc]

I have the exact same problem, but as an OSC raw newbie I am having trouble identifying exactly what the fix was in the thread above. Could someone help me identify where the issue is inorder to get my button images etc to re-appear? They were working just fine in the past and then randomly stopped showing up during a period of time when I hadn't even logged into OSC. It appears that the file paths are all correct, but the images still aren't showing.

 

The site is: http://fuelcellsetc.com/store/

 

My Config file looks like:

 

<?php

define('HTTP_SERVER', 'http://fuelcellsetc.com');

define('HTTPS_SERVER', 'https://fuelcellsetc.com');

define('ENABLE_SSL', false);

define('HTTP_COOKIE_DOMAIN', 'fuelcellsetc.com');

define('HTTPS_COOKIE_DOMAIN', 'fuelcellsetc.com');

define('HTTP_COOKIE_PATH', '/store/');

define('HTTPS_COOKIE_PATH', '/store/');

define('DIR_WS_HTTP_CATALOG', '/store/');

define('DIR_WS_HTTPS_CATALOG', '/store/');

define('DIR_WS_IMAGES', 'images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_INCLUDES', 'includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');

define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');

define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');

define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');

 

define('DIR_WS_DOWNLOAD_PUBLIC', 'pub/');

define('DIR_FS_CATALOG', '/home/fuelcell/public_html/store/');

define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');

define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');

[FuelCellsEtc]

Sorry, forgot to mention, and don't know if it matters, but it is a basic install of OSC 2.2 RC, no modifications thus far.

[spooks]

Your site is flagged as of very poor repute (!) , do you have viri on the site, (!) many must have had issues for the low rating to cause a block?

[FuelCellsEtc]

i believe it is blocked/flagged primarily due to SSL absent and nothing in my "privacy policy" document for quite sometime. As I say, it was a raw setup and I am now working on getting all of that resolved and updated, but if I can't get it to even display buttons properly, I may have to look as some other sort of Cart software that may be easier to use and integrate with the rest of my site.

 

I do also have a desire/need to be able to create some custom items that I think I may have better luck with in OSCommerce than some of the other Cart software. And I will certainly be posting more on that once I get a handle on the current site and the standard products. But first thing is first: get it operational and error free.

[♥kymation]

Your button images are generating a 500 server error. This is usually due to incorrect permission settings on the images or the directory they are in, or on a misplaced .htaccess file.

 

If this is a new install, you should not be using any of the osCommerce 2.2x series. Version 2.3.1 is far more secure, and it won't have the button image problems that you are seeing.

 

Regards

Jim

[spooks]

@@FuelCellsEtc

 

That's not it, your site is flagged as bad by a rating service that purely rates based on user reports.

 

Have you checked for viri, the most common area for hackers to hit is the images folder and thats what you say fails.

 

Of course the rating could be due to what's been on your domain before & nothing to do with your latest install.

 

I`d take a look, but am reluctant to ignore the warning, 'Don't go there!'

[FuelCellsEtc]

Jim,

 

Thank you so much! I just renamed .htaccess to .htaccess.bak and that fixed it.

I had thought I tried that, but I guess I hadn't. I'm still not quite sure why these .htaccess files do this sometimes for no apparent reason, but this certainly helps me.

 

This isn't a new install, and since I'm new and just barely starting to get the hang of OSC, I'm a little worried about upgrading. But I guess it would be better now than once I had a lot of stuff customized already.

I'm just ready to have an operational store underway.

 

Anyway, thank you again for helping

 

Spooks,

Thanks also, I'm not 100% sure how to go about checking for viruses etc from this end; but I will see what I can find out. I assume it's similar to a normal virus scan of the file location, even though it's located on a server instead of local and may be exposed to a different type of virus (I suspect?). I've had others who are more web dev savy than myself check and they said it was clean. Of course, any advice you are willing/able to give would be much appreciated, but I understand this is diverging a little from OSC specific help :)

 

Dan

[♥kymation]

I just checked, and your images folder is wide open. It's even willing to list its contents for me. You need to secure this thing ASAP. There's a pinned thread in the security forum about securing 2.2x stores. This is going to be a lot of work, and it needs to be done quickly. Some of the tools available are virus/malware scanners that can help you get rid of whatever infestation is already there.

 

The amount of work that you will spend on getting this site cleaned up and secured is probably a lot more than it would take to wipe it and install 2.3.1. It all depends on how much customization you have already done. Oh, and 2.3.1 is secure as is. No modifications needed.

 

Regards

Jim

[spooks]

@@FuelCellsEtc

 

Well taking a look at search results for your site I note every single page is rated as bad, which is un-usual, so if no virus (your host should be able to check that too) then it could be due to malicious rating by competitors. The service is called WOT and is a add-on to firefox browsers.

 

If you've never added any security though, then it is likely that you have been hit, read the thread & check the contents of all folders.

 

Re 501 You need your htaccess working, if not least for the security you've (hopefully) added to it, one way to find what caused the 501 is to empty it, then add things back bit by bit till the problem comes back. Again some hackers modify your htaccess to their own ends.