Dashboard broken

Resolved Grzegorz.Janoszka
(@grzegorzjanoszka)

8 years, 10 months ago

Recently I noticed that the dasboard is broken, the page is empty and the HTML code ends with:

<script type=”text/javascript”>
jQuery(document).ready(function(){
postboxes.add_postbox_toggles(pagenow);

jQuery(‘#wps_close_nag’).click( function(){
var data = {
‘action’: ‘wp_statistics_close_donation_nag’,
‘query’: ”,
};

jQuery.ajax({ url: ajaxurl,
type: ‘get’,
data: data,
datatype: ‘json’,
});

jQuery(‘#wps_nag’).hide();
});

});
</script>

When I go to see the referrers I see almost empty page and the HTML code ends with:

<div class=”wrap”>
<!– Screen icons are no longer used as of WordPress 3.8. –> <h2>Najlepsze odsłyłające strony</h2>
<ul class=”subsubsub”>
<li class=”all”>Wszystkie <span class=”count”>(235161)</span>

<div class=”postbox-container” id=”last-log”>
<div class=”metabox-holder”>
<div class=”meta-box-sortables”>
<div class=”postbox”>
<div class=”handlediv” title=”Kliknij, aby przełączyć”>
</div>
<h3 class=”hndle”><span>Najlepsze odsłyłające strony</span></h3>
<div class=”inside”>
<div class=’log-latest’>

I asked the colo company to show me the PHP errors, but I haven’t goet them yet. Once I have them I will post them here.

Thank you for your support!

https://wordpress.org/plugins/wp-statistics/

Viewing 15 replies - 1 through 15 (of 25 total)

1 2 →

Plugin Contributor Greg Ross
(@gregross)

8 years, 10 months ago

Most likely your running out of memory while generating the overview page.

To to the optimization page and see how much memory is being reported.

Thread Starter Grzegorz.Janoszka
(@grzegorzjanoszka)

8 years, 10 months ago

The PHP memory limit is 256M, PHP 5.6.10. Is it likely that I need more than 256M?

Plugin Contributor Greg Ross
(@gregross)

8 years, 10 months ago

Depends on how much data is being processed. The more history you keep the more memory that is required.

Thread Starter Grzegorz.Janoszka
(@grzegorzjanoszka)

8 years, 10 months ago

Greg, will the historical data be lost or just somehow aggregated?
I have just enabled the option to clean everything older than 365 days.
Will let you know if it helped.

Plugin Contributor Greg Ross
(@gregross)

8 years, 10 months ago

The total visitors/visits will be retained in the historical settings. Data about clients (like browser type and other data) will be deleted.

Thread Starter Grzegorz.Janoszka
(@grzegorzjanoszka)

8 years, 10 months ago

I am logging php errors and I see some errors from other plugins, but nothing gets logged from your plugin even if I try and try to display the broken pages.
I am mostly interested in UU’s. Do I understand correctly that I can delete all the data older than 100 days, but I will still have a correct UU count for the whole year?

Plugin Contributor Greg Ross
(@gregross)

8 years, 10 months ago

Take a look at the source code in your browser (usually ctl-U) and check for any “Fatal Error” lines on the broken pages.

If you delete anything over 100 days, your totals for the last 365 days will only reflect the 100 days of traffic. However if you look at the total hits on your site it will reflect the “correct” all time hits to your site.

Thread Starter Grzegorz.Janoszka
(@grzegorzjanoszka)

8 years, 10 months ago

Well, I caught some PHP errors from your plugin:

[25-Jun-2015 10:29:07 UTC] Błąd Table ‘682_paleosmak.statistics_historical’ doesn’t exist bazy danych WordPressa podczas wykonywania zapytania SHOW FULL COLUMNS FROM statistics_historical wysłanego przez do_action_ref_array, call_user_func_array, wp_statistics_dbmaint_event, wp_statistics_purge_data
[25-Jun-2015 10:29:07 UTC] Błąd Table ‘682_paleosmak.statistics_historical’ doesn’t exist bazy danych WordPressa podczas wykonywania zapytania SHOW FULL COLUMNS FROM statistics_historical wysłanego przez do_action_ref_array, call_user_func_array, wp_statistics_dbmaint_event, wp_statistics_purge_data

They seem to be only from the cron job, though.

If PHP is running out of memory while processing the data, shoudln’t it be reflected in the php error log? Because there was nothing about memory at all.

Plugin Contributor Greg Ross
(@gregross)

8 years, 10 months ago

Normally yes, you would see a memory error in the logs.

Plugin Contributor Greg Ross
(@gregross)

8 years, 10 months ago

Can you also use phpMyAdmin to check to see if your database has a ‘statistics_historical’ table in it?

Plugin Contributor Greg Ross
(@gregross)

8 years, 9 months ago

Closing due to inactivity.

Thread Starter Grzegorz.Janoszka
(@grzegorzjanoszka)

8 years, 9 months ago

Sorry for not replying. Your plugin has the following tables:

wp_statistics_exclusions
wp_statistics_historical
wp_statistics_pages
wp_statistics_useronline
wp_statistics_visit
wp_statistics_visitor

I still don’t see any PHP errors and I still see nothing in the dashboard.

Plugin Contributor Greg Ross
(@gregross)

8 years, 9 months ago

No problem, I found the bug that was causing the historical table to not be found, it will be fixed in the next release.

Can you tell me how many rows are in each of the above tables?

Thread Starter Grzegorz.Janoszka
(@grzegorzjanoszka)

8 years, 9 months ago

table | rows
wp_statistics_exclusions | 0
wp_statistics_historical | 0
wp_statistics_pages | 417
wp_statistics_useronline | 2
wp_statistics_visit | 367
wp_statistics_visitor | 220318

So it seems the table _historical is empty.

Thread Starter Grzegorz.Janoszka
(@grzegorzjanoszka)

8 years, 9 months ago

BtW, not sure if I am supposed to make another thread, but it seems I have found a small bug. I go to settings and then exclusions, I click on “Treat corrupt browser info as a bot:” to enable it, then save at the bottom. After I go to exclusions again, this option is not checked in. Not sure if the bug is in saving or just displaying, but please check it out.

Viewing 15 replies - 1 through 15 (of 25 total)

1 2 →

The topic ‘Dashboard broken’ is closed to new replies.