ArtcoInc

@Alexfillman I am going to give you the benefit of the doubt, and hope you are not just spamming us here. The site you have linked to is a WordPress site, not an osCommerce site. M

@brandnewen The simplest solution, although temporary, is to ask your host if they can roll back to a prior version of PHP. Some will, some won't. It doesn't hurt to ask. Beyond that, you have a couple of options. None will be quick and easy, though ... 1) Find another host that will allow you to use a prior version of PHP, and move your site to them 2) Choose one of the several osC forks that does run under newer versions of PHP, and migrate your site to the new version. You can do this with your existing host. 3) Try to update the code on your existing site to run under newer versions of PHP. If you are not a coder, this may be difficult. Plus, recognize that you would be making your own fork of osC, and no one else would be able to support it for you, 4) Move your site to another shopping cart. 5) Wait until osC v4 is released. We don't know when that will be, though. Can you wait? If any of this sounds too difficult to do yourself, you may need to hire a developer to do it for you. Good luck! Malcolm

@oldcelt Did you try changing your PHP version?

@oldcelt OCS v2.3.4.1 has not been updated in years. It was written back when PHP 5.x was the norm. Newer versions of PHP will cause problems with 2.3.4.1 ( shop owners have had their shops crash when their host upgraded PHP). Is there a reason you are installing v2.3.4.1? Not only will it have problems under current versions of PHP, it is not responsive (needed these days with all handheld devices), and Google will downgrade any site not responsive. There are a couple of osC forks on here that are more current (both in PHP and responsiveness), as well as the Phoenix fork. Or, you could wait until osC v4 is released. Do note that osC v4 is a completely new code base. HTH

@oldcelt Since you are installing this on your WAMP system, can you select a different version of PHP? Try running PHP v5.x, and see if that makes a difference.

@oldcelt Is this an install of a stock v2.3.4.1?

@oldcelt PHP version?

True, but less chance for error with adding the new file. Besides, it is just a suggestion.

@Soeb In 2.3.4.1, there is a file in the root (catalog) directory called stylesheet.css. I strongly suggest that you leave this file alone. Instead ... Create a new file in the same directory called user.css. In this file, add all of the CSS changes you want to make. Then, in /includes/template_top.php, add a call to load the new user.css file AFTER the call to load stylesheet.css. M

@Soeb While there are/were a number of "templates" available for purchase from a number of sources, I do not recommend any of them. Many/most of them altered core files, often with poor code practices. If all you want is to change the colors, fonts, and/or backgrounds, you can achieve all of this using CSS (Cascading Style Sheets). I don't remember if there is a user.css file in 2.3.4.1. If not, you can easily add one, and call it in the beginning of each page. If you are not familiar with CSS, it is essentially a new language ... something that we can't walk you through here on the forum. If you want more of a design change, you will have need to modify some of the core files. If you are not familiar with coding in HTML and PHP, this is again something we can't walk you through here on the forum. I would strongly recommend you hiring a developer. Lastly, please be aware that 2.3.4.1 is quite old, and has not been updated in many years. It will not run under current versions of PHP, nor is it responsive (necessary these days with cell phones and tablets). If all of this sounds too complicated, I again recommend you consult with a developer. Malcolm

@ce7 Have you tried this? (in fact, please read the entire thread) There is also another discussion on this subject in the other forum. HTH M

@Jack_mcs Thank you again. I can view the search history in this shop (I have an add-on installed), and I see that this all started around April 25. Since then, there have been over 400 searches for either 2022 or 2023. And other than the Date Available field, I don't think that there is anything in the part listing that refers to a date, or these numbers. Going through the Search Log, I see that the actual search is for "2022" or "2023" (without the quotes). In the log, I have history of longer, multi-word searches (including some obvious exploit attempts). So, yea. Thanks again! Malcolm

@Jack_mcs Thank you. Here's a sample of the Who's Online page ... 00:02:520Guest207.46.13.21008:28:5508:28:55/catalog/advanced_search_result.php?search_in_description=1&keywords=2023 00:11:100Guest207.46.13.15508:20:3708:20:37/catalog/advanced_search_result.php?search_in_description=1&keywords=2022 00:24:420Guest207.46.13.15508:07:0508:20:34/catalog/advanced_search.php?search_in_description=1& 00:12:080Guest207.46.13.4508:19:3908:29:36/catalog/advanced_search_result.php?search_in_description=1&keywords=2022 00:00:500Guest40.77.167.7408:30:5708:30:57/catalog/advanced_search_result.php?search_in_description=1&keywords=2023 00:03:200Guest40.77.167.7408:28:2708:28:27/catalog/advanced_search_result.php?search_in_description=1&keywords=2023 Malcolm

One of my shops has been getting MANY searches for the expressions "2022" and "2023" (without the quote signs), all from many different IP addresses. Is anyone aware of an exploit effort searching for these terms? Or, does anyone know why these searches are being made? TIA Malcolm

@killiank Are you keeping the same domain name? If so, all you need to do is change the index.html (or index.php) file in the root of your domain to point to the new folder with your new store. If not, you can do a redirect in the .htaccess file in the root directory of your old store to the url of the new store. HTH M