Woocommerce-admin: [4.9.0-RC.1] Notice shown when RazorPay is installed from task list

[vedanshujain]

Describe the bug
If you install RazorPay and set the keys in via task list after completing OBW, looks like title and description properties are not set. This causes notices during the whole site. See screenshot:

To Reproduce
Steps to reproduce the behavior:

1. Install RazorPay via tasklist
2. Set razor pay keys during the task list setup.
3. Visit the frontend, you will see those notices

Expected behavior
No notices.

Desktop (please complete the following information):

• OS: [e.g. iOS] macOS Big Sur
• Browser [e.g. chrome, safari] Safari
• Version [e.g. 22] 14.0.1

Additional context
Root cause looks like title and description setting options are not set via task list.

[juliaamosova]

This issue is a duplicate of https://github.com/woocommerce/woocommerce-admin/issues/5963 where @moon0326 already did some investigation.

[moon0326]

@juliaamosova The layout part is duplicate (empty space), but I think the error message is new. I will test out the error message and work in this issue if I can reproduce it.

[juliaamosova]

Thanks @moon0326!

[moon0326]

I was able to reproduce it locally. I opened a PR in Razorpay github as this should be handled in the plugin.

[timmyc]

@pmcpinto @MechielCouvaras - we have encountered a few issues with the Razorpay gateway plugin during testing of 4.9 - do we have a contact there we can escalate these issues to?

[pmcpinto]

I don't have a contact and Mechiel is afk this week. Probably we'll need to wait until he comes back next Monday.

[moon0326]

The PR has been approved by Razorpay. I also left a comment for the release date.

[isaumya]

@timmyc You can mention all the issues that you have faced either mention them here or provide the respective issue IDs and I can forward the thinks to the Razorpay Senior Management and Product Managers to look at those issues with priority.
Hope this helps. 😃

Also thank you @moon0326 for your PR, Razorpay has recently released a new version of their WooCommerce plugin with the patch you have mentioned in the PR. Have you checked it?

[moon0326]

@isaumya Sure thing! Yup, the latest version (2.6.0) fixed the problem.

[timmyc]

Excellent, since the fix has been released in the plugin, I think it is safe to close out this issue now.