Bugs. So. Many. Bugs.

  • Lee Peterson

    (@lpeterson23)


    6 years ago

    A critical bug in version 2.1.8 of WP-Stateless marks the very last straw for our team and our clients. We can no longer afford to drop everything we’re doing to troubleshoot why something that previously worked fine for many releases suddenly breaks without warning.

    From defined constants going unrecognized to site-wide banners displaying for absolutely no reason to the CDN bucket name becoming unset, breaking media uploads and front-end references, we’re truly disappointed with what appears to be a refined, well-polished media management solution introducing unexpected bugs with every patch release.

    Question: Since when does a patch release introduce new bugs and break existing functionality?
    Answer: When semantic versioning practices aren’t adhered to.

    Given a version number MAJOR.MINOR.PATCH, increment the:

    1. MAJOR version when you make incompatible API changes,
    2. MINOR version when you add functionality in a backwards-compatible manner, and
    3. PATCH version when you make backwards-compatible bug fixes.

    Version 2.1.6 introduced new constants, or, more precisely, replaced constants. This should have been reserved for a MAJOR version release, something considered as “incompatible API changes.”

    Version 2.1.4 introduced an updated version of Google OAuth, a change which broke new setups for our entire team. This should have been reserved for a MINOR version release, something considered “a backwards-compatible change”.

    Version 2.1.7 introduced a dashboard-wide notice for sites set to use Stateless mode, forcing file name rewriting even for users of the CDN mode. The banner meant for Stateless settings persisted even when unnecessary, causing confusion for all. This should have been reserved for a MAJOR version release, something considered as “incompatible API changes.”

    The list goes on. Fortunately for us, the list will no longer be something that causes our team to scramble or our account managers and directors to have uncomfortable discussions with multi-million-dollar clients and projects.

Viewing 1 replies (of 1 total)
  • technicalheadwear

    (@technicalheadwear)

    I’ve been thinking of ditching stateless too as I can’t afford to have issues with such a critical component.

    The only thing that has stopped me so far is that I don’t know what else to do.

    Won’t I run into the same issues with any other plugin?
    I’ve had a look at a plugin that enables the Imgix service but it’s also free.

    I wish Stateless had a subscription option that would give the team more time to focus on quality. The “free” option really spooks me. I’m not a fan of free if it comes to business tools.

    I hope that your post is a wake-up call for the developers. The plugin is too important to mess around with lightly.

Viewing 1 replies (of 1 total)
  • The topic ‘Bugs. So. Many. Bugs.’ is closed to new replies.