Reiner030

Especially from security sight – why don’t you upgrade your setup to 5.x ?
I our case we stay behind a firewall so 4.9.10 is fine till one open plugin is compatible with 5.x version.

Was finding this plugin while searching howto cleanup the growed up tables wp_stream and wp_stream_meta for staging system.

Hello Rolf,

I don’t think that it can still be done by webinterface ??
My search how you do the cleanup found this query:

// DELETE POSTMETA ORPHANS
                       $sql = sprintf ("
                       SELECT '%s' AS site,
                               <code>post_id</code> AS ID,
                               'meta' AS type,
                               '' AS post_title,
                               '' AS post_modified,<code>meta_key</code>, <code>meta_value</code>
                         FROM %spostmeta
                        WHERE post_id NOT IN (SELECT ID FROM %sposts)
                        ORDER BY <code>meta_key</code>
                       ", $prefix, $prefix, $prefix);

So I shortened it to check only count of orphaned post metadata; it also takes very long to quere the count while uncached:

# time mysql ALL_staging_landing_pages -e 'SELECT COUNT(*) FROM wp_postmeta WHERE post_id NOT IN (SELECT ID FROM wp_posts);'
+----------+
| COUNT(*) |
+----------+
|   458809 |
+----------+

real    0m21.260s
user    0m0.012s
sys     0m0.008s

Thats the intention to have some summary only before cleanup. But perhaps it’s only of interest if enough people are requesting for this ??
Our developer has to check then on staging system if the deletion is unproblematic (which I think so).

(The pages/trash count is so high because there is an automatic update task setup every minute for multiple languages each which pushes new/updated/deleted pages to WordPress instance for a long time.)

“EDIT” – some 0 missing:
* Chrome tab is crashing after around 300.000 items listed.

Same problem is also complained by detectify and they offer this solution for it with examples:

https://support.detectify.com/customer/portal/articles/1969819-login-csrf

The site is connected — ‘WP-Piwik 1.0.5 is successfully connected to Piwik 2.15.0. You are running WordPress 4.3.1.’ — and not generating any statistics.

… and do you see requests to piwik in your apache/nginx log when you access your site which belong to piwik tracking URLs ?

Ah interesting… ?? To complete:
Ghostery (Firefox, Chrome and for more browser available) normally checks / counts the advertising only.
But you can also setup the plugin/addon to block such requests.

Hi,

one common reason not mentioned in this thread (which was for me the cause):
You could have enabled in your browser the “don’t track” me option…
So piwik code would be shown and called but not counted if you setup piwik to recognize and handle this header.

For this case i love the addon/plugin “Ghostery” which exists for Firefox, Chrome, Opera and I think also more browser which shows you from which services you get tracked on sites.

weird, now its working fine…
Perhaps there was some wrong content in PHPSession stored or so.

But thanks for your support.

Reiner

Hello David,

yes… I use LastPass, so everytime the same correct password is used.
Is there some way so that I can debug / log the check for you ?

Bests

Reiner

… accidently double posted …

@av8nlvr
I “missed” informations in this problem to… but after only 1+ hour problem analytics I found in the FAQ:

https://yoast.com/wordpress/plugins/seo/faq/#my-sitemap-index-is-giving-a-404-error-what-should-i-do

=> WHY ISN’T THIS INFORMATION LINKED in the Admin Backend of this plugin?

I first thought that there is a problem in combination with WPML like in this thread:
https://wpml.org/forums/topic/wpml-yoast-sitemap-problem/#post-375509

=> @support: please check this because you have a buggy URL there produced:

The sitemap header moved from:
<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="//my.test.domain/main-sitemap.xsl"?>
to:
<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="WPSEO_FRONT_URLcss/xml-sitemap.xsl"?>