Jump to content

MrPhil

Members
  • Content count

    8,158
  • Joined

  • Last visited

  • Days Won

    112

MrPhil last won the day on May 9 2020

MrPhil had the most liked content!

Profile Information

Recent Profile Visitors

114,619 profile views
  1. Phoenix 1.0.0.2, not 2.0.0.2?
  2. MrPhil

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

    Have you read the full thread, as well as related ones in the PayPal section? "Login with PayPal" is gone, replaced by "Connect". There are some suggested code changes to get this to work.
  3. MrPhil

    Login with Paypal

    IIRC, 5.010 is indeed the last full installation, and there are a number of incremental updates following it, up to 5.018. I haven't looked to see if all the updates will be applied in one "update" click, or if you have to update several times to get to 5.018, but you might want to keep an eye on what it's doing. I recall that there are gaps in the sequence (i.e., there are not 8 updates to get to 5.018). There have been some recent changes to PayPal (e.g., Connect vs Login), so 5.018 isn't the last word, but I think Harald has to manually do some code changes to bring it up to date. I don't know what his plans are there.
  4. MrPhil

    Auto Update Currencies

    If the code only looks at the time of day, and doesn't keep track of the day on which it was last run, it's not very good code. Anyway, if you can't run a proper "cron" job, look at "poor man's cron" examples that do track when the last time something was run was, and kick off the run if enough time has passed. Such code would be started from some place in osC such as application_top.php. I think there may be a poor man's cron in one of the mass mailing add-ons, where you don't want to dump an avalanche of emails on the system, but just dribble out a few at a time, then wait for the next run of osC that's a few minutes later. I don't know if anyone has generalized a PMC to run arbitrary modules at arbitrary times/dates, but that would be a great feature for osC. Perhaps you would be better off if you worked with your host to understand what their limitations are on cron jobs. It's understandable that they want to keep out-of-control scripts off their servers, but cron is a necessary part of any non-trivial website. You got burned once by not understanding what they allowed, but that doesn't mean you can't craft a cron job that they will allow.
  5. MrPhil

    Auto Update Currencies

    Does your host actually not let you run cron (on a Linux server), or do they restrict the kinds of things you can run, such as PHP scripts using 'php'? Mine does the latter, but they allow using cURL to run PHP scripts.
  6. MrPhil

    Login with PayPal saying return url is wrong

    I'll include it in the next release of Frozen patches. This is a separate issue from the Login/Connect with PayPal in the other thread, or does it affect it, too?
  7. MrPhil

    Login with PayPal saying return url is wrong

    Is this issue the same as (or related to) ? If it is, at the very least please put a pointer in that thread pointing to this one.
  8. MrPhil

    Ezsocial for osC2.3.4BS v1.0a

    Are the interface and logo unchanged, or is osC's implementation going to have to be completely redone, anyway? It sounds like the latter to me, but I guess it hasn't settled down yet.
  9. MrPhil

    Ezsocial for osC2.3.4BS v1.0a

    Since Google+ has mostly gone away, should we be thinking about removing it from stores? I never used it, but my understanding is that it's only available for "G Suite", whatever that is. Do the Google+ functions on osC still do anything, or are they just an embarrassment that osC hasn't been updated in ages? If it should go away, I can add that to my Frozen patch set. It will be up to others to fix Edge and the official product.
  10. MrPhil

    Database Optimizer

    Keep in mind that it's more than just changing function names mysql_ to mysqli_. Some parameter lists in the calls will also be changed, so you need to check those.
  11. 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.
  12. MrPhil

    Login with Paypal

    Login with PayPal has been changed to Connect with PayPal. See if anything in helps you.
  13. 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.
  14. 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?
  15. MrPhil

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

    It appears that there are incremental updates past 5.010. Do I have it right that I manually bring Frozen up to 5.010 with the PayPal app, and then apply the incremental updates 5.011, 14, 16, and 18 to be fully 5.018 ready? And then keep an eye open for further 5.xxx updates to come? I guess that HPDL is somehow keeping up to date with PayPal patches.
×