Changed from free to paid

  • I updated my plugins and suddenly my web has no cookie consent because a free plugin became 100% paid plugin. Hu-manity, you should change your brand name to Capi-talism.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author dFactory

    (@dfactory)

    Unfortunatelly, it’s not true.

    The plugin didn’t became 100% paid, it’s just an option you can use if you think you need it. The UI/UX issues in the plugin onboarding could make you feel that way, but this will be addressed in a bufix release of the plugin, in a day or two.

    • This reply was modified 3 years, 9 months ago by dFactory.
    Thread Starter jemmerich

    (@jemmerich)

    Sorry, but I tested it throughly and there was nothing in the console from cookie notice. But the cookie from analytics was running good even if I had it well configured (before version 2.0) that it could not run without consent.

    Plugin Author dFactory

    (@dfactory)

    If your compliance status is Pending, there could be an issue like this indeed.
    We’ve fixed it already and releasing in the next version of the plugin today/tomorrow.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Changed from free to paid’ is closed to new replies.