Mehmet

Hi @programmin,

Thanks for your message.

The error is due to the missing type column in the wp_statistics_pages table.

Before making any changes, please make sure to back up your database.

Then, try running this SQL command:

ALTER TABLE wp_statistics_pages ADD COLUMN type varchar(180) NOT NULL;

The database optimization tools are now under:
Statistics > Optimization > Data Cleanup
This section handles tasks like removing old records, visitor data, user agents, and more.

To help us understand why this happened, we’d appreciate if you could share:

• Your Site Health Info
• When the issue started
• Whether the site was migrated, cloned, or updated recently

Looking forward to your reply.

Best,
Mehmet

Hello @cdserveopro,

Thank you for reaching out.

If I understand correctly, you are referring to embedding statistical data into your Divi pages using shortcodes.

WP Statistics does support shortcodes, which allow you to display various statistics directly on your pages or posts.

You can refer to our documentation here for more details:
https://wp-statistics.com/resources/shortcodes/

For example, to display the total number of visitors, you can use this shortcode:

[wpstatistics stat=visitors time=total]

Regarding your second question about generating CSV files automatically:
Currently, WP Statistics does not automatically generate and email CSV reports.

However, we do offer an add-on called Advanced Reporting, which allows you to receive statistical reports in PDF format.

Additionally, you can manually export your statistics data in CSV, XML, or TSV format by going to:
Statistics > Optimization > Data Export

Let us know if you have any further questions or need help setting things up.

Best regards,
Mehmet

Hi @rdtardif,

Thank you for your detailed message and for the additional context regarding the site migration.

It seems that the issue may be related to a missing column in the database.

Could you please try running the following SQL command in your database?

ALTER TABLE wp_statistics_pages ADD COLUMN type varchar(180) NOT NULL;

It appears that, for some reason, this column is not currently present in your database.

Before proceeding, we strongly recommend creating a full backup of your database.

Please let us know once you’ve done this or if you run into any issues.

Looking forward to your update.
Best regards,
Mehmet

Dear @programmin,

Thank you for opening the thread!

The error you’re seeing ({“code”:”not_found_meta_box”,”message”:”Invalid MetaBox Name in Request.”}) is occurring because the MetaBox functionality has been deprecated in version 14.12 of WP Statistics.

Recommended Solution:

Use the new methods provided by WP Statistics to retrieve hits data:

// Using the Hits class directly
$hits = WP_STATISTICS\Hits::record();

If you need to maintain the same API endpoint structure, you can create a custom endpoint in your theme’s functions.php:

add_action('rest_api_init', function () {
     register_rest_route('wp-statistics/v2', '/metabox', array(
         'methods' => 'GET',
         'callback' => 'custom_metabox_callback',
         'permission_callback' => function () {
            return current_user_can('manage_options');
         }
     ));
 });

 function custom_metabox_callback($request) {
     $name = $request->get_param('name');
     if ($name === 'hits') {
         $hits = WP_STATISTICS\Hits::record();
         return rest_ensure_response($hits);
     }
     return new WP_REST_Response(array('code' => 'not_found_meta_box', 'message' => 'Invalid MetaBox Name in Request.'), 400);
   }

Let us know if you need any further assistance!

Regards,
Mehmet

• This reply was modified 1 year, 1 month ago by Mehmet.

Hello @cooperator_jr,

Thank you for your update.
We are pleased to hear that the latest version is working correctly on your end.
We will now proceed to close this ticket as resolved.

Best regards,
Mehmet

Hi @the5krunner,

Thank you for reaching out and sharing this issue with us.

The query you’ve mentioned is part of the visitor migration process within WP Statistics.

It is expected to run temporarily as part of data handling and optimization routines.

However, if it is running continuously and causing high CPU usage, this might indicate an unexpected behavior or a specific condition on your site.

To help us investigate further, could you please provide any relevant log entries or server error logs related to this process?

We’ll be happy to look into this and assist you further.

Best regards,
Mehmet

Dear @tarikozaslan,

Thank you again for your patience and for reporting the issue.

I’m following up to let you know that this warning has been resolved in version 5.2.11, released on April 25, 2025.

Please update your WP SlimStat plugin to the latest version to apply the fix.

Let us know if you experience any further issues or have any questions.

Best regards,
Mehmet

Hi @kmsh1,

The issue you experienced has been resolved in version 5.2.13.

Please update to the latest version and let us know if the problem persists.

Best regards,
Mehmet