Lyyn

Perhaps it has something to do with varnish. Since my host installed that on his servers, my tweets aren’t downloading anymore. Not only tweets but all WP-Cron are broken, I think.

Any workaround?

I found the solution. I think it’s because my hoster has changed something with Apache, the variable $_SERVER[‘REMOTE_ADDR’] which is used for getting the IP of the visitor sent always “127.0.0.1” which is in exclusion list.

I had to use $_SERVER[‘HTTP_X_FORWARDED_FOR’] for getting the real IP.

So, in counterize.php, from around the line 1250, I changed this :

if( isset( $_SERVER['REMOTE_ADDR'] ) )
{
    $remoteaddr = apply_filters( 'counterize_server_remote_addr', $_SERVER['REMOTE_ADDR'] );
}

to this :

if( isset( $_SERVER['REMOTE_ADDR'] ) )
{
    if(isset($_SERVER['HTTP_X_FORWARDED_FOR'])) {
        // Fix
        $remoteaddr = apply_filters( 'counterize_server_remote_addr', $_SERVER['HTTP_X_FORWARDED_FOR'] );
    }
    else {
        $remoteaddr = apply_filters( 'counterize_server_remote_addr', $_SERVER['REMOTE_ADDR'] );
    }
    /*echo('<pre style="visibility: hidden;">');
    print_r($_SERVER);
    echo('</pre>');*/
}

It now works fine, but idk if this is viable.

k, sorry in advance, it’s going to be engrish more than english ??

Since the 24th november, my Counterize plugin doesn’t work : it doesn’t count anymore the visit for both bots and humans. I think it’s because of some plugin’s updates, but when I turn on the error’s display, it doesn’t show anything related to Counterize.

What I tried:
– Show the errors: as explained above, nothing seems to be linked with Counterize
– Refresh user-agent list: Nothing has changed
– Flush the database with the plugin’s tools: Nothing changed too.
– Add an entry manually with a SQL query : It works, Counterize shows my new entry.
– Deactivate the plugin, go on the blog and browse some pages, reactivate and rebrowse : Absolutely none new entry.

What can I do?

I have the same issue, I can’t add a custom author. I use “Better WP Security” which changes the prefix of the database, can it be the source of the issue?

WP v. 3.5.1 /// Plugin v. 1.5.4