• It looks like they have removed features from the free version and put them into the paid version in an attempt to coerce free users to pay for the premium version.

    Even worse, some features listed on the page for the free version are not really available in the free version. You have to pay for them.

    I think this “bait and switch” practice is bad business.

    We used to recommend this plugin highly.

    We strongly recommend you avoid this plugin and others by this company due to their misleading business practices.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Malay Ladu

    (@malayladu)

    Hi,

    Sorry but we never meat that or forced people to pay.

    Yes, we have premium plans and those who want premium feature they need to pay it.

    Free version of ES also works very well.

    The working of “User Roles” have changed and because of it we have put into Premium plan.

    Our intention was to provide security by default (in free version) and if people want flexibility, they can upgrade to premium and get access to settings.

    Hope that helps.

    Thread Starter Sonja London

    (@summit)

    Forcing users to use the Administrator role just to send an email is dangerous. It does exactly the opposite of “provide security by default”. If this were attached to another role, like an editor or even a capability like “es_send_email”, rather than a role, I would have applauded you and made changes.

    • This reply was modified 4 years, 11 months ago by Sonja London.
    Thread Starter Sonja London

    (@summit)

    “Yes, we have premium plans and those who want premium feature they need to pay it.”

    I have no objection to that. To be clear – my objection is the “bait and switch” – removing features from the free version and putting them in the paid version. In the retail industry in the US, “bait and switch” is illegal. Sadly, that law does not appear to apply here.

    • This reply was modified 4 years, 11 months ago by Sonja London.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Removing features to force users to pay for them’ is closed to new replies.