ubergeeke

Ah, missed some of the MailChimp settings. Got it figured out.

I added the code This time, I got no errors, and no upvote button when not logged in. Success!

Then I logged in, and I *still* can’t see the upvote button, so it’s not working. Suggestions? Should I remove the spaces around the period in the following line and see if that works?

$content = $content . thumbs_rating_getlink();

Reverted back to this, which restored site to previous state.

function thumbs_rating_print($content)
{
return $content.thumbs_rating_getlink();
}
add_filter(‘the_content’, ‘thumbs_rating_print’);

Because that code block just hosed the whole site.

What’s that extra . for on the “$content .= thumbs_rating_getlink(); ” line? Can’t remember ever seeing something like that before.

Ah, right! Just reviewed the installation instructions.

Ok, I added this code block to the end of functions.php:

function thumbs_rating_print($content)
{
return $content.thumbs_rating_getlink();
}
add_filter(‘the_content’, ‘thumbs_rating_print’);

Other than that, I added this code block to my themes Custom CSS section, both to change the color AND to get rid of the thumbs down (I only want users to vote up, not down):

.thumbs-rating-down{
display: none !important;
}

.thumbs-rating-container .thumbs-rating-up {
background: #CC181E!important;
}

OVERALL GOAL: for only logged in users to up-vote posts. (Not pages, not any other kind of content, just posts; and only logged-in users.)

I didn’t. I only installed the plugin but made no code mods except for Custom CSS to remove down-vote, as directed by you last week.

Additionally, I have searched high and low, and can’t find a fix for this on the web. What this tells me is that my search terms are probably vague and incorrect (though “wordpress mu posts alphabetical” seems pretty clear to me).

Is there really no fix without a plugin?

I’ve done systems and network administration for about fifteen years. A friend needed a favor…which led to me being in the deep end of the PHP pool.

I’ve been a WordPress user for about three years, but haven’t had to tweak much on the back end since it works so well out-of-the-box. Inheriting a significantly-modified implementation has been…interesting.

No, comment emails aren’t working either. And neither is our “contact us” form.

I’m a bit confused about what to do/try next. Add function.mail.php to the root directory? Enable a particular setting within a specific PHP file? Comb my existing phpmailer.php and forget-password.php files for settings that might work?

And thanks again for responding.

(cough.) I *am* the tech. And evidently, I now need to know how to *enable* the mail() function.

Ah-hah! Things to try! Nothing makes this geek happier than actual to-do steps!

Ok, went to https://www.mysite.com/wp-login.php

Clicked on “Forgot password” link. Here’s path of link:
https://www.mysite.com/wp-login.php?action=lostpassword

Received this error:

The e-mail could not be sent.
Possible reason: your host may have disabled the mail() function…

Sidenote continued: upgrade scheduled!

I will also happily email you the site address. (In fact, will do so immediately.) Needless to say, since it requires updating, I don’t want to post the URL here as a big fat invitation.

Thanks for responding. It’s *very* much appreciated.

On the blog’s home page, there’s a “sign in” link, which when clicked leads to a pop-up (actually, a “slide down” more than a “pop up”) login window. Just below the username and password fields is a “Forgot password” link, which when clicked leads to a pop-up (slide down) window asking for an email address.

This box is the one that’s broken, I think. No matter what email address is entered, the text turns red and nothing else happens. I’m not sure if this is something that is a default WordPress setting, or a customized interface from the vendor who built the site. (Did I mention I inherited its management?)

At this point, we’re manually resetting user passwords. What I’d like to do is somehow fix this “forgot password” function. Furthermore, I’m not sure what could be interfering – though it makes sense that it must be a plugin or some back-end config. Perhaps I should take a look at some of the PHP files associated with logins? If so, which ones?

Sidenote: A manual update means considerable downtime, though you’re right that it must be done. I may need to wait a couple of months for a lag – we’re in a peak season at the moment and a manual update will require several instance synchronization steps in our cloud config which would translate to hours down rather than just minutes. (Hopefully that makes sense.)