We've tested EasyRecipe recipe literally thousands and thousands of times against hundreds of different themes and loads of other plugins.  There's over 15,000 sites actively using the plugin, so we're pretty confident that it works.

Well, confident that it works in 99% of blogs.  Unfortunately for plugin developers, pretty much every single WordPress blog is unique. Even two blogs that share the same theme and plugin set present different environments for plugins, unless one is literally a clone of the other.

What this means for us as developers is that from time to time we come across a blog environment that presents us with problems we've never seen before.  Sometimes it's just that a theme or another plugin does something that we never anticipated and planned for. However more often than not, it's that the theme or another plugin has a bug or doesn't follow the WordPress standards and it breaks EasyRecipe.  Often the bug doesn't have any effect on the blog - other than to stop EasyRecipe from functioning as it should.

In these cases, it can be extremely difficult for us to find the root cause from a distance. Usually a description of the failure gives us no insight as to what's actually happening behind the scenes and if the problem occurs on the admin side, a description is all we have. However, we can usually get a much better idea of the problem if we can observe what actually happens onscreen when the error occurs.

So sometimes we'll ask for an admin login to a customer's blog.

When we do login, we are scrupulously careful not to make any changes at all without explicit permission.  Most times we don't need to change anything on the blog anyway, we just need to watch what's going on when the error occurs.

How to give us a login

The best way to do this is to create a new user with administration rights and a strong password for us to use.  Then when we've resolved the problem, you can delete the user.