emgb_520

Closing.

I figured it out. Thanks.

Hi, Matt.

Just wanted to check in here on this.

Thanks!

I have followed up with the plugin author directly from their website contact form. Hopefully I get a response.

Thanks!

I have reached out to the plugin author directly via personal website. Hopefully I get a response.

Thanks!

Thank you for the response, Matt.

I am unclear on your suggestion to use the “Reply To” field. Can you elaborate? According to the Mandrill settings, the “Reply To” email is where emails go for replies from the end user.

Thanks!

Anyone? Thanks!

Following up again. Thank you!

Hello – does anyone know the answer to this question?

Thank you!!

WOOHOO!! Thanks, Matt. I will be working on getting it updated on my client’s sites!

Do we know how long their review might take? I have this plugin on 20+ client sites and will be in a world of hurt with replacing it, if they do not re-add the plugin.

Thanks!

I sent an inquiry to [email protected] about this plugin author’s lack of response on this forum and asked about why the plugin was closed and if it will be back. This was their response to me:

While we understand the concern, our policy is to not disclose why plugins are closed to anyone save the developer for the first 60 days. After that time, the reason why a plugin is closed will be made public, but in vague terms (i.e. ‘Guideline Violation’ or ‘Security’).

We know this can be frustrating, especially with larger plugins, which we rarely close unless we feel there’s no alternative. In general, we advise giving it the 60 days before taking action. Many plugins are reopened shortly after being closed. But if a plugin does hit the 60 days, then either the developer has no intention of updating it, or the issue is beyond their capability to correct. At that point, we recommend finding an alternative/replacement.

There are cases where you will see ‘This closure is permanent’ and that is a sign the plugin will not be updated and should not be used. We try to limit those, as it’s not a great experience for anyone, but generally happens when a developer asks to close a plugin, or a developer is banned for repeat violations.

Again, we do understand why this is frustrating and vague, but we want to give the developers every reasonable chance to make corrections before publicizing why their work was closed, to help protect their reputations as much as we can.

————————-

This means we have to wait until 10.1.24 (since this plugin was removed on 7.31.24) to hear what is going on if the plugin has not been added back to the repo.

• This reply was modified 3 months, 2 weeks ago by emgb_520.

This is really important – can we please get a response?

Thanks!

I came here to ask this, also. I went to Matt Miller’s (developer) website and there is nothing related to support there. Can’t even navigate off of the home page.

I also need to know a replacement if the Mandrill plugin is no longer supported.

Thanks!

Hello – I was checking in to see if there was any additional information about when the update might get released. Thanks!