Support » Plugin: YARPP - Yet Another Related Posts Plugin » No custom related and abuse when deactivating

  • The plugin does not allow per post config. Also it is not posible manually set related posts for a post. But this is not a real problem, it just do not have the specs i need. The problem came when i tried to deactivate the plugin. I got an abusive screen, asking for the reason to deactivate. There is no way to deactivate without feedback. There is a list of deactivating reasons, I tried 80% of this options, and I got a message: visit our forums. Finally i could deactivate when clicked ‘others’.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Michael Nelson

    (@mnelson4)

    Sorry to hear you weren’t happy with the features, and had a hard time deactivating the plugin.

    As with other plugins, the deactivation survey is actually optional, but it sounds like it wasn’t clear enough to you that that was the case. I think you missed the button saying “Skip & Deactivate” (probably because once you select a feedback option it changes to “Submit & Deactivate” and usually asks for some explanation.)

    We’ll talk about what can be done to make that more intuitive.

    By the way, we’re working on allowing you to manually set related posts, but it would be helpful to know what other configurations you’d like to set per-post.

    Anyways, best wishes finding a plugin that suits your needs @holoduke99 !

    Can you clarify that your plugin has a step *before* being deactivated, and after clicking 8deactivate* ?
    if so I’d say hijacking the expected WP process is reason enough for a poor rating. Food for thought.

    Plugin Author Michael Nelson

    (@mnelson4)

    Yes when you click “deactivate” there is a pop-up asking for feedback, which you can skip by clicking “skip and deactivate”. It’s actually quite common among plugins over the past few years, but still yes it does seem to lead to a few upset users. Your input is noted @reelism, thanks.

    As is your consideration 🙂

    Reasons why someone deactivates a plugin should be optional. Offer a Skip button.
    That means you are kindly asking for a reason so you better understand the problem someone is having with your plugin, not forcing them. They don’t work for you as testers.

    Plugin Author yarpp

    (@jeffparker)

    @nosaint We 100% agree. Feedback is completely optional and there is a skip button available to skip it entirely.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this review.