• Night

    (@nightw0lv)


    Broke my website on production after update because shortcodes stopped working, the developers do not test their codes and that is the worst for a plugin to have.

    Since yesterday it is reported and today no update.

    • This topic was modified 1 month ago by Night.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Verdi Heinz

    (@ver3)

    Hi @nightw0lv

    We’re looking into this and appreciate your patience. As a small team, we work hard to provide the best possible product—including the free version you’re using.

    It would really help if you could share issues like this in the right place, where our developers actively monitor and respond: WordPress Support Forum.

    Leaving a review like this before we’ve had a chance to help creates a misleading impression and takes time away from solving the issue. We’d truly appreciate it if you’d consider removing your review for now and sharing your experience after we’ve worked through it together. An honest review means the world to us—but we’d love it to be based on the final outcome, not just the frustration in the moment.

    Thanks for understanding! Looking forward to resolving this with you. ??

    Plugin Contributor Verdi Heinz

    (@ver3)

    @nightw0lv Have you read my message?

    Thread Starter Night

    (@nightw0lv)

    Yes I did read the message, and decided to ignore it, I removed the plugin because there was no:

    1. Update from your team about the incident
    2. Update on the plugin for 3+ days
    3. Test before release
    4. Working together? you did not for 2 days give me any reply I had to waste 2 hours figuring out by clients why things are missing and not working. – lesson learned.

    Your plugin in might work now or later, but if your untested releases break peoples websites does not deserve 1 but 0, everyone can give untested releases but a good developer tests his code before release. – no I do not trust you to do that.

    Plugin Author Shea Bunge

    (@bungeshea)

    We’re really sorry about this @nightw0lv, and the delay on getting a fix out. The bug you mention should be fixed now in version 3.6.8.

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