Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


MrPhil last won the day on May 22

MrPhil had the most liked content!

Profile Information

Recent Profile Visitors

109,009 profile views
  1. MrPhil

    Admin password reset

    Then you're talking about the password-protection on your admin directory? It would be best to back out the .htaccess changes that invoke the password protection, and use your host's control panel function to "password protect a directory". Note that the osC Security Check page will complain that there is no password protection, but so long as you have to enter an extra ID and password before you can sign in, it's working. Possibly there is a way to directly change (or force a change in) the password in the .htpasswd file with your hosting control panel file editor, but I've never tried that. You might look in the files and see if there's anything that looks like a password you recall. I would hope that it stores the password in a hashed form (encrypted), but then you won't be able to recover it by looking in the file. You may be able to delete the hashed password and have it ask for a new one when you sign on for the first time. If you emptied your administrators table, you will also have to create a password for that login. By the way, osC 2.3.1 is absolutely ancient. It is going to fall over dead as soon as your host upgrades to PHP 7. You should be thinking about migrating to "Frozen".
  2. MrPhil

    Modifying the create account page - Frozen BS

    RE: "where is the text that says..."
  3. MrPhil

    Call to undefined method error - Please help

    Blindly renaming class function names to __construct may cause problems. See the discussion in In some cases you may need to leave class function name and build either a dummy __construct or one that calls class function name. You could get a copy of Frozen and look at the class code to see what was done there. If this is just a temporary bridge until you can get onto Frozen (or even Edge), you might want to consider simply suppressing "deprecated" warnings. There's plenty of discussion on this forum. It's not a permanent fix, as eventually something will be removed from PHP and cause serious errors, but it could tide you over until you have an up-to-date osC running (2.3.4 is quite long of tooth).
  4. MrPhil

    Editing Footer Links...

    Text such as "Conditions of Use" will normally be found in one of the "language" directory files. Rather than searching through them manually, use a tool such as findstr (Windows) or grep (Linux) to search all your .php files for the string "Conditions of Use". Then just edit the file that came up. Don't forget the /s or -S flag to search all subdirectories below the top one. This way you never have to ask again "where do I find such-and-such string?". Give a man a fish... Adding a new link means finding the code that outputs to the appropriate section of the screen, and modifying it. You of course need to be fairly able in HTML and PHP (don't use a WYSIWYG page editor to do this -- it will mess up the code).
  5. OK, we're talking about two different kinds of "deposits", but the same (or very similar) code might handle both of them. @nomaUsageDom wants a non-taxable deposit (for recycling) that shows up as a line item in the receipt. @supercheaphobb wants customers to leave a refundable (if you end up having to cancel the order) deposit (earnest money), not taxed, with the balance and full tax due later. The deposit might be the only item on the receipt. The accounting would be handled differently between the two. For the recycling deposit, if it could come after the merchandise subtotal, it might be handled like a tax (GST, VAT, etc. modules?). If it needs to be in the merchandise list, perhaps the shopping cart could be modified to automatically add a new item in the cart -- the deposit? You'd have to add some checks that the shopper doesn't remove the automatically-added deposit "item" from the cart! For the earnest money deposit, are there any add-ons for "layaway plans", etc.? Maybe such could be modified to sell an "item" which is not a deliverable in and of itself, and is not taxable. I suppose you would always want in your records that the full item was ordered, but only partial payment received so far. Maybe someone has already come up with a good way to do this.
  6. MrPhil

    Upgrading to the latest version

    You've got two entirely separate things here: 1) conversion of the DB from old schema to new, and 2) selective editing of DB content. I wouldn't try to mix them -- do (1) then (2). You'll often get yourself in trouble if you try to transfer table-by-table. I find it better to change the DB layout (schema) from old to new in one go, and then edit content at my leisure, either in the .sql backup, or on the live DB using phpMyAdmin. My preferred method is to dump both the old and new databases in .sql file format, including the table creation commands (which gives you the layout). It's not rocket science to compare each table, field-by-field, and update the old DB's .sql file; it's just painstaking and meticulous work. If there are add-ons and other customizations to the old store, that is really the only way to do it. If new fields are added, you may have to synthesize appropriate data for them. Has anyone come up with a tool yet to take an old .sql dump and a new one, and generate the SQL needed to update the old DB to the new one's schema (leaving alone add-on changes)? You'd still have to eyeball the SQL to check what it's doing. Of course this requires getting your hands dirty in the depths of the database, and is not for the faint of heart. So long as you keep a backup of the database you're modifying, and know how to use that backup to restore the DB (if you've modified a live one on the system), you shouldn't cause a catastrophe -- you can always start over.
  7. So you want to add some fixed amount (or percentage) to the price? Are the reasons that you don't want to simply increase the price by that amount that 1) it shouldn't be taxed, 2) you want it listed as a separate item? The product description could take care of the second objection with "price includes 20% recuperation deposit" etc., but it would still be taxed. As this is different from shipping charges (which may or may not be taxable themselves) I guess you couldn't call it a shipping charge, unless there is a way to add a second shipping charge (and set it as non-taxable). All I can suggest at this point is to maybe look at the "minimum order fee" and modify it in some way to reflect the charges you want to make, and set it as non-taxable? There also may be some sort of "per item shipping fee" code that could be your starting point, if there isn't already something ready-to-go.
  8. MrPhil

    Login with Paypal

    Login with PayPal has been changed to Connect with PayPal. See if anything in helps you.
  9. MrPhil

    Admin password reset

    Can you get to the database (such as with phpMyAdmin) from your hosting control panel? Just truncate (empty) the administrators table. When you try signing on again, you'll be asked for a new administrator ID and password.
  10. Without logging visits to the old site (new code needed: maybe add something to the Query String during the redirect, and process it in new code at your new store), all you can do is guess how long people will continue to use bookmarks to the old site. Search engines should be gone within 2 or 3 months at most... maybe allow 6 months for people not to show up at the old site? Someone is bound to follow an old link or bookmark two years from now, but at some point you've got to cut your losses of maintaining a redundant site (cost of extra domain name registration, but you ought to be able to share hosting with the new store [see "add-on domain" on most servers]).
  11. Of course, that's on the old store's site, pointing to the new store site. If you've lost access to the old site, you're probably out of luck.
  12. If it's just some orders, and it's fairly old osC code, I've seen this problem with customers failing to properly return to the store after completing payment. That is, they "back" up or otherwise go off someplace else from the PayPal site, and never return to the store to complete the transaction. This assumes it's a PayPal mode that takes the customer offsite (to paypal.com). I think that some of the more recent osC versions may have code to successfully complete the transaction even if the customer never returns (but PayPal signals that it completed). You might look around at that (and discussion on this forum). Otherwise, it's operator error. About the best you could do is to put in a BIG REMINDER before they're sent off to the PayPal site that they need to come back to your store in a certain way, for the transaction to complete.
  13. MrPhil

    PayPal App v5.018 Log In with PayPal is now dead

    At this point, I see no reason to carry this further, here. If you think there are security problems, feel free to start a new topic/thread and continue that part of the discussion there. Perhaps someone more familiar with the work and reasons for changing to the short forms ( @burt ?) could speak to this. Has Pete found an area of legitimate concern, or is he mistaken? In places where these superglobals could potentially be used to inject nasties, I was under the impression that cleanup was done on a case-by-case basis rather than globally. Of course, this does increase the chance that some case will be overlooked! Are "magic quotes" still around? I thought I heard about their being withdrawn. Certainly, we should always be on the lookout for places where $_* could be used to inject malicious code. Should cleanup be restricted to places where it could actually be used to do something bad (in HTML sent back to the browser, in database fields, etc.)? Is there such a thing as a universal cleanup that could be done?
  14. MrPhil

    Change to EDGE from Frozen

    You can keep your products, moving from any version of osC to any other, but you'll have to compare the database structures (schemas). It's likely that you'll have to massage the old DB to be structured the same as the new, a manual operation. When moving from one version to the next one up, SQL is often provided to do this for you, but I don't think there's anything for Frozen -> Edge. I don't think there are massive changes in the DB, but there might be a few. You are aware that Edge is a moving target (unstable -- a feature added today may be gone tomorrow)? Have you thought out why you want to leave Frozen and move to Edge? Is it worth the effort? Beyond the performance improvement of BSv4 support, I'm not sure there is that much changed. If you are having problems with Frozen, be sure to apply the patches (another manual operation; see link in my signature below).
  15. If your products, SEO, directory structure, etc. are identical between the two sites, and the domain name is the only difference, it's very simple. In .htaccess, RewriteEngine On Rewrite ^(.*)$ https://<www.newdomain.com>/$1 [R=301,L] This assumes everything on the old site is to be sent over to the new site. If you want only part of traffic (to the old store) to be redirected, or the old store is in a directory of its own (a good idea), it would be done a bit differently.