Problems with Email CoAuthor On Post

I just tested the plugin on 6.3.1 and it’s working without issue (and I updated the tested on part, so that should show up correctly shortly).

What error message are you getting?

Hi Denny, thankyou for you reply. The message are:

“email Author On Post” needs to be?configured?before it can be used. Please correct the configuration before having the plugin sending email.

Si è verificato un errore critico sul tuo sito web. Controlla la casella di posta dell’amministratore del sito per istruzioni.

I saw you posted an update online 38 minutes ago, thank you. But nothing has changed unfortunately: at the moment I installed it on a site other than the one where I have to install it, to avoid creating problems to the site.

The error that gives is a generic “critical error” that does not lead to the configuration of the plugin.

If you want I’ll give you access to the correct site so you can see too.

That message just indicates that the plugin just needs to be configured using the settings page. Once the settings are changes that message will go away. (That error message is just looking at the name and subject that are set. As soon as one of those is changed the message should go away.)

No Danny: The message asks you to configure the plugin, and that’s fine. Only if I click on the “configure” then it gives me critical error and does not make me do the configuration.

Ah. I wonder if that’s because your WordPress install is in /wp/ not in /. I’ll take a look and see if I can figure out why it isn’t presenting the correct link.

I don’t think that’s the problem: it’s true that the test installation I did under wp… but the official installation is done on the root directory of the site where I actually have to install the plugin: https://oblo.it
And it still doesn’t work.

That’s really strange. I assume that the link from the normal settings menu works fine? (Settings > Email CoAuthor On Post)

I checked the plugin code, and those are both using the exact same link, and when I test it on our test and live systems the link works as expected. Could there be a redirection plugin that’s catching the URL request and trying to redirect you to another URL which isn’t valid?

There are no redirects… and in the left menu there is only emailcoautor on post without other subheadings. The only way to run the configuration is the initial link, but as I said, it doesn’t work.
Do you want me to give you access to the site so you can see exactly what happens? Leave me your email that I send you the login details… if you want.

Uploaded a new release that fixes the issues.

Leave me your email that I send you the login details… if you want.

Please never do that again. People get banned from this site for accepting that.

@mrdenny

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.