fijisunshine

Hi Matthew,

Thank you for your reply. And thank you to the development team for looking into this.

However, I just upgraded to ver. 5.2.9 and the issue still exists. The Top Referring Domains section just says “No data to display”.

I’m been using ver. 5.0.4, which is the latest version without this issue. And ver. 5.0.4 continues to work well for me – it shows all the Top Referring Domains properly.

Would you mind forwarding this note to the development team? Thanks again

Thank you for your reply, Matthew. More debugging results for you:

The issue occurs with version 5.0.5 and later. The issue isn’t present in version 5.0.4 and older. With version 5.0.5, the Top Referring Domains section says “There has been a critical error on this website”. With version 5.0.5.1 and later, the Top Referring Domains section says “No data to display”.

The issue relates to the PREPARE statement on the sql command that generates the data in the Top Referring Domains section. This PREPARE was added in version 5.0.5.

From the version 5.0.5 code, here is the SQL statement from line 126 in wp-slimstat-reports.php for the Top Referring Domains section:

‘slim_p1_10’ => array(
‘title’ => (‘Top Referring Domains’, ‘wp-slimstat’), ‘callback’ => array(__CLASS, ‘raw_results_to_html’),
‘callback_args’ => array(
‘type’ => ‘top’,
‘columns’ => ‘REPLACE( SUBSTRING_INDEX( ( SUBSTRING_INDEX( ( SUBSTRING_INDEX( referer, “://”, -1 ) ), “/”, 1 ) ), “.”, -5 ), “www.”, “” )’,
‘as_column’ => ‘referer’,
‘filter_op’ => ‘contains’,
‘where’ => ‘referer NOT LIKE “%’ . str_replace(‘www.’, ”, parse_url(home_url(), PHP_URL_HOST)) . ‘%”‘,
‘raw’ => array(‘wp_slimstat_db’, ‘get_top’)
),
‘classes’ => array(‘normal’),
‘locations’ => array(‘slimview2’, ‘slimview5’, ‘dashboard’)

Here is the php error that I get when running version 5.0.5:

[26-Sep-2024 02:47:42 UTC] PHP Notice:? Function wpdb::prepare was called <strong>incorrectly</strong>. The query does not contain the correct number of placeholders (2) for the number of arguments passed (1). Please see <a href="https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.8.3.) in REDACTED/wp-includes/functions.php on line 6085

[26-Sep-2024 02:47:42 UTC] PHP Fatal error:? Uncaught TypeError: array_slice(): Argument #1 ($array) must be of type array, null given in REDACTED/wp-slimstat/admin/view/wp-slimstat-reports.php:990

Stack trace:

#0 REDACTED/wp-slimstat/admin/view/wp-slimstat-reports.php(990): array_slice(NULL, 0, '20')

#1 REDACTED/wp-slimstat/admin/view/wp-slimstat-reports.php(956): wp_slimstat_reports::raw_results_to_html(Array)

#2 REDACTED/wp-slimstat/admin/view/index.php(153): wp_slimstat_reports::callback_wrapper(Array)

#3 REDACTED/wp-slimstat/admin/index.php(710): include('REDACTED...')

#4 REDACTED/wp-includes/class-wp-hook.php(324): wp_slimstat_admin::wp_slimstat_include_view('')

#5 REDACTED/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)

#6 REDACTED/wp-includes/plugin.php(517): WP_Hook->do_action(Array)

#7 REDACTED/wp-admin/admin.php(259): do_action('admin_page_slim...')

#8 {main}

? thrown in REDACTED/wp-slimstat/admin/view/wp-slimstat-reports.php on line 990

Line 990 in wp-slimstat-reports.php in version 5.0.5 is here:

$results = array_slice(
$all_results,
wp_slimstat_db::$filters_normalized[‘misc’][‘start_from’],
wp_slimstat::$settings[‘rows_to_show’]
);

The root cause of the issue seems to be the PREPARE statement on the sql command not executing properly. As a result, $all_results on line 990 is null.

I did a plugin conflict test and I also did a theme conflict test – those didn’t solve the issue. For security reasons, I’d prefer not to publish Site Health > Info publicly. But I can publish it for you if absolutely necessary to solving this problem.

Any suggestions? Thanks again!

In addition to my prior message, another insight:

When Maintenance > SQL Debug is enabled:

All of the section, such as Top Countries and Top Cities, show a sql statement that’s executed to generate the content in that section. For example, in Top Cities, the sql statement is: SELECT city, COUNT(*) counthits FROM my_database_slim_stats WHERE city IS NOT NULL AND 1=1 AND dt BETWEEN 1726790400 AND 1726836006 GROUP BY city ORDER BY counthits DESC LIMIT 0, 1000

However, in the Top Referring Domains section, there’s no sql statement shown. This section continues to only say “No data to display”. The Top Referring Domains section is the only section that doesn’t display a sql statement.

It seems that no sql statement is being called in the code for the Top Referring Domains section. Any ideas why this would be?

Thank you the great suggestions, Matthew. There are no errors in browser console. Yes, there are correct entries in the referer column in the database. For example, Google searches appear as “https://www.google.com/”

On the Maintenance tab > Tracker Error, I see this error: [September 10, 2024 11:20 pm] 203 Malformed resource URL

This error seems is related to this SlimStat Analytics support ticket: https://www.ads-software.com/support/topic/tracker-error-203-malformed-resource-url/

Was Mostafa able to resolve this issue? Or any suggestions? Thanks again

Hi Matthew,

Thank you for your reply. Yes, I’m able to see the Top Referring Domains section. It’s empty but it shouldn’t be given the date range that I select (and knowing that visitors definitely came to the site via Google search during that date range). In fact, if I set the date range to the past 3 years, the Top Referring Domains section is still blank, which is impossible for this specific website. All the other sections, such as Top Countries and Top Screen Resolutions, are working great. The issue is only with the Top Referring Domains section. There are no errors or issues Tools > Site Health > Info.

Any suggestions? Thanks again

Thank you for your excellent reply. I followed your instructions and moved the two lines regarding WP_CACHE and WPCACHEHOME to /public_html/wp-config.php and that fixed the issue.

WP Super Cache works perfectly now! Thank you

P.S. Thank you for all of your work on NS Cloner.

Hi Takayuki,

Thanks for your reply. The site is on localhost so it’s not publicly available.

The textarea has two small lines in the bottom right corner, indicating that it should be resizable by the user. But it’s not actually resizable.

Any suggestions? Thanks again

Thank you, Mike. No issues so far using “600”.

If I find any issues, I’ll let you know.

Thanks again

Thank you, @shanedelierrr. The issue is now resolved.

When I loaded the Tools page, several file requests were getting 404 errors and they weren’t loading. I reset the permalinks on my site and then these 404 errors went away. Now the Tools work again.

Thanks again!

Thank you for your reply, Kharis. The issue is now resolved. It was a plugin conflict. For Sydney version 1.80 (and later), the other plugin had a css element that was causing the contents of the tables to be “float: left;” in the dashboard/admin area of the website.

To fix it: I used an add_action on ‘admin_head’ in functions.php of my child theme to include this css for the dashboard/admin area on the affected css selector: “float: none !important;”

Thanks again!

Thank you for your reply, Kharis. The issue is in the WordPress backend (i.e. admin), not the publicly viewable website.

In the WordPress backend/admin, click on Posts or Pages to view your Posts or Pages listed in a table. For example, for Pages, the column titles are “Title”, “Author”, “Date” and “Expires”. These column titles are spaced correctly. But the contents of the table (for example, the title and author of each page) do not align with the column titles. They’ve all collapsed to the left side of the table.

This issue occurs in version 1.80 (and all later versions) but not in version 1.79.

Thanks again

Perfect, thank you Kharis!

Thank you, Kharis. Your solution fixed the issue.

Hi Kharis,

Any suggestions on how to determine the root cause of this issue and resolve it?

I’m having trouble figuring out the cause.

Thanks again