esd3104
Forum Replies Created
-
Thanks. I found a work around using the Yoast Icon/Function in the top menubar. Subsequently the error seems to have fixed itself. Seems likely the offending plugin must have had an update, potentially the “BetterDocs” plugin I use which updated itself recently.
Anyway, seems to be resolved now, for me anyway.
Thanks for that. I will try to remember that email location for anything in the future.
@kariskyverge thank you very much. Just submitted as of 10:05 am US central time. The org name is North American MGB Register and the reply to email address is one from our @namgbr.net domain. I did post a link to this support thread in the message also. Thanks.
@amberskyverge thanks for the quick response. I don’t believe this has been happening all the time but I can’t pinpoint when it started.
Interestingly in another account we have for payments (same organization different sales channel) this problem doesn’t show up. Just a single “GDP*” prefix. So, it appears to not necessarily be a universal issue but may be tied to one specific payment account.
In the dashboard for the affected account (Settings > Payments > Receipts & Statements I’ve checked what’s entered there and the “GDP*” is not entered by us and the example statement image on the page doesn’t show the duplicate “GDP*”.
Please let me know what additional info is needed or we can take this offline to emails and I can provide details/account numbers/screen shots – whatever might be needed.
Forum: Plugins
In reply to: [Autoptimize] Suddenly Seeing Server 500 Errors – Logs Point to AutoptimizeThanks for the quick response. I have been working though some other issues in my hosting account.
I will look at this in due course but I will follow this approach to re-enable. I’ll mark as resolved for now as it looks to be unique to me/my hosting.
The EmbedPress folks seem to have a fix, just need to wait for a updated production version to be released. See https://ww.wp.xz.cn/support/topic/fyi-css-conflict-with-pretty-google-calendar-plugin/
That patch version seems to work/solve the conflict. I’ve installed and the calendar display is now the same as it is on my prod site with EmbedPress disabled.
Forum: Plugins
In reply to: [GoDaddy Payments for WooCommerce] What Does version 1.7.5 actually change?OK, to rephrase, to check my understanding, the transaction will only be declined if the AVS result fails to match the ZIP/Postal Code. If the ZIP/Postal Code matches but the street address does not, the transaction will be approved.
If that’s correct this should be a useful update. 👍
@kariskyverge so after 50+ transactions I am not seeing any issues. Just 1 customer had an issue but they live in an apartment for which addressing can always be error prone. They apparently correctly changed the address to match so seems the bug fix implemented is working as expected. 👍
Thanks, I also got a note from Ed that the bug had been fixed. I have flipped GDP back on but until I get some renewals for club membership I won’t know if it’s working. That should happen around May 15 when the next reminders hit. Tks
Thanks for responding – no additional questions at this time. It seems your core systems are setup to decline anything that is not an AVS response code of Y which is frankly insane to apply to every single merchant. I get what the fraud concern is, but trust me, what is implemented isn’t the solution.
I posted here because you actually respond. 🙂 In another post it was mentioned about getting support vie the GDP Portal. I tried chat and got no response so I sent an email via that option and also got zero response (a different unrelated to AVS issue). 🙁
I’d actually love to help and provide input if anyone wants to connect. As a payments systems person, its distressing to see what could be a great merchant processing/gateway service be ruined by bad decisions in the core processing logic.
Forum: Plugins
In reply to: [GoDaddy Payments for WooCommerce] Increased number of AVS errorsYep @marekop I have this same debate after a round of AVS problems that seem to come in spells. My time (a volunteer) vs. the cost savings is an ongoing debate. There’s a lot of good things about GDP but the change they made with AVS was bad. It’s not as bad as when first implemented, but usually once a week I consider dumping them because of an AVS issue.
- This reply was modified 2 years ago by esd3104.
For anyone else needing this solution the code snippet problem was caused by single quote translation issues. By replacing all single quote marks with my keyboard it worked as expected.
function sv_custom_button_text_place_order( $button_text ) { return 'Make Payment'; // new text goes here } add_filter( 'wc_payment_gateway_poynt_credit_card_order_button_text', 'sv_custom_button_text_place_order' );Forum: Plugins
In reply to: [GoDaddy Payments for WooCommerce] Increased number of AVS errors@marekop you may find this interesting. https://ww.wp.xz.cn/support/topic/canada-avs-issues/
There are still too many AVS failures and there’s no way as a Merchant you can set what the GoDaddy Payments does in terms of accepting AVS or controlling how strict (or not) it is applied. For me ZIP code alone matching is “good enough”.
For now I tolerate this annoyance but it’s far from ideal and other processors allow the control of AVS strictness on a merchant by merchant basis.
I have submitted my contact info using the form and the “I’m getting in touch for something else” option as none of the others seemed to provide appropriate options.