• Resolved ituk

    (@ituk)


    “This plugin was closed”? for what reason? is it not safe to use?
    Thanks,
    Itamar

Viewing 15 replies - 16 through 30 (of 30 total)
  • mihdan

    (@mihdan)

    We have added WordPress 5 support to the plugin and are waiting for confirmation from the WordPress team to give us the right to manage the plugin. I see no reason to submit it back to wp repository.

    Plugin Support Michael Nelson

    (@mnelson4)

    Thanks for the update @mihdan. But I think before we put the plugin back on www.ads-software.com, we need to bring it back in line with the plugin guidelines (I believe it was removed due to guideline violations). I’ve done that to the best of my ability my fork. (FYI I sent you a separate email to try to cooperate on YARPP, rather than duplicate each other’s work or have separate forks.)

    @ituk, thanks for the encouragement. Before any version gets back on www.ads-software.com it would be best if it got tested. Could you try https://github.com/mnelson4/yet-another-related-posts-plugin/archive/master.zip, preferably on a test site, to make sure the YARPP Basic functionality still works?

    Thread Starter ituk

    (@ituk)

    @mnelson4 I’ve installed your version and it’s working properly so far. I’ve even installed it on my live environment.

    @mihdan and @mnelson4, I don’t know if you two are really up to it, but it would definetly be wonderful if you could cooperate on this one. It’d be quite silly to have more than one YARPP.

    Thanks,
    Keep us updated!

    Plugin Support Michael Nelson

    (@mnelson4)

    Thanks @ituk, that’s great news.
    I emailed the WordPress plugin review team to find out the status of YARPP. They said they actually haven’t heard from @mihdan (so maybe you talked with someone else?) but they said there are actually copyright issues around having someone new adopt YARPP.

    Mika Epstein said:

    Due to the nature of the sale of that plugin, we can’t give it to anyone. Basically the copyright is convoluted ??

    Anyway, sadly, we CANNOT allow that plugin to be adopted. You would need to get permission from YAARP.com for that.

    So, if we are to fork it and put it on www.ads-software.com, it will need a new name (suggestions? I thought “not another related posts plugin!”, or NARPP) and unfortunately YARPP users won’t automatically update to it, tgeyllneed to deactivate YARPP and then install and activate NARPP.

    Plugin Support Michael Nelson

    (@mnelson4)

    Oh, and I found a good article detailing the history of YARPP and it’s sale: https://letswp.io/what-happened-yarpp-yet-another-related-posts-plugin/

    Plugin Support Michael Nelson

    (@mnelson4)

    Another interesting development: if we put a fork of YARPP on wp.org, the WP plugin review team would like to rename things from “YARPP” as much as possible, but are understanding that can’t be done throughout while maintaining compatibility with existing integrations.

    pamps

    (@pamps)

    Hi,

    I am using YARPP on my sites. For what I understand it is not about safe and updated, right?
    It is an issue concerning “name ou copyright”… not a security issue, correct?

    Thanks!

    pamps

    (@pamps)

    Hi again,

    I am also try to install the last fork but after that YARPP says:

    “Consider Titles” and “Consider Bodies” are currently disabled…
    YARPP’s “consider titles” and “consider bodies” relatedness criteria require your wp_posts table to use the MyISAM enginefulltext indexing feature. Unfortunately your table seems to be using the InnoDB engine… ALTER…

    Well, if somehow WP put that table as InnoDB engine I dont want to change on an running site.

    Seems YARPP has more issues to correct… I suppose.

    Regards.

    Plugin Support Michael Nelson

    (@mnelson4)

    Hi @pamps

    For what I understand it is not about safe and updated, right?

    The version of YARPP on www.ads-software.com isn’t being maintained, and was removed because it violated several of the www.ads-software.com plugin guidelines. But it wasn’t removed because of a security problem. To my knowledge, there are no security vulnerabilities in it (otherwise that would have been the first thing to get fixed in my fork).

    Regarding that notice suggesting to change the database engine to MyISAM, would you mind if we discuss that on a separate topic? It’s a good issue to discuss, but I don’t want to hijack ituk’s original topic.

    Plugin Support Michael Nelson

    (@mnelson4)

    Actually @pamps I created a GitHub issue to discuss the database engine issue: https://github.com/mnelson4/yet-another-related-posts-plugin/issues/3

    pamps

    (@pamps)

    Hi @mnelson4,

    Many thanks for the support!

    Plugin Author YARPP

    (@jeffparker)

    YARPP is not closed. After a bit of a hiatus, YARPP will come back with a bang! Stay tuned. ??

    this is great news

    that’s great news.

    Vielen Dank! Super Plugin!

Viewing 15 replies - 16 through 30 (of 30 total)
  • The topic ‘Is the plugin closed permanently?’ is closed to new replies.