Unreliable

  • I operate a large blog that uses WordPress as a headless CMS with a Next.JS frontend, which is largely enabled by this plugin. Let me just say first that creating an entire alternative third-party data API is an ambitious undertaking and I appreciate all the work the authors have put into it.

    But as a developer I have to throw out a word of caution that this plugin often has major bugs that can have critical impact on your production website. For example after a recent minor update we discovered a bug where any URL with a special character in it started returning a 404, causing several of our pages to suddenly become unavailable to users and delisted from Google, and this went on for many months before we realized it.

    There have been many similar instances. My general approach is to lean more on WordPress’s REST API over time which is more reliable since it’s maintained by the WordPress team, and only use WPGraphQL when it’s necessary.

    Also recommend turning off auto-updates and test your website extremely thoroughly after any upgrade.

    • This topic was modified 1 year, 5 months ago by benknight.
    • This topic was modified 1 year, 5 months ago by benknight.
Viewing 1 replies (of 1 total)
  • Plugin Author Jason Bahl

    (@jasonbahl)

    Hey Ben!

    Thanks for the critical review. I’m so sorry for the inconvenience the bug(s) have caused you.

    I just checked the issues and I don’t believe you brought this to our attention. It’s a bit difficult to help correct an issue if the issue isn’t shared with us.

    We’ve been pretty good at responding to your issues when you raise them: https://github.com/wp-graphql/wp-graphql/issues?q=is%3Aissue+author%3Abenknight.

    Would have loved to have the chance to work with you on this!

    My hunch is that you’re referring to a regression that was caused in 1.14 release and we worked with those that raised issues to resolve these regressions in a timely manner (see 1.14.1 – 1.14.3 releases and their corresponding issues raised).

    Anyway, we have decent test coverage for a lot of common scenarios, and do our best to prevent regressions, but unfortunately regressions do still occur.

    When we are made aware of a regression, we do our best to address them pretty quickly, and then add more tests to help prevent future regressions. The use cases for WordPress + WPGraphQL are quite vast, so we’re always looking to add tests for scenarios that aren’t already well covered.

    Multilingual / non-English use-cases could definitely use more testing!

    We’d love folks with more experience here to contribute tests / scenarios, etc so the codebase can better support those use cases. It’s certainly something I have limited experience with.

    If there’s queries that you rely on, I’d love to work with you to get the core WPGraphQL functionality you’re relying on better tested to ensure future releases don’t break the functionality.

    Let us know if you’d be willing to help us get some of these things better tested! ??

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