Thanks for updating, should make sure the plugin page reflects that (3 posts)

  1. lrivers
    Posted 3 years ago #

    Thanks for fixing the XSS vulnerability. I feel safer already. That said, you should update the link info and the date of revision on the plugin info page. The plugin home page link does not resolve and the revision date is still April.



  2. Jeremy Clarke
    Posted 3 years ago #

    It's possible the update was done by someone in core WordPress rather than the main developer, I think this happens sometimes when there is a security issue in a popular plugin because it's better to fix it than wait for the developer to show up. In that case it would make sense that they didn't update compatibility because if the plugin author is absent then it's good that the plugin page makes it look abandoned.

    In fact the plugin author's personal site is completely offline, which is not a good sign. It might be time to fork or give up on this plugin unfortunately :S

  3. BlaenkDenum
    Posted 3 years ago #

    I made the update actually, after being contacted by a core member.

    However, you are right. If anyone is interested in taking up development of this plugin I will be glad to give you access to the repositories, preferably someone who is familiar with the intricate differences between the WP, WP-MS, and maybe even WPMU APIs.

    Otherwise I guess you can give this plugin a try.

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic