I’d like to know the answer as well.
As a precaution, I deleted the plugin but the author bios persist.
This is not encouraging.
I’ve cleared all caches — maybe it’s a network cache issue?
Clearing the caches and rebooting solved the persistence issue *phew*!
What do you recommend as a replacement?
I remember going through a bunch of plugins before I settled on StarBox, which worked intuitively and quickly. 🙁
Hi,
The plugin is temporary closed because we didn’t made updates lately. I don’t know if this is fair but I hope that it will be back online soon.
Thanks for the feedback
Calin
It’s the first time I heard that reason, but it doesn’t seems to be very likely, because there are a lot of plugins that haven’t been updated for many (6-8) years, that are still available.
It’s more likely, that your plugin has been reported because of a security issue and the admins have hidden it to avoid making more victims during the investigation.
When something is removed, shouldn’t there be a reason stated by WordPress?
To the owner: yes (and they do)
To the public: no, because vulnerabilities should be fixed before disclosing them.
@calinvingan
I’d like to know that too.
Should we disable the plugin temporarily, is there a security hole that needs fixing?
Any ETA when it’s coming back?
The problem is that we haven’t received any notice from a WP.org rep. Otherwise we would have immediately fixed any problems.
1) We didn’t receive a notice that there is something to fix
2) We haven’t received a notice that it was taken down. Luckily a couple of users emailed us about this and that’s how we found out.
I’d also like to know what’s up. This has been completely out of the blue.
You should contact plugins@wordpress.org to ask what’s going on and why you didn’t receive a notification.
Thanks for the email, Jos. We’re going to investigate and then write an answer here once we ourselves know more.
The plugin team always emails authors about problems, and this is no exception. We did send an email and have not received a response.
We received another email just now regarding this issue, and I have replied to it, forwarding along the original email as well.
I’m writing this message in order to confirm that the plugins team is indeed sending emails, but we don’t control whether or not you receive them. If you do not receive our response, you may contact me directly at otto at wordpress dot org, and I will attempt to use an alternate means of communication with you.
Samuel, do you know what was the reason that the plugin was pulled off by the repository though?
Yes, I do. It’s not a serious concern. Relax. 🙂
I’m glad it’s not a security reason and so now I can re-enable the plugin.
