thellwig

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 25 total)
  • Thread Starter thellwig

    (@thellwig)

    I did have W3-Total-Cache enabled, so I deleted that plugin from the Plugins folder (I couldn’t actually disable it since the Network section is inaccessible). However, that didn’t seem to change anything.

    Thread Starter thellwig

    (@thellwig)

    Hmm, I followed the steps in that link, and found a few more occurrences of olddomain.com that I replaced. There are now no more references to any form of olddomain.com in the database. I had already updated the .htaccess and wp-config.php files the first time around, so nothing to change there.

    The Network Page problem still persists unchanged. Any other ideas?

    Thread Starter thellwig

    (@thellwig)

    I went into the DB and changed all references from https://olddomain.com to https://newdomain.com
    I found a website that listed all the locations in the DB tables that the domain name occurred in.

    I thought maybe I missed some, but I doubt that would affect it, as if that were the case, I’d at least still be seeing the old domain name in the links to the Network page, right?

    Ok, I actually solved it pretty quickly, but I still have no idea how my file got infected.

    For anyone else having this problem, here’s how to fix it. Notice how the link to 91.196.216.64/s.php located between two other scripts? Open up the script that is referenced right before this one.
    For example, in Boe’s situation, you would open up the jQuery script file. (In my case it was in the Tipsy script file.) Go all the way to the bottom of that file, and you’ll see a line of code that looks like this: https://pastebin.com/XxxbPFUy (yes, it’s a really long line. That was the code I found in mine).
    DELETE THAT LINE!

    Once you’ve done that, reload your site and the link in the header will be gone.

    So that’s how to remove it, but I don’t know how to keep it from coming back. Any insight into what caused this would be helpful.

    I wonder if this is coincidental or not, but I’m in Rolesville, NC, yes, right next to Wake Forest, and I just had the same script show up in my WordPress site too.
    It’s in the <head></head> tag surrounded on either side by other legitimate scripts.

    If anyone finds out where the problem is and how to fix it, I’ll be much obliged!

    Timothy

    Mike, this is probably way too late for you, but for anyone else who encounters your problem as I just have, here’s how to fix it:

    In your code, find the line that is fetching the comments. It will look similar to this:
    $comments = get_comments("post_id=$post_id");

    Now, right after this line, before you actually do anything with the comments, add this line:
    $comments = ecf_getComments( $comments, $post_id );

    Just one note here, in the second block of code, the second parameter $post_id is a variable that I previously defined in my code. You will have to change that in your code to reflect whatever the id of your actual post is.

    If you’re inside The Loop, that’s easy enough. If not, here’s the code that I used to get the ID for the current post outside of The Loop:

    global $wp_query;
$post_id = $wp_query->post->ID;

    Hope this helps someone.

    Fantastic. Thank you so much!

    I’m working on the same problem and will let you know if I solve it. If you have solved this already, could you let me know what you did?

    Thanks!

    W3 Total Cache can be kept running on your installation without breaking the comment rating plugin. All you have to do to eliminate any possible intereference is disable all javascript compression/combination/minification.

    yohay, I’ve had my caching system ‘weird up’ a lot of things. Have you checked the SQL db table to see if the ratings are being saved but not displayed?

    Oh, and what caching system are you using? I was having major problems with W3 Total Cache breaking most javascript code when ever I tried to minify/combine the javascript files.

    jss, thanks for the fix. It’s great!

    Just to clarify though, most of it is unnecessary.
    All you need is the first line:

    date_default_timezone_set('America/Los_Angeles');

    Just paste that in wpf.class.php after the first <?php and that will work.

    You don’t need the

    $script_tz = date_default_timezone_get();

if (strcmp($script_tz, ini_get('date.timezone'))){
    echo 'Script timezone differs from ini-set timezone.';
} else {
    echo 'Script timezone and ini-set timezone match.';
}
    thellwig

    (@thellwig)

    Ok, I solved half of my own problem by adding the wp_footer() function to my footer…oops.

    But, I’d still like to know that error means that gemboy posted and what I can do to fix it.

    Any thoughts?

    thellwig

    (@thellwig)

    I got this same error and the actual plugin isn’t working for me on 3.0.1
    The thumbs up/down icons will appear on the page but when I click them nothing happens. The data never even makes it to the database as the commentrating table stays empty.

    Can someone more knowledgeable give me a hand in resolving this?
    Much appreciated!

    Let me add that though this plugin says it’s only good up through 2.9, it works fine on 3.0.1

    I understand that is is frustrating, but I honestly don’t know what else to do to solve your problem. I’ve installed and written custom code for this plugin on two different sites and both times it’s worked like a dream. I’m really sorry Mike. ??
    Maybe someone else more knowledgeable will stumble across this thread and point out something we’ve both been missing…

Viewing 15 replies - 1 through 15 (of 25 total)