• Resolved marcopolo11

    (@marcopolo11)


    Dear Team,

    We website is running on the latest version of woocom and wordpress with your plugin, many users have reported “critical error” after payment, while looking upt he logs, your plugins name came too often, the problem disappers when we disable the plugin.

    We reported this problem to our payment gateway (razorpay) and they also pin-pointed your plugin’s name to cause the error.

    Could you please look into this and have this addressed?

    2022-08-25T06:26:53+00:00 CRITICAL Uncaught Error: Call to undefined function attribute_slug_to_title() in /home/u707151460/domains/durvient.com/public_html/wp-content/plugins/woo-razorpay/includes/support/cartbounty.php:286
    Stack trace:
    #0 /home/u707151460/domains/durvient.com/public_html/wp-content/plugins/woo-razorpay/includes/support/cartbounty.php(191): readCartCB('14693')
    #1 /home/u707151460/domains/durvient.com/public_html/wp-content/plugins/woo-razorpay/woo-razorpay.php(1536): handleCBRecoveredOrder('14693')
    #2 /home/u707151460/domains/durvient.com/public_html/wp-content/plugins/woo-razorpay/woo-razorpay.php(1402): WC_Razorpay->updateOrder(Object(Automattic\WooCommerce\Admin\Overrides\Order), true, '', 'pay_K9laQOjswl3...', NULL)
    #3 /home/u707151460/domains/durvient.com/public_html/wp-includes/class-wp-hook.php(307): WC_Razorpay->check_razorpay_response('')
    #4 /home/u707151460/domains/durvient.com/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)
    #5 /home/u707151460/domains/durvient.com/public_html/wp-in in /home/u707151460/domains/durvient.com/public_html/wp-content/plugins/woo-razorpay/includes/support/cartbounty.php on line 286

    The page I need help with: [log in to see the link]

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Contributor Nauriskolats

    (@nauriskolats)

    Hi @marcopolo11

    Thanks for letting us know.
    We will look into this to see of this is caused by CartBounty and how to solve it if we come to find it is caused by our product.

    Right now, looking at the log files, what we see is that payment gateway plugin Razorpay has actually added some sort of a file inside their plugin called cartbounty.php and the file is located in the plugin folder here: plugins/woo-razorpay/includes/support/cartbounty.php
    And this file is using a function called attribute_slug_to_title() which at that moment does not exist so there should be a check at the end of Razorpay if they are using in their file this function if it exists or not. If this function does not exist, it should not be used there.

    It would be good if somebody from Razorpay support could join this thread to provide some additional inside as to why there is a file called cartbounty.php in their plugin files and what is the reason for it / what it does.

    Thread Starter marcopolo11

    (@marcopolo11)

    Thank you very much @nauriskolats, we have flagged the matter to the razorpay and have asked them to join this thread.

    Razorpay mentioned that they had received similar complaints from their other customers which is why they asked us to deactivate cartbounty (and 1 more plugin) on our website.

    @ramprak – Kindly join this thread and assist.

    Thread Starter marcopolo11

    (@marcopolo11)

    @razorpay – Kindly join this thread.

    Plugin Contributor Nauriskolats

    (@nauriskolats)

    Great, thank you @marcopolo11
    Would really like to learn more about the function that is used in the file, reasoning behind it and to help resolve this either on our end or Razorpay’s ??

    Plugin Contributor Nauriskolats

    (@nauriskolats)

    Ok, I have done a bit of work already and it seems I might have found the reason it is getting an error. I downloaded Razorpay plugin and checked the file inside plugins/woo-razorpay/includes/support/cartbounty.php file.

    So the issue seems to be that this line here:
    $productAttributes = attribute_slug_to_title($singleVariation->get_variation_attributes());

    Is missing Class definition in front of the function. It should be written like so to resolve it:

    $cartbountyPublic = new CartBounty_Public(CARTBOUNTY_PLUGIN_NAME_SLUG, CARTBOUNTY_VERSION_NUMBER);
    $productAttributes = $cartbountyPublic->attribute_slug_to_title($singleVariation->get_variation_attributes());
    Thread Starter marcopolo11

    (@marcopolo11)

    Thanks @nauriskolats , still waiting for @razorpay @ramprak to respond, I will share your update with them when I have a call with their developers today.

    @marcopolo11

    Thanks for reporting this issue. We are working on the fix. The new version of the razorpay woocommerce plugin will be released with this fix.

    Regards,
    Chetan

    Plugin Contributor Nauriskolats

    (@nauriskolats)

    Excellent, happy to hear that this will be fixed in the nearest future ??
    Thank you @marcopolo11 for bringing attention to this and @chetangn for adding integration improvement!

    Best wishes,
    Nauris

    We released the new version with the bug fix. @marcopolo11 please update the plugin to the latest version 4.2.0 and let us know the issue is resolved or not.

    Regards,
    Chetan

    Plugin Contributor Nauriskolats

    (@nauriskolats)

    Thank you very much @chetangn for such a quick release and update!

    Thread Starter marcopolo11

    (@marcopolo11)

    Thank you @chetangn , updated to the latest version.

    @nauriskolats hope you won’t mind keeping this issue open for a couple of days while I verify the issue resolved. Would you be able to inspect if razorpay has fixed the php file you had mentioned earlier?

    Plugin Contributor Nauriskolats

    (@nauriskolats)

    Hi @marcopolo11, I’m afraid I’m unable to validate if the issue has been resolved by actually running the code since I do not have Razorpay account, however I checked the code and the issue seems to be resolved now ??

    Thread Starter marcopolo11

    (@marcopolo11)

    Thanks @nauriskolats , I will keep monitoring the logs and will flag it if cartbounty’s name come up (I don’t think it will).

    Appreciate @nauriskolats and @razorpay @chetangn prompt action on this matter. Kudos to all of you.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Cartbounty breaking the checkout/thank you page’ is closed to new replies.