stat with no path

Hi @werdpres

I have no idea how this can happen at the moment.

Can you check your database and there your statify table for entries with an empty target? And check the markup of this line?

Maybe there is a page with special characters and is not correctly escaped, or something like this (displaying error).

Thanks!

All the best
Torsten

hi Torsten

there are thousands of rows with empty targets, though they appear to be a rather small % of the total number

here’s an example…

https://i.postimg.cc/s2SKctDV/Y-09-14-23h-23m-40s.png

…i’ll guess that the above info is probably of little use in figuring out what the problem is – i also wonder if these thousands of rows without targets isn’t pointing to a larger problem ???

dunno if this helps, but the character set defined in wp-config is define('DB_CHARSET', 'utf8mb4');

pretty sure this was ‘utf8’ by default, but i changed it for reasons i don’t remember, other than it was to solve a problem

that charset matches almost all of the db tables, except for the ‘statify’ table which is ‘latin1_swedish_ci’

Hi @werdpres

i’ll guess that the above info is probably of little use in figuring out what the problem is

Yes, but it reveals at least one information. The target is already lost before saving to the database.

dunno if this helps, but the character set defined in wp-config is define(‘DB_CHARSET’, ‘utf8mb4’);

It is not relevant. WordPress is using utf8mb4 if the MySQL on your server is supporting it and it is using utf8 if it is not supporting it. So it doesn’t matter if you have utf8mb4 or utf8 in your wp-config.php.

that charset matches almost all of the db tables, except for the ‘statify’ table which is ‘latin1_swedish_ci’

This seems to be the default charset. Maybe we should set this explicitly. I am not sure if this can cause this bug.

Are you using the javascript tracking? Or any minification tools? Maybe the JS link is broken or the parameters are stripped for some reason …

As we are just reading those parameters from our own request.

All the best
Torsten

> Are you using the javascript tracking?

i had been using a caching plug and i experimented with the JS tracking option on and off and it didn’t seem to make a difference – currently i’m not using the caching plug and the JS option is off

> Or any minification tools?

Fast Velocity Minify

> Maybe the JS link is broken or the parameters are stripped for some reason …

i use Clearfy and i disable REST API Links, XML-RPC, jQuery Migrate

see my reply above, but i also had another question…

i assume there’s not way to recover the ‘target’ value for the rows containing an empty value, therefore, is it ok/should i delete these rows?

Hi @werdpres

Clearfy has an option to remove query strings. If this is turned on, it would strip target and source info in our request.

As the info is not written to the database there is nothing to recover. So yes, you can delete those rows.

All the best
Torsten

i went through Clearfy settings at least TWICE because i was certain it had an option to strip query strings … and i missed it twice ??

the reason i disabled them is because there is apparently a consensus that they are bad for SEO – if you agree, then i might suggest implementing an alternative method of passing this data if possible

questions…

1. when does Statify use query strings – when the JS opt. is enabled, disabled, or both?

2. Clearfy has 2 options: “Remove Version from Script” and “Remove Version from Stylesheet” – which one needs to be disabled?