Mehmet
Forum Replies Created
-
Hi @taojing10,
Thank you for reporting this. We’ve identified this as a known issue where the background migration process can stall and stop progressing.
This problem is often related to hosting resource limits. Before applying the fix below, we recommend checking the following with your hosting provider:
- PHP Memory Limit: Should be at least
256M. You can check this in Tools > Site Health > Info > Server. If it’s lower, ask your host to increase it or adddefine('WP_MEMORY_LIMIT', '256M');to yourwp-config.php. - PHP Max Execution Time: Should be at least
120seconds. Low values (30s) can cause the migration to time out silently. - WP-Cron: The migration relies on WordPress cron to keep running in the background. Some hosts disable WP-Cron or limit how often it fires. Check with your host that cron jobs are enabled. You can also ask them to set up a real server-side cron job for better reliability.
If after checking these settings the migration is still stuck, you can reset it with the following steps:
- Using your hosting’s file manager or FTP, navigate to
wp-content/ - Create a folder called
mu-pluginsif it doesn’t already exist - Create a new file inside it called
wp-statistics-reset-migration.php - Paste the following code into that file:
<?php
add_action('admin_init', function () {
global $wpdb;
$wpdb->query("DELETE FROM {$wpdb->options} WHERE option_name LIKE 'wp_statistics_update_visitors_source_channel_batch_%'");
$wpdb->query("DELETE FROM {$wpdb->options} WHERE option_name LIKE 'wp_statistics_visitor_columns_migrator_batch_%'");
delete_transient('wp_statistics_update_visitors_source_channel_process_lock');
delete_transient('wp_statistics_visitor_columns_migrator_process_lock');
delete_site_transient('wp_statistics_update_visitors_source_channel_process_lock');
delete_site_transient('wp_statistics_visitor_columns_migrator_process_lock');
delete_option('wp_statistics_update_visitors_source_channel_status');
delete_option('wp_statistics_visitor_columns_migrator_status');
$jobs = get_option('wp_statistics_jobs', []);
if (is_array($jobs)) {
unset($jobs['update_source_channel_process_initiated']);
unset($jobs['update_visitors_source_channel_total']);
unset($jobs['update_visitors_source_channel_processed']);
unset($jobs['visitor_columns_migrator_initiated']);
unset($jobs['visitor_columns_migrator_total']);
unset($jobs['visitor_columns_migrator_processed']);
update_option('wp_statistics_jobs', $jobs);
}
wp_clear_scheduled_hook('wp_statistics_update_visitors_source_channel_cron');
wp_clear_scheduled_hook('wp_statistics_visitor_columns_migrator_cron');
@unlink(__FILE__);
}, 1);
- Visit any page in your WordPress admin, the stuck notice should disappear and the file will delete itself automatically.
- remove
wp-statistics-reset-migration.phpafter that.
After the reset, once you’ve confirmed your hosting resources are adequate, the migration prompt may reappear on the Referrals page and you can re-trigger it.
We’ve escalated this matter to our development team and we will follow up with you once a permanent fix is available.
Please let us know if this resolves the issue for you.
Hi @taojing10,
Thank you for your patience and for taking the time to troubleshoot. We’ve looked into this further, and we believe this issue is addressed in the latest release, WP Statistics v14.16.1.
Could you please update to the latest version and check if the Historical Total Visitors and Views feature is working as expected? Specifically:
- After updating, try entering your historical values again and verify they are being added to the totals.
- Also try running the “Refresh Summary Totals” migration again to see if the error is resolved. If the issue persists after updating, please let us know and we’ll escalate this directly to the development team for a deeper investigation. Best regards
Best regards,
Hi @hirngesicht,
Just a quick follow-up, WP Statistics v14.16.1 has now been officially released and includes the fix for the Bypass Adblock issue when using WP Statistics as a MU-plugin on Bedrock.
Please update to the latest version and let us know if the issue is fully resolved on your end. If you run into any further problems, don’t hesitate to reach out.
Best regardsHi @taojing10,
Since we haven’t heard back from you, we’ll go ahead and mark this topic as resolved for now.
If you still need assistance, feel free to reopen this topic or create a new one and we’ll be happy to
help.Best regards
Hi @taojing10,
Since we haven’t heard back from you, we’ll go ahead and mark this topic as resolved for now.
If you still need assistance, feel free to reopen this topic or create a new one and we’ll be happy to
help.Best regards
Hi @valentinalisch,
Since we haven’t heard back from you, we’ll go ahead and mark this topic as resolved for now.
If you still need assistance, feel free to reopen this topic or create a new one and we’ll be happy to
help.Best regards
Hi @michelswiss,
Since we haven’t heard back from you, we’ll go ahead and mark this topic as resolved for now.
If you still need assistance or have any further questions, feel free to open a new topic and we’ll be
happy to help.Best regards
Hi @elmalak,
Since we haven’t heard back from you, we’ll go ahead and mark this topic as resolved for now.
If you still need assistance or have any further questions, feel free to open a new topic and we’ll be
happy to help.Best regards
Hi @picaruco,
Thanks for the kind words, glad you found the stats useful!
Let us know if you need anything else.Best regards,
Hi @elmalak,
Unfortunately, once WP Statistics is deactivated or removed, the data that wasn’t stored in the database is not recoverable, so the lost statistics can’t be restored.
To understand why the plugin was deactivated automatically, we’ll need more details from you (for example: server logs, error messages, recent updates to WordPress/plugins/themes, or any security plugins you’re using).
Please share more information so we can investigate the cause.
Thank you.
Hi @valentinalisch,
Thanks for reporting this! You’ve identified a known issue with WP Statistics and JavaScript-based navigation. There’s an active discussion on GitHub about this exact problem:https://github.com/wp-statistics/wp-statistics/issues/1019
The team is aware that the JS tracker doesn’t properly handle
history.pushStateevents. The page ID from the initial load gets stuck and used for all subsequent AJAX navigations.For now, the best workaround is to either:
- Disable JavaScript-based tracking in WP Statistics settings (rely on server-side only)
- If you’re comfortable with code, you can manually trigger a fresh tracking call after your AJAX navigation completes
The development team is working on a proper fix. I’d recommend subscribing to that GitHub issue for updates. Thanks for your patience and for using WP Statistics!
Hi Stephen,
Thank you so much for this wonderful review and for recommending our plugin 🙏
We’re really glad to hear that the Twilio gateway and Elementor integration have been helpful for your lead capture workflow.Your kind words about our support truly mean a lot to us and motivate us to keep improving.
If you ever need anything, we’re always here to help.
Best regards,
Hi @envolk,
Thank you very much for your kind words!
We’re really glad to hear you’re finding the plugin helpful and easy to use.We truly appreciate your support.
Best regards,
Hi Michel,
Thank you for reporting this.
The string “Stranica za prijavu” is not originally part of our plugin, as all default strings in the plugin are in English. Since this text is not English, it is most likely coming from a translation file or another plugin/theme.
I’d recommend first checking whether this string is associated with our plugin by scanning it with a plugin like Loco Translate. If it is linked to our plugin, it may have been translated incorrectly and can be corrected there. Otherwise, it’s likely coming from a different plugin or the active theme.
Please let us know what you find, and we’ll be happy to assist further if needed.
Best regards,
Hi Tim،
Thanks for your patience, and sorry for the delay in getting back to you, we really appreciate your understanding.
We’re currently in direct contact with the Textplode team and are waiting for an official update from their side. In the meantime, we’ve prepared a temporary solution so you can get things working again.
Please replace the current Textplode gateway with the version available in the following repository:
https://github.com/wp-sms/wp-sms/tree/release-17-0-x-update-textplode-gatewayThis version is compatible with the current plugin and should resolve the “Textplode class could not be found” error for now.
As soon as we receive an update or fix from Textplode, we’ll follow up and provide further guidance if needed. Thanks again for your patience, and don’t hesitate to let us know if you need any help applying the temporary fix.
Best regards,
- PHP Memory Limit: Should be at least