• go $fsck yourself
      link
      fedilink
      English
      21 month ago

      No, I didn’t. I just ignored it because it’s not a very good point or relevant to the question.

      • AmbiguousPropsOP
        link
        fedilink
        English
        4
        edit-2
        1 month ago

        You are completely missing their point. The plugin repo and updates are hardcoded to use WordPress’s servers, that’s the issue here. Yes, you can totally self host WordPress, you don’t need something like cpanel (in fact, I don’t see how it’s relevant to this discussion, and I think the last time I used that archaic backend was in 2015), but if you want access to the plugin repo + automated plugin updates, you are unfortunately impacted by this BS.

        Why be rude to people who are just trying to explain the issue to you?

        • go $fsck yourself
          link
          fedilink
          English
          21 month ago

          Ah yeah I definitely misunderstood the question of the comment they were replying to. I only brought up CPanel because it’s extremely pervasive and is an example of how easy it is to host WordPress.

          On the flip side, you can upload plugins to install them and the plugins can be coded to use different servers for automatic updates. In fact, the most popular platform to buy paid plugins and themes, Envato, has a plugin to facilitate updates which don’t use the WP.org repo servers.

          Honestly, the plugin repo and “click to update” system is one of the biggest problems with the WP ecosystem. Since the vast majority of plugins and themes are horribly made and run by idiots, it’s very often that updates will break sites outright. That’s why I disable it for client accounts.

          Sorry I came off as rude. It was just a misunderstanding.