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,515 profile views
  1. Have you searched this forum for mysql_connect? mysql_ is old and deprecated, and has been replaced by mysqli_. This has been discussed a number of times. Anyway, it sounds like you are running a very old version of osCommerce. What osC version, and what PHP version? Any host worth using is running at least PHP 5.6 (7.1 is considered current), and osC 2.3.4BS "Edge" is the current osC release. The "Access denied" message may or may not be a separate issue. See if dealing with the MySQL/MySQLi issue fixes this one too. If not, maybe your DB password got reset or corrupted during the upgrade?
  2. You need to examine the page HTML (in your browser), and determine a unique selector path (ids, classes, elements) that marks the element you want to change. Let's say, it has an id="SalePrice" in the element. Then in user.css, #SalePrice { color: red; } The hard part is finding a selector path that doesn't hit unwanted elements.
  3. Does that mean you were editing PHP files? If so, I'll bet you left a blank or empty line at the beginning or end of one or more .php files. That will give you a 500 error.
  4. Yes, PHP 5.2 is way ancient, and you should be talking to your host about getting up to date (at least PHP 5.6). PHP 7.1 is considered the current level. Regarding your database, I don't know if MySQL autoincrement fields always start at 0 unless you take some explicit action to reset the counter to a higher level ("set auto-increment = 432" or something like that), or if they look at the highest existing value you import, and go from there. Possibly the former is what your database is set up to do. Did you run with default values before importing your backup? Maybe it didn't realize it needs to bump up the autoincrement value for each table. You can try doing it manually in phpMyAdmin ("Next autoindex" value) and see what happens. You probably should have a backup first...
  5. Glad you got it done. Most FTP clients are set up to show only 2000 files, and a backup is just one (large) file. All hosting control panels have a way to upload files, FTP can be used, and phpMyAdmin may even be set up to directly upload the import (.sql) file from your PC. Well, you got it done anyway.
  6. (more on export/import): 1) if you're only changing a few tables, snip them out of the .sql backup and import them one at a time 2) before importing a revised table, be sure to first empty (truncate) the existing table so that you don't get doubled entries. Of course, you should have a DB backup and know how to restore it, first. Working on a live store is trickier than one that's offline -- depending on the data being changed and how long it will take to truncate/import the table, and whether the table might get updated by a customer during this, you might want to take your store offline temporarily, to prevent such conflicts.
  7. Also consider doing a backup (export) to an .sql text file, and then using a good text editor such as ViM or Notepad++ to modify the text (e.g., globally replace http:// with https://, with, etc.). Finally, restore (import) into the database.
  8. So rather than a standard form, it's more of a chatbot with an agenda? It just asks you a series of questions until you've answered everything? I could see a problem with this, in that it's not clear what data will be requested, and you might add a piece of data in the wrong place because you need to give it, but don't know if it will be asked for. At least, if I can see the entire form, I can see what will be asked and where the most appropriate place to put some specific information will be. I can also judge how long this is going to take, and even whether they're going to want information that I don't care to give. Verdict: useless. Maybe it could be slightly useful for some situation where what questions are to be asked depends on earlier answers, but that can already be done with dynamic update of a form, or splitting it up into several pages.
  9. If Edge is using them interchangeably, it's wrong. It should pick one or the other, with consistent use of "Add to cart" being preferred. I think that's the clearest and least ambiguous phrasing, that won't leave a visitor fearful that they're committing to paying for the item like "Buy Now" might. A true "Buy Now" function would indeed require some changes (empty the cart, put this one item in it, and proceed to checkout -- more than that if you want to keep the existing cart contents and keep shopping, even more if you want to check for duplication between Buy Now and cart). I didn't say anything about "purchase later"; Flora said that. That would be a Wish List function. It's not a bad idea to have some sort of "Purchase" button everywhere that the item is displayed. If someone wants to throw a diamond ring in the cart without checking the details, that's their concern. Just make it clear that there is a way to get product details, if you're not already on that page (as an aside, being able to pull up product details on anything already in the cart would be useful, for comparison shopping). Having both Add to Cart and Buy Now could be confusing as to which is which, but would offer the convenience of impulse buying. Having icons on the buttons (arrow pointing down into shopping cart, and arrow pointing right to cash register) could help clarify which does what. I discussed before the problems of having both buttons, and conflicts between them. It's also possible to have multiple carts, if you wish to ship to different places or pay for some purchases with one method, and others with another credit card, all in one shopping trip. Malcolm, I just noticed in the email notification, that it's Artco Inc (incorporated). That sans-serif font that the forum uses I always saw as "Art Colonic" (an el rather than an EYE) :) (and always thought that was a rather strange ID to pick) That's why I dislike sans-serif fonts!
  10. Your biggest problem, if selling new merchandise under their brand name, is the likelihood that the manufacturer will come after you for "trademark violation". While legally (everywhere that I know of) they can't prevent you from reselling merchandise, they do have complete control over use of their trademark(s) and can make legal trouble for you over your unauthorized use of their trademark. They prefer that only authorized channels offer their goods, where they have some control over the quality, etc. of the buyer's experience. Consider yourself warned.
  11. Hi, Hank! :) Couldn't resist... Obviously this was designed by an artiste. I kept trying to enter my name somewhere in or near the prompt, before I happened to see the off-white-on-white "Enter name here"! I agree that this bozo doesn't know the first thing about designing a usable page. What does an up-pointing arrow mean? Oh, hit Enter! Problems can show up anywhere. This morning I was looking at the National Hurricane Center map of watches and warnings for Hurricane Maria. For hurricane watches, they chose a certain shade of pink that I, with red-green color deficiency, can't tell apart from the gray used for land. I can't see any watches unless I notice that it extends outside of the land boundary! I think I'll write to the NHC and give them some feedback on this.
  12. Exactly which version of osCommerce (2.3.4 BS Edge is the most current)? What PHP version? Did you check that the logo file (image file) was actually correctly uploaded, and is displayable in your browser (by going to the address of the file)? What does your Admin say the store logo currently is? Perhaps you need to set it to use your image, separately from uploading it.
  13. Don't forget that running PHP code in cron (system command line) is different from running it in the web server (via HTTP). You are not in the same environment, and may have different path settings, environmental settings, and even a different version of PHP. In general, if using cron, you want to make sure everything (paths, settings, etc.) are explicitly spelled out.
  14. Walmart's "Add to cart" button is not the same as a "Buy Now" button. I agree that it would be a bit unusual for someone to put such a major item in their cart without looking at the details page, but hey... maybe they just use the same template for $1.49 hair pins as they do for a $677.00 gas generator. Yeah, Walmart would count as "fair to middlin'" in size. Now, just what are we discussing here? Buy Now and Add to cart are two very different things (in my eyes, anyway) -- the former is a commitment to purchase immediately (go directly to shipping and payment), while the latter is merely putting the item in the cart or basket, to (probably) be purchased at the end in checkout. It doesn't really make sense to me to buy some items now and others (slightly) later, in the same shopping trip. It can make sense to offer both, for impulse purchases and normal purchasing, but as I discussed earlier, be wary of mixing the two. On the other hand, a discussion about where it makes sense to put purchase buttons (how many opportunities do you get to make that sale) is a good one, but is separate from the Buy Now/Add to Cart discussion.
  15. If I notified a store that I was changing my email address (through proper channels), I would certainly expect that any pending orders would change to the new email address. There should normally be only one email address stored for a customer (as part of the customer data), rather than an address stored for each order. Does osC store multiple copies? That would be called unnormalized data. I suppose that it's possible that additional email addresses might be stored for an order, such as a gift recipient's, but I don't think they should replace the primary email address. Don't forget that a notification of change should be sent to the old email address, just in case someone had done this change maliciously. Then you have a chance to manually change it back to the correct (old) address.