Forum Replies Created

Viewing 15 replies - 16 through 30 (of 158 total)
  • Thread Starter ttoaster

    (@ttoaster)

    Hi Elliot,

    It is happening on at least the WordPress login form; haven’t tried the others yet. But I suspect it will also fail on the Comments form (WordPress) and Woocommerce login and review forms too.

    Update: Just tried it again on one of my Dev sites, and now it appears to be working just fine?

    • This reply was modified 1 year, 4 months ago by ttoaster.
    Thread Starter ttoaster

    (@ttoaster)

    An update for you:
    I have been watching all orders coming through and ALL orders using iDEAL are the only ones where duplicate emails are sent (both to me and to the customer).

    Thread Starter ttoaster

    (@ttoaster)

    Hi,

    No I do not have debug logging enabled (for privacy) so I do not have that data available, sorry.

    I have seen it with all iDEAL payments via your plugin, not just a few, all.

    I guess I’ll have to live with it then, and just field any questions from customers that may erroneously believe they have been charged twice for their order (or remove iDEAL as a payment option).

    Regards,
    Martin

    Thread Starter ttoaster

    (@ttoaster)

    Hi,

    As previously stated this is only happening with iDEAL, all other payment options are working as expected (single email per order, etc.)

    No, I don’t have multiple webhooks to this site, and no, I don’t use NGINX for my server, I use Apache.

    I have the following enabled (other than Credit card, Apple Pay and Browser Payments):

    Bancontact, Giropay, EPS, iDEAL, Przelewy24, Multibanco, Alipay and WeChat.

    This issue is not occurring with any of the others listed above, nor Credit Card, Apple Pay or Browser Payments.

    Regards,
    Martin

    Thread Starter ttoaster

    (@ttoaster)

    Hi,

    This is not happening with any other payment methods, only iDEAL, see the order notes for the latest one (sanitised for privacy):

    payment_intent.succeeded webhook received. Payment has been completed. 10th June 2023 at 15:20 Delete note

    Order charge successful in Stripe. Charge: py_XXXXXXXXXXXXtx498. Payment Method: iDEAL 10th June 2023 at 15:20 Delete note

    Order charge successful in Stripe. Charge: py_3XXXXXXXXXXXXtx498. Payment Method: iDEAL 10th June 2023 at 15:20 Delete note

    Order status changed from Pending payment to Completed. 10th June 2023 at 15:20 Delete note

    Order status changed from Pending payment to Completed. 10th June 2023 at 15:20 Delete note

    I don’t have any other plugins that change the order email processing logic.

    Regards,
    Martin

    Thread Starter ttoaster

    (@ttoaster)

    It is very simple, instead of the Tabs on the Product page being like this (side right column):

    Description
    Terms & Conditions
    Useful Links
    Reviews

    I would like to be able to show them like this instead (as a single line):

    Description | Terms & Conditions | Useful Links | Reviews

    As shown here (horizontal tabs) https://ps.w.org/yikes-inc-easy-custom-woocommerce-product-tabs/assets/screenshot-2.png?rev=2489914

    Thread Starter ttoaster

    (@ttoaster)

    Hi,

    Looks like it is clashing with WPS Hide Login, can you fix it?

    Thread Starter ttoaster

    (@ttoaster)

    Update: Just tried to install 3.7.0 (upgrade from 3.4.2) on one of my prod servers, and guess what?

    Yes, the very SAME error is displayed as with 3.5.0, 3.6.0 and 3.6.1! This is getting to be a real comedy of errors now, and it isn’t funny!

    So, NO it isn’t RESOLVED, far from it.

    Rolled back to 3.4.2, and it works fine, no errors!

    Thread Starter ttoaster

    (@ttoaster)

    Hi Saif,

    No, I am not prepared to waste any further time on this; this thread has all the data you need to identify the exact line and file in your plugin that is causing the error.

    It is a wonder that Square allow you to continue offering your “official” plugin as the number of issues with it, and the appalling rating it has is not doing their reputation any good.

    Thread Starter ttoaster

    (@ttoaster)

    Update: Just tried to install 3.6.1 (upgrade from 3.4.2) on one of my prod servers, and guess what?

    Yes, the very SAME error is displayed as with 3.5.0 and 3.6.0! This is getting to be a real comedy of errors now, and it isn’t funny!

    So, NO it isn’t RESOLVED, far from it.

    Rolled back to 3.4.2, and it works fine, no errors!

    • This reply was modified 1 year, 8 months ago by ttoaster.
    Thread Starter ttoaster

    (@ttoaster)

    Hi,

    3.6.1 doesn’t throw the error I reported with 3.5.0 and 3.6.0; however I have PHP 7.4 (not 8.0) so there are some other code changes in 3.6.1 than just the PHP 8.0 fix!

    I will do some more testing with this version on my dev servers before I update my prod servers, and see if there are any other issues.

    Thread Starter ttoaster

    (@ttoaster)

    This issue is still not fixed in 3.6.0, just updated from 3.4.2 and yet again I get the error email, and in it is the very same error message. Can you not fix this? I’m not the only one having this issue!

    Thread Starter ttoaster

    (@ttoaster)

    @edisonapps I used the Rollback plugin… but you can simply download the old version from the Plugin page and then re-install it manually, if you prefer…

    I never installed 3.5.0 on my Production site because of the issue I reported when testing it on my Dev server (which is a duplicate of the Prod server).

    Thread Starter ttoaster

    (@ttoaster)

    @edisonapps do like most of us that have had the issue, roll back to the previous version, or if you want a more reliable plugin look elsewhere…

    Otherwise, ditch Square and use Stripe instead; which I think I’m just about to do (ditch Square; I already use Stripe), as the level of support for this plugin is frankly unacceptable!

    Thread Starter ttoaster

    (@ttoaster)

    Hi,

    Yes, it is a staging/dev server that is a clone of my production server; I use this to test ALL new plugins and plugin updates before installing them on my production server.

    So, I have no need to create another staging server (or desire to do so). The old version of the plugin works, the new one throws an error (as reported). The issue is with your plugin code, not my server or the other plugins installed (no other plugins were updated when I installed your Square plugin update this morning), so it isn’t a conflict, unless you have added some conflicting code.

    Why not investigate (via Diffing) or your change system (code repository) what code has been changed/added related to the Configuration interface, and debug it? It isn’t rocket science!

Viewing 15 replies - 16 through 30 (of 158 total)