ashlyjohny

Hello @rudsonnunes ,

Thank you for reporting this.

We checked this on our end and, as far as our testing shows, Notiqoo does not impose any limit on the number of template variables that can be mapped. We tested templates containing 7–8 parameters and were able to assign all variables successfully without encountering the issue you described.

Based on our findings, the issue may be specific to your setup. One possibility is that one of the custom parameters is not being detected correctly or is not returning a valid value, which could cause the template mapping screen to incorrectly report a missing variable.

To help us investigate further, could you please provide the following:

1. A screenshot of your WhatsApp template as it appears in Meta/WhatsApp Manager, showing all variables used in the template.
2. A screenshot of the Notiqoo notification settings page where you are mapping the variables.
3. Any debug log errors generated when attempting to save or send the notification.
4. Details of any custom parameters or custom code being used for the template variables.

If possible, please create a temporary test site using TasteWP and reproduce the same issue there. Once the issue has been replicated, please share the temporary login credentials with us. We will check the issue directly on the TasteWP site, review the configuration, and investigate what is causing the problem so that we can provide accurate guidance and a suitable solution.

We noticed that you provided a fifth parameter is product names, which is likely causing the issue. Facebook only delivers message templates with valid parameters, and they recommend a maximum of four. Please also ensure that the product names are kept short.If possible share the custom paramater code that you created to get product names.

Once we receive the above information, we will be able to determine whether the issue is related to template configuration, custom parameters, or another factor within the site setup.

Thank you for your understanding, and we look forward to assisting you further.

• This reply was modified 2 days, 23 hours ago by ashlyjohny.
• This reply was modified 2 days, 23 hours ago by ashlyjohny.

Hi @karanzen,

Thank you for your reply.

I think there was a small misunderstanding.
Before, the woom_run() part was commented, and that was the issue.

Please replace the code in the same file from line 100 to 114 exactly with the code below:

if (!function_exists('woom_run')) {
    function woom_run()
    {

        $plugin = new Woom_Messaging();
        $plugin->run();
    }

    // if (
    //  function_exists('woom_run') &&
    //  in_array('woocommerce/woocommerce.php', apply_filters('active_plugins', get_option('active_plugins')))
    // ) 
    {
        woom_run();
    }
}

Please copy and replace it exactly as above, then save the file and check once again.

Hi @karanzen ,

Currently, the Notiqoo plugin does not support network-wide activation in WordPress Multisite. You need to either use it on a single-site installation or activate the plugin individually for each site in the multisite network.

You can find the plugin settings under:
WooCommerce → Settings → Notiqoo

Thank you!

Hello @ishanmail28,

Could you please share the screenshot for reference? It seems no screenshot was attached.

Hi @ishanmail28 ,

We haven’t heard back from you in the past 5 days, so we’re assuming the issue has been resolved. We’ll go ahead and close this thread for now.

If you still have any concerns or need further assistance, feel free to reach out by opening a new support request anytime.

Thanks!

Hi @ishanmail28 ,

Thank you for sharing the template details!

Could you let us know whether the two templates that were sent successfully had any parameters (variables like {{1}}, {{2}}, etc.), or were they plain static text templates with no variables?

This will help us narrow down the issue — if the successful templates had no parameters and the order_refund template does, the problem is likely with how the parameter values are being passed to the API for this specific template.

Also, could you please check for any errors in the debug log and in the WooCommerce status logs?
You can find this under: WooCommerce → Status → Logs. If you notice any errors there, kindly share them with us so we can investigate further.

Looking forward to your response!

Hello @tcmfood ,

This works slightly differently depending on the checkout type used on your WooCommerce site. There are two cases:

1. Block Checkout
   If you are using the Block Checkout, the billing phone number is not validated by default. You can make the field required and ask users to enter the phone number in international format (with + and country code).

However, WooCommerce currently does not provide support for custom validation for this field in the Block Checkout. We are waiting for an update from the WooCommerce side to enable this functionality. Once WooCommerce adds support for phone number validation in Block Checkout, we will immediately add support in our plugin as well.

2. Classic Checkout
   This works properly. The billing phone number must be entered in international format (+ with country code). If the format is incorrect, checkout will not proceed.

We have also provided a setting to disable our custom validation, so you can use other phone validation plugins if needed.

Hi @nimonogi ,

We have not received any updates regarding this issue for several days. Assuming that the issue has been resolved, we will proceed to close this ticket. If you encounter further issues, please feel free to create a new support thread.

Thank you!