Latest News: (loading..)


  • Content count

  • Joined

  • Last visited

  • Days Won


MrPhil last won the day on August 19

MrPhil had the most liked content!

About MrPhil

Profile Information

  • Real Name
  • Gender

Recent Profile Visitors

101,896 profile views
  1. The wonderful thing about computers and websites is that you can tear it all down and start over. It's not like your parents gave you a stupid name and you have to decide whether to live with it for the rest of your life or cause a major disruption to your records and offend your parents by going to court and changing it. Don't sweat it over your store installation -- if you screw up, you can always redo it. Regarding the database, the server is usually the machine where the DB lives. If it's on the same machine as your website, it is usually "localhost" or "". If it's on a separate machine, it will be a name such as "" or an IP address. Ask your host. There will be a database name that allows you to tell apart multiple databases you may own, such as "osCshopDB". On shared servers, where many accounts will be naming databases, hosts often have you prepend your account name to the DB name: myacctname_osCshopDB when referring to it, such as in config.php. Finally, you create a user and the associated password who is the one who authorized to actually perform operations on the DB, including everything to do with running the store. Again, the name will often have the account name prepended to it for use in the configuration file, etc. There should be full instructions with the files. You're overthinking it all. Relax... you're not doing anything permanent and irreversible. You can always start over with no penalty.
  2. If it has a "responsive-osCommerce-master" directory, then you didn't unzip it quite correctly. It should just be "catalog" (or change it to "shop" if you prefer). On your PC, you should be able to drag and drop the directories from under responsive-osCommerce-master to be under catalog. You might even be able to do that in your hosting control panel (some sort of "Move" operation for directories). In any case, it should be easy enough to shuffle stuff around to the right place.
  3. Very old osC versions fail to set the $language variable on newer PHP versions. What exactly is the osC version you're running? is not really up to date, and I don't think it has a "gold" release. Are you really talking about osC 2.3.4BS Edge, which is the only production-ready osC release that runs on PHP 7? That's the one you should be installing and using.
  4. I don't think I've ever seen an application that went directly to the printer when I pressed the Print button, without a dialog asking for the printer to be used, and its settings. That includes word processors, browsers, mail clients, and PDF readers. They use OS/windowing services to select the printer. About the best you could probably do is to write the output to a temporary file, and then under the covers, batch submit it (via command line) to a printer. You might, under your OS, be able to associate custom printer names for different paper trays and modes on one printer, as well as for physically separate printers. Or, the command could specify the paper tray, landscape/portrait, etc. Would it be adequate to still have a print dialog, but have everything prefilled/preselected based on which queue you sent to? Is that what you're asking for? That gives you a chance to recover if the printer went down, ran out of paper or ink, or otherwise had problems. Then it's normally just one "go ahead and print the thing" button click. Your OS might have a print dialog that you could invoke from your store application, along with pre-setting all the choices. It might even have the ability to accept the file on a socket or pipe, so that you don't have to write a file first. Naturally, all this is going to be very OS-dependent, but it might be possible to put some hooks into osC to help with the process. Just some random thoughts... I'd like to hear the thoughts of others (I'll take off my tinfoil hat, first!).
  5. WHERE is this one running? Old server or new? The only reason I can think of that your old server is not redirecting to the new server, is that your shop URLs are coming in on (not and thus not being caught by your RewriteCond given in the first post. My change (www\.)? should take care of that. Now, how about the root .htaccess on your new site? Does it have anything blocking /shop, or even redirecting back to the old site? And your new site has the same directory structure as the old one? What happens when you send a URL to the old shop? Do you get any error messages?
  6. If you have the typical entry-level shared hosting, as Malcolm said, MySQL should already be installed for you. It likely resides on another server, or some systems still have it share space on your server (address = "localhost"). Your host will tell you. You (or your application installer) will not be installing MySQL, but rather, will be creating a database on it and then filling it with tables and data. Any host should back it up for you, but it's still a good idea to run some utility (such as "Export" on phpMyAdmin) once in a while to back it up onto your PC. Needless to say, you should get some practice in restoring files and database from your personal backups, before there's an emergency and you need to figure it out for real. By the way, if you've been around the business long enough, you've heard more than a few horror stories about host daily backups that were defective for one reason or another, and if you didn't have your own personal backup, you're screwed. Now, if instead of a shared hosting server, you bought a bare-metal dedicated server or co-location deal, you might very well be responsible for installing MySQL yourself. However, it sounds like you are nowhere near the experience level needed, and would have no business trying to do that yourself.
  7. If you don't even know what a "database" is, you'd better not try doing this yourself. You'll need to hire someone who knows what they're doing. There are listings in the commercial support section of this forum. By the way, it's rare that a hacker would destroy your database, too. Even if they did (and it's possible), your host may have a backup they can restore for you, although they usually don't keep them around for more than a week or so. That would at least preserve your existing data. Hopefully you've learned a lesson about keeping regular backups of your site files and your database!
  8. This .htaccess is in the root of your OLD website, right? And you have RewriteEngine On? Just for safety, I would make the www optional, in case any incoming links are without it: RewriteEngine On RewriteCond %{HTTP_HOST} ^(www\.)?oldwebsite\.com [NC] RewriteRule ^(.*)$$1 [R=301,L] That ought to work if this is on your old site's root. Is your old osC installation in the root or in /catalog (where it should be)? You'll have to inspect your .htaccess file to make sure you don't have anything before this that's catching your osC addresses. And obviously, on your new site you have nothing that's redirecting back to the old site, or anything crazy like that. Is your new site on the same server as the old one (the new one is an "add-on domain" under the same account)? Or are they on different machines? If it's an add-on domain, that could complicate matters as the new site will have its own root.
  9. If you did install from HM's control panel, you probably ended up installing osC 2.3.4. That's what they'll presumably have you install again. DON'T. It's totally obsolete. The only production-ready up-to-date version you should use is available on GitHub and is osC 2.3.4BS "Edge". You will need to migrate your database to the new format. Once you're on "Edge", you will have a completely up-to-date store compatible with PHP 7.0 (maybe 7.1 by now) and is RESPONSIVE.
  10. No level of government will care that you are running a classified ads site, so no permission is needed. However, there are a number of ads for illegal products or services that could get you in trouble, and you need to remove immediately, such as narcotics dealing, sex trafficking, murder for hire, and stolen or forged goods including credit card numbers. You'll need to scan your ads for keywords, either manually or automatically, and flag suspicious ads. There are already a number of online classified ads sites running in the USA, so you will have lots of competition. I suggest moving this to E-commerce Laws section.
  11. Have you looked at Easy Populate? It's spreadsheet (CSV file) mass update of your store database, and might be what you're looking for.
  12. It's certainly not harmful to be highly ranked in Google and other search engines, and that's useful for helping to pull in fresh eyeballs. However, it's not the be-all and end-all of your site. Once visitors are there, you want something that will engage them, keep them around, buy something (if you're selling), and come back again and again. You don't want to fall into the trap of "teaching to the test", where kids graduate from High School able to breeze through standardized exams, but have otherwise learned absolutely nothing in 13 years of "education". Concentrating too much on SEO and neglecting the rest of the user experience can do this to you. On the other hand, the most fantastic site and user experience won't help you if no one knows about you, so you have to put some effort into SEO! If you are adequately covered with Social Media marketing and other non-search engine related outreach, you can de-emphasize seach engine results (ranking) if the changes to your site they require conflict with your other goals. P.S. pretty stellar company to be in, in your second post! :)
  13. "latest version" being what? The official current version 2.3.4 is totally obsolete -- don't use it. Install and run the community-supported version osC 2.3.4BS Edge instead, which is the only production-ready up-to-date version offered. 2.4 is still beta, and 3.0 is dead. may be a little better than plain 2.3.4, but is not totally updated. We'll also need to know your PHP version and which add-ons you've installed (if any).
  14. OK, then. I mentioned it because Some people blindly follow instructions and make a URL of http:, even when their site is entirely under SSL ( https: ). Don't count on an .htaccess 301 redirect to "fix" it to https. There's no guarantee that a remote site sending a callback will properly handle a 30x redirect coming back to it from your server.
  15. Consider running a daily cron job to list all your files (ls -la) and flag new ones and unexpected changes (to size or last update timestamp). Such a thing is helpful for discovering unauthorized changes to files, and added files (such as described in the article). It's another layer of security. One of the security add-ons might already incorporate this function. For very high traffic sites, checking two or three times a day might not be unreasonable. In the referenced article, someone got into an osC 2.3.4 site and planted a backdoor or data dumper. It didn't seem to describe how the hacker got in, though, leaving the possibility of a security hole in osC itself, or (more likely), some problem on the server or a compromised password.