Mehmet

Hello @haribonda,

Thank you for taking the time to share your detailed feedback with us. I’m genuinely sorry to hear that your experience with the plugin and our support process didn’t meet your expectations.

I want to address the points you raised:

Email Communication Issue:
I sincerely apologize that your email ended up in spam and wasn’t responded to promptly. This is absolutely not the experience we want our customers to have, and I’m sorry you had to reach out via Twitter to get a response. We’ve processed your refund as per our 14-day money-back guarantee, and I’m glad that was resolved.

WhatsApp Cloud API & OTP Functionality:
You’re absolutely right about the challenges with WhatsApp Business Cloud API Authentication templates. This is an area we’re actively working to improve. The Meta API parameter handling, especially for templates with buttons, has been a known challenge that we’re addressing with our development team.

Regarding the phone number prompt flow you mentioned – this is valuable feedback. The scenario where users don’t have phone numbers stored is indeed a real-world use case that should be handled more gracefully, and we’ll take this into consideration for future improvements.

Documentation:
Your feedback about clearer documentation for WhatsApp Authentication templates is well taken. We recognize that this is an area where we need to provide better guidance and examples.

Your feedback is genuinely valuable to us, and we’ll use it to improve both the product and our support process. I’m sorry we couldn’t deliver the solution you needed for your specific use case, but I appreciate you giving us a try and taking the time to provide this constructive feedback.

If you ever decide to try our products again in the future, I hope we can provide you with a better experience.

Best regards,

• This reply was modified 5 months, 1 week ago by Mehmet.

Hello @haribonda,

Thank you so much for taking the time to test this code example and share the working solution with us! This is incredibly helpful.

We really appreciate you providing a verified code snippet that addresses the URL button parameter issue. This will definitely help other users who might encounter the same challenge with WhatsApp templates.

Thanks again for your contribution and for being part of the community!

Best regards,

Hello there,

Thank you for the detailed information.

The WP-SMS WhatsApp Cloud gateway currently doesn’t support button component parameters. It only handles body text variables and header media attachments, which is why Meta returns the error about missing button parameters.

Recommended Solutions:

Option 1: Use COPY_CODE Button Template (Best for OTP)

Create an authentication template in Meta Business Manager with a COPY_CODE button instead of a URL button. This type works with the plugin because Meta handles the button automatically; you only need to pass the OTP code in the body parameter.

Option 2: Simple Text Template (Easiest)

Create a text-only template without buttons:

Your OTP code is {{1}}. Valid for 10 minutes.

Option 3: Custom Code (Advanced)

If you need URL buttons, you can use the wp_sms_request_params filter hook to add button parameters manually. This requires adding custom PHP code to your theme’s functions.php file.

add_filter('wp_sms_request_params', function($params) {
    // Only modify WhatsApp Cloud API requests
    if (isset($params['body'])) {
        $body = json_decode($params['body'], true);
        
        // Check if this is a WhatsApp template message
        if (isset($body['template']) && isset($body['template']['components'])) {
            
            // Add button component for URL button parameter
            $body['template']['components'][] = [
                'type' => 'button',
                'sub_type' => 'url',
                'index' => '0',
                'parameters' => [
                    [
                        'type' => 'text',
                        'text' => '' // Add your dynamic URL suffix here if needed
                    ]
                ]
            ];
            
            // Re-encode the modified body
            $params['body'] = json_encode($body);
        }
    }
    
    return $params;
}, 10, 1);

You can also submit a feature request here: WP-SMS Feature Request

I suggest trying Option 1 or 2 first. Let me know which approach you’d like to use, and I’m happy to provide more specific guidance!

Best regards,

Hello @pfm,

Thank you for reporting this! I’ve investigated and found that these Google Fonts (including the broken Roboto URL) are not being loaded by WP-Statistics.

The “Analytics by WP Statistics” comment in your page source appears just before the fonts, but they’re actually being added by a different source, most likely:

• Your WordPress theme (Twenty Twenty-Five, Twenty Twenty-Four, etc.)
• A caching/optimization plugin (like Autoptimize, LiteSpeed Cache, etc.)
• WordPress Core’s font optimization feature

To identify the exact source, try temporarily deactivating your caching/optimization plugins or switching to a default theme to see if the fonts disappear.

Once you identify the source, you should be able to disable Google Fonts from that plugin/theme’s settings and use local fonts instead.

Let me know what you find, and I’m happy to help further!

Best regards,
Mehmet

Hello Ricky,

Thank you for reaching out, and I’m happy to help! Your lifetime data is still available in WP Statistics; it’s just accessed a bit differently now.

Here’s how to view your complete historical data:

1. Go to Statistics → Visitor Insights
2. Click on the Overview tab
3. Click on the date picker in the top area (top left corner)
4. Select “Custom Range” and set your desired start date (e.g., the date your blog started) through today
5. The chart below will display all your data for that period with all the information you need

Additionally, if you’d like to export your complete data for analysis or backup, you can go to Statistics → Optimization → Data Export to access all your historical records.

Your data hasn’t been deleted, it’s all still there! The Traffic Summary widget simply shows quick preset ranges, but the full history remains accessible through the custom date picker.

Please let me know if this solves the problem or if you have any other questions!

Best regards,
Mehmet

Hello there,

Thank you for reaching out, and your English is perfectly clear! No worries at all.

You’ve identified a known issue. The PV graph filtering behavior changed in the recent versions, and you’re correct that in version 5.0.10.2 it displayed only the filtered referrer data, while in 5.3.4 it shows only the total PV graph.

We are aware of this issue, and the good news is that it will be fixed in a big upcoming update that addresses this and several other improvements.

Thank you for your patience and for taking the time to report this. We appreciate it!

If you have any other questions, please don’t hesitate to ask.

Best regards,

Hello @dxylott54,

Thank you for reaching out and for being proactive about your site’s security!

Regarding CVE-2025-14151 (Stored XSS vulnerability in the outbound_resource parameter):

• Affected versions: 5.3.2 and earlier
• Fixed in: Version 5.3.4

To secure your site, please update Slimstat Analytics to version 5.3.4 (the latest version). This update resolves the vulnerability completely.

If you need further assistance or have any other questions, please don’t hesitate to ask. I’m happy to help!

Best regards,