angelleye
Forum Replies Created
-
This has been fixed and will be included in the next update that we’ll be releasing soon!
Forum: Reviews
In reply to: [PayPal for Divi] DOSEN’T WORKWe do not have any other reports of this problem. You say no support… what is your ticket number with us?
Forum: Plugins
In reply to: [PayPal for WooCommerce] PAYFLOW COMMENT1 AND COMMENT2I did go ahead and get these hooks added to our current hook documentation.
It’s still not fully complete, but you can see quite a few hooks there you may not have known about.
Forum: Plugins
In reply to: [PayPal for WooCommerce] PAYFLOW COMMENT1 AND COMMENT2We have filter hooks available for these fields already. We just haven’t gotten it documented yet. That’s always helpful, huh!?
The hook name for COMMENT1 is
ae_pppf_custom_parameter, and the hook name for COMMENT2 isae_pppf_comment2_parameter.So this should get what you’re wanting done:
add_filter( 'ae_pppf_custom_parameter', 'own_ae_pppf_custom_parameter', 10, 2); function own_ae_pppf_custom_parameter($customer_note , $order) { return $order->get_order_number(); } add_filter( 'ae_pppf_comment2_parameter', 'own_ae_pppf_comment2_parameter', 10, 2); function own_ae_pppf_comment2_parameter($empty, $order) { return 'My Website'; }Just drop that into your (child) theme’s functions.php, or make yourself a little plugin file for it (which is what I prefer to do) and that should do it.
I’m a little confused about the context. Can you elaborate on the example please?
Hmmm…yes, we’ll check into this and figure out what’s going on there. We’ll get another update released to fix it soon (assuming we can reproduce it).
We’ll provide more info on that soon.
That sort of thing could be done pretty easily if you’re a WordPress coder, and that’s really what this plugin is for.
The whole idea is that it will quickly get you setup with an IPN data holder, basically, and let you do whatever you want to do with that data.
Are you familiar with writing hook functions for WordPress and interacting with the DB in general?
You should have a
subscr_idthat gets returned when you create the initial profile, and that same ID should be available in the subsequent subscription payments so that you can match them up.So I typically like to add the
subscr_idto my user profile record (or a related subscriptions table) with the actual payments in a related payments table.This would give you a tight relationship between all the data so you can pull any queries you need.
Forum: Plugins
In reply to: [PayPal for WooCommerce] ‘Undefined index’ during WC product save@alx359, Please go to Settings -> PayPal for WooCommerce -> Tools Tab. There will find our Bulk Edit Tool for Products.
From the Action drop-down, choose Disable Payment Action, and then for Target set All Products.
When you run that it will effectively set the database with a value for “disable”, and this should eliminate the PHP notice you’re seeing.
At that point, if you did need to specifically adjust that value for any product(s), you could do so accordingly.
Well, yes, but we need to clarify exactly what product you’re using. Are you creating Subscription buttons with PayPal Standard (HTML forms), or are you building recurring profiles using API calls?
The final review page is going to be required if you’re using Express Checkout and skipping the Woo checkout page. If you aren’t skipping the Woo checkout page, then you could skip the final review, but this is not the recommended experience. It’s recommended to avoid forcing users to fill out forms.
The option to disable T&S is actually related to when you’re skipping the Woo checkout page. If you’re skipping the Woo checkout page, and you want to skip the final review, then you’d have to also disable T&C in that case, so that it doesn’t force the final review. Without that option checked, if a T&C page is set and the Woo checkout page is skipped, then the final review would be necessary to get that T&C agreement.
Smart Buttons are not meant to work with the Woo Checkout page either. Pretty much everything you’re trying to do is meant to be used with “Express Checkout Shortcut”, which again, is the intended design of Express Checkout.
I know we tried to get the Smart Buttons working well in the Woo Checkout page originally and we struggled a bit. Since it’s not the intended use we haven’t focused on it again, but I’ll see if we can get that added to our next Sprint and get it worked out.
Not sure which option you’re referring to about Different Shipping Address..??
Forum: Plugins
In reply to: [PayPal for WooCommerce] Invalid Card Expiration DateWe have pushed a 1.5.3 update that resolves this problem. Thank you for reporting!
First, if you set the IPN URL the way you mentioned here it’s going to override your PayPal profile setting, so our plugin’s URL would never get hit, and any hooks you have configured would not be triggered.
Second, no, the recurring payment IPNs would not go to the original URL you set from the button variable. Those would go to whatever you have configured in the PayPal account profile.
As such, I always recommend that you use our plugin as a catch-all for your IPN solution as a whole. This way you can set the PayPal account to point to the URL our plugin provides, and you’ll have the freedom and flexibility to do anything you need based on payment status, transaction type, etc.
If you need the data to also be sent to the URL listener you’re using now from the button, that’s where our IPN Forwarder plugin comes into play. This allows you to forward the IPN data out from our base plugin to as many additional URLs as you need, so that they all work together.
Yes, those will trigger payment IPNs, so those will come through the same way.
For that you would just use the
paypal_ipn_for_wordpress_payment_status_completedhook.This will be triggered any time a payment of any kind comes through with the
Completedstatus.