chrisguitarguy

Well, I don’t think it was related to this plugin. It writes no htaccess files.

That’s the plugin error message, yes. It shouldn’t have locked you out without failed login attempts.

Do you see a WordPress screen? Or do you see a server error page?

This plugin never generates the message “you don’t have permission to access /wp-login.php on this server”

> I think it could benefit from some explanation

Yes. It’s on the list!

> maybe some shortcut buttons and/or radio buttons to “enable and disable” each line

robots.txt files are their own complete package. Learning how to write one is a prerequisite for using the plugin.

> and moving it to it’s own menu entry

A page with a single field? Seems to make more sense with other stuff.

Should be back to working in 3.5 and 3.6 now with 1.1

Yep! Just updated.

> I believe I left the User-agent:* Disallow:/wp-admin/ and Disallow /wp-includes/ on the file.

No, that doesn’t do anything that would block you from the admin area.

Other plugins you have installed? What theme are you using? It’s likely just a strange interaction or some such.

You can “emergency disable” a plugin by FTP’ing into your site and renaming the plugin folder.

the CSS class auto-link is added to all links in 0.9.1

You can modify that programmatically with the seoal_link_class filter:

<?php
add_filter('seaol_link_class', function($cls) {
    $cls = 'my-custom-class';
    return $cls;
});

Should be fixed in 0.9.1

Well, I’ll keep playing around with it to see if I can get it to happen again.

If you do stumble upon something, can you post it here?

For now I’m going to mark this as resolved.

I like this idea, and will look into it!

It probably has to do with where the word appeared. Did it happen on all posts or just the one?

Does it happen with just maintenance by itself with no other keywords?

I’m assuming you have the phrase “contact us” somewhere in text of your posts/pages?

Did you check the boxes on the right side for which posts types to target?

Can you post some of the HTML that’s giving you trouble so I can test against it?

There’s probably no way around the conflicts with the contact form, short of building a complete HTML parser into the thing (probably not a great idea). So you’ll likely just have to do <!–nolinks–> on those pages.

They are case insensitive now.

You would like them to be case sensitive? On a link by link basis?

-CD