transom

Hi Mika, this is on Dreamhost’s side and it turns out that I spoke too soon. It worked for weeks then about a week ago – stopped working. Worked yesterday and now today – not working. This is all on the dili server and homiemail-sub4 servers. All while I haven’t touched the plugin or settings on my side.

Ok – apparently this was a host issue. Things have returned to normal with no changes on my part. So that the good news. The bad news is that I haven’t been able to find out what changed at Dreamhost to make it not work and then work.

Thanks for the prompt responses. I am going to persue with my web host to see if something broke there and/or tackle breakpointing the pop3 class to see if I can get some more info on why it fails.

I’ll update the thread if I find something conclusive.

Tried both from my laptop as well as using ssh into wp server to try from there.

I am interested that the pop3 class doesn’t return an actual error message. Is there somewhere that I can change the “timeout” (I did notice that the authentication took a moment from my laptop and no time at all from the server).

Yes – even tried changing the password. I know the new password works. Tested via telnet as well as webmail interface.

I know there are lots of variables here. I would appreciate any tips on debugging.

Actually – the variable $has_ut is created in another function using
$has_ut = function_exists('user_trailingslashit');

Since $has_ut is only used on line 567 in yoast_get_paged of All_in_One_SEO_Pack, it might be better to use this:
if (function_exists('user_trailingslashit'))

Working with a client today, I found a javascript bug in scripts.js that kept another plugin from working in the backend.

It was reporting:
Uncaught TypeError: Property ‘$’ of object [object Window] is not a function
The issue is with:
var $ = jQuery.noConflict();
$(document).ready(function(){

a better way to do this (and fixes the issue)
jQuery(document).ready(function($){

If only I was a regular Git user, but yes I’ll do this in a day or so.

Here is a link to Github gist that appears to do that:
https://gist.github.com/2142009

And the article that explains the gist https://buddydev.com/buddypress/exclude-users-from-members-directory-on-a-buddypress-based-social-network/

YMMV

Another classic way for this to happen is that one of the plugins/themes has a character at the end of the file (after the ?> tag)

Start with switching the theme to the default. If the problem goes away, search your preferred theme for a “f” that has fallen in your html.

If that is unsuccessful, turn off all your plugins. Turn them on one at a time to see if you can find the culprit.

Once you have found the responsible plugin, you may find it easier to just install a fresh copy to see if that solves the problem.

You are mixing two concepts.

You will need to tell WordPress which category you want on the front page. There are several ways to do this.
This plugin is probably the easiest.
https://www.ads-software.com/extend/plugins/frontpage-manager/

If you change back to the default theme, Twenty Eleven, does the admin bar return?

If so, you are doing something wrong in your custom theme.

If not, turn off all plugins and see if the admin bar re-appears. If it does, turn on plugins one at a time until you find the culprit.

The only “odd” thing that I see is the query_posts – what happens if you comment that out?

Based on the code pasted – there really isn’t a reason to re-do the query. Paging should be already handled.

You might also want to reset your Permalinks. Go to Settings -> Permalinks. Change to default, SAVE, and then back to your preferred setting.

A quick search of
https://www.ads-software.com/extend/plugins for a term such as “approve members”
yields plugins like:
https://www.ads-software.com/extend/plugins/maven-member/

— (just need to unsubscribe the thread)