HeliR

here is the solution, mybe add some css selecotr in addition, I just added the lines

  if($single->post_status=="private"):
       $info .=" private";
    endif;

Line 395 – lcatdisplayer

  private function get_post_link($single, $text, $class = null){
    $info = '<a>ID) . '" title="' . wptexturize($single->post_title) . '"';

    if ( !empty($this->params['link_target']) ):
      $info .= ' target="' . $this->params['link_target'] . '"';
    endif;

    if ( !empty($class ) ):
      $info .= ' class="' . $class . '"';
    endif;

    $info .= '>' . $text . '</a>';
    
  if($single->post_status=="private"):
       $info .=" private";
    endif;

    return $info;
  }

• This reply was modified 5 years, 7 months ago by HeliR.
• This reply was modified 5 years, 7 months ago by HeliR.

I use your precious plugin since about 4 years on my single side blog and i can ensure you that 90 pages run on blog_id=0,

1300 posts have blog_id=1

I traced it today by putting “automatic output on page / post” in the top10 settings.

It outputted the real hits.

I could later trace it to some SQL-selection bug in top10 that I documented in a support post

In addition I suggest you to have a look at this shortcode I posted here, it allows you to view the page-hits (counted by topten) with a shortcode in the footer or sidebar or within the post without messing in the source of the theme.

My single-site-blog has about 1200 active posts plus about 60 pages.

in wp_top_ten:
I find about 90 entries with blog_ID=0, partially double posts, mostly only cntaccess=1 but some old ones (low postnumber) with higher hitnumbers

picture of blog_ID=0 with higher hitnumbers

the other 1200 entries in wp_top_10 have blog_ID=1

So it cant be just a recent bug.

I have no idea why some of this (old) posts are counted with 2 different blog_IDs

I don’t understand the logic behind blog_ID selector here on my single-site WP installation, as it does not separate private / public / pages / posts,
it counts posts double long ago and now – this is definitly some bug.

Another Picture showing very old post being counted double with blog_id=1 and blog_id=0

I am not skilled enough but I guess I have to clean out the double entries, consolidate them to blog-id=1 (add up double counting) and put every posts/page blog_ID to 1, am I right?

Mybe you can create some SQL-Statement that does that for us, I guess we are 100000 Users, it takes 1-2h, so you could save the planet a tremendous amount of energy if you clean this problem with some code.

here is another screencut of the database with some double counted recent posts showing the problem

found it:

go into database, search for “post_per”

then you find an entry in the table “wp_user_meta”
whose meta_value = edit_post_per_page

Now edit this value and put it down to a decent value, e.g. 30 or 50 – voila, the post edit admin page is here again

umeta_id user_id meta_key meta_value
87 3 edit_post_per_page 50

I needed the line DirectoryIndex index.php, this line disappeared in my htaccess without my doing (plugin?)

# BEGIN WordPress
DirectoryIndex index.php
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

some redirection plugin seemed to have messed / changed my .htaccess

I have the DirectoryIndex default off, and have to turn it on. Without directoryIndex index.php the search function does not work. This line did disappear in my htaccess without my influence and search stopped working

# BEGIN WordPress
DirectoryIndex index.php
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

SOLVED the error with is_writeable with following solution found in www.ads-software.com

To solve that do following:
add following line in wp-config.php

<strong>define('WP_TEMP_DIR', ini_get('upload_tmp_dir'));</strong>

Daniel told us on his homepage (https://backwpup.com/blog/) that he is now using
* Uses now ‘WP_TEMP_DIR’ for getting temp folder

in above blog-entry we see that WP_TEMP_DIR is basically undefined in WordPress, so we have to set it, so Daniel, you better use the above solution to save you from such reports.

The CRON Error is still present in DASHBOARD

tx, Heli