Lee Rickler

Update to sort this out.

Update to the latest and all your dreams will be restored!
Kudos to Yoast for listening and fixing!

Happened here in a few places – for me, the main error was admin redirect.
Instead of the usual domain.com/wp-admin I was getting domain.com/domain.com/wp-admin – which obviously gave a 404

Seems we all jumped to blame 3.3.1 update!
Well, I’ve learned something at least.

Yup. Just found out here as well.
Tried on 2 different machines both on 3.3.1 and both tried in twentyten and custom themes.

Scrub the above – now works fine for me.

Post excerpts work fine.
Pages don’t have excerpts, by default, but they do if you add the following to your functions:

add_post_type_support( 'page', 'excerpt' );

New project and I totally forgot to add it!

Can you get access to the original database?
Try looking at your accounts CPanel or speak to your host about PHPMyAdmin access – you can then change the admin email and password.

Once you have that check the ‘lost password’ works and change it.

Or for a more comprehensive plugin, try this one.

No, I don’t have an answer so I wondering what you did (hence the ‘resolved?’).

BUT, essentially the only way I can think of is to turn your machine into a webserver and grant the client temp access.
There’s various ways you could possibly do this depending on your set-up plus someone with more/ better knowledge than me might even come up with an actual method.

Resolved? How so?

No. I’m talking about the SEO link embedded itself into the admin bar.

Easiest way to remove is to put this in your theme functions file:

function my_admin_head() {
    echo '<style>li#wp-admin-bar-wpseo-menu.menupop { display:none; visibility:hidden }</style>';
}
add_action('admin_head', 'my_admin_head');

I does look like it’s sorted now.
At least, it’s working on my live and local test sites.

I get the above error on a live site but not on a local set-up – both using 3.3 rc1.

If the issues stress you then I would report them to the plugin developer and they can take recommended action and issue and update.

Works fine here in Chrome and Firefox.

Yet another lesson learned by me, although I can’t see the point of using it in the CSS, in this instance.

Many thanks though.