this post was submitted on 11 Oct 2024
47 points (85.1% liked)

Programming

17432 readers
211 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] gofsckyourself@lemmy.world -1 points 1 month ago (1 children)

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

[–] AmbiguousProps@lemmy.today 4 points 1 month ago* (last edited 1 month ago) (1 children)

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?

[–] gofsckyourself@lemmy.world 2 points 1 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.