Jump to content

cdetdi

Members
  • Content count

    41
  • Joined

  • Last visited

  • Days Won

    1

cdetdi last won the day on April 10

cdetdi had the most liked content!

Profile Information

  • Real Name
    Corey

Recent Profile Visitors

2,532 profile views
  1. Had to do this as well.
  2. I think you're under estimating the pain of a broken shop here... Upgrades that you publish are excellent, but they don't come with (not saying they should come with) a list of stuff that will break if you install the update. As another owner said, if a shipping module is just outright broken, a 10 minute upgrade might turn into 1-2 HOURS of missed sales. And those are hours you don't get back - you still need to do shipping, inventory, payroll, customer service etc. In MY experience, being completely honest, upgrades are never 5-10 minutes, but typically 1-2 hours or longer. My shop is very customized, so don't take this as a complaint. This is sharing the fact that a small .x upgrade is a BIG deal for owners like myself. I'm hopping from frozen to Phoenix and it isn't painless. Stuff you expect to work just doesn't, and I'm updating/patching most of the things I use on the daily. I appreciate the move to "Approved Add-Ons", but I think it needs to go farther. If an add-on is "Approved" it must also mean that is is updated regularly - if it falls 30 days or more behind the current release it must loose its approved status. This means that users like myself can have confidence that we can upgrade to the latest release, with all approved modules in a timely fashion.
  3. Raiwa - I read your response, and I followed all the constants. I think you are missing my question. 'MODULE_HEADER_TAGS_POINTS_REWARDS_POINTS_POINTS_EXPIRES_REMIND' is a CONFIGURATION KEY that, I assumed, would be used in a script to auto remind. Accordingly I assumed it would be referenced in that script. If it is only used in the language file in order to build constant. 'EMAIL_EXPIRE_INTRO' then I should be able to find the tep_mail function that uses that constant. Searching/grepping for EMAIL_EXPIRE_INTRO yields no results other than the language files, so it isn't actually used anywhere that I can see. I'm just looking for a simple yes or no really if this remind function exists. I'll build it if not, just wanting clarification. ::EDIT FOR WORDINESS::
  4. I contacted Raiwa directly regarding this and he recommended I post on this thread in case others have this issue. The install instructions say: I was trying to determine how this script works so that I could adapt it for our integration with a third-party email system (Oracle's Bronto). However, I found no "Script" anywhere in the code that would make the points auto expire. Looking for guidance. I tried to find the script for auto expire by searching for the constant 'MODULE_HEADER_TAGS_POINTS_REWARDS_POINTS_POINTS_EXPIRES_REMIND' in the entire module package. The only instances I found of this are in the install functions. I did not find any other functions that check this value and then run a script. Does anyone use this feature?
  5. cdetdi

    Google reCAPTCHA v3

    Small nit: For v3 Recaptcha Google recommends enabling the tracking code on EVERY page load, not just ones you want to protect. This enables Google to create a traffic profile. e.g. if a customer has been shopping the site normally but then submits a contact us in a suspicious way (e.g. did a copy-paste autofill which was very fast) Google takes into account the non-spammy behavior beforehand. It looks like your module only loads on the hooked pages, I suggest loading the tracking code on all pages following Google's guidance.
  6. cdetdi

    Paypal Standard Payments Failing

    Working here too with updated cert.
  7. cdetdi

    Paypal Standard Payments Failing

    Submitted.
  8. cdetdi

    Paypal Standard Payments Failing

    Line by line review, the failed logs do not show the field for 'receipt_id'
  9. cdetdi

    Paypal Standard Payments Failing

    Balance works fine. The notify-validate logs show all the normal information, except that the response area is blank. Notify sync is much less data than normal, and again no response shown.
  10. cdetdi

    Paypal Standard Payments Failing

    I have been using Paypal both Payments Standard and Express checkout for years. As of Sunday at midnight, all my orders using Payments Standard get stuck in the initial order status. No payment information is posted to the order nor is the order moved to the status I have configured to move it once the IPN has been received. In the log all the PS logs show a red icon rather than green. They do not show "VALIDATED" on the bottom. The "_notify-synch" log is also different - only 5 lines rather than the customary information with more verbose order information. Went through files and nothing on my end changed. I also did not find in Paypal's docs any information about a change to the API as of Sunday night. ANY Help would be appreciated, as it is causing a headache for order processing. * UPDATE * I've avoided the order processing headache by disabling Payments Standard and moving all customers to Express Checkout.
  11. @Tsimi Wondering if Pheonix update is close before I tackle it myself. Also have some custom feature questions if you have time for a custom job hire.
  12. Got it, thanks. Coffee time....
  13. I'm hoping to add some code that disables the points system for customers who are wholesale accounts - they already get good discounts. I'm using your Pheonix Wholesale Pro module on a Phoenix build. Are you planning on accounting for customer wholesale type in the points system in the future? Since this is a complicated add-on with many modules, is there one location that would disable the entire system, or, do I need to add a check in every module/part of this add on? Thanks! C
  14. cdetdi

    Horizontal Megamenu

    Jim - are there plans to bring this up to Phoenix? Willing to sponsor the development, let me know.
  15. I don't think this is true any longer. I think the instant update API has been deprecated and will be discontinued going forward.
×