111–120 of 183 posts
A user profile display was ~30 SQL queries (who needs cache), and my poor 5$ VPS was sweating ...
learned a lot on what not to do! fun times !
I love Wordpress. People install it on their own, install dozens of useless, unsecure and buggy plugins ("it's easy, just clic clic clic... I love my admin panel !") and after a while their websites break and then we can charge them for a more secure and resilient solution.
Earlier quoted context omitted.
Are you intentionally not mentioning which country and law?
GDPR, EU. You cannot simply load third party shit on your website, without asking for consent. By downloading an SVG from a third party provider, I would need to ask the visitor, whether transmitting their IP address is OK or not, since that is personal data. Aside form all the information associated with when someone accesses the site.
What I find remarkable is that multiple people can say 'I am a Wordpress Developer' and it will translate into very different experiences and skillsets. For some it means clicking around installing theme, plugins then writing the content of pages through the Wordpress admin. For others it means old school php code to customize Wordpress behaviour with PHP template to write the HTML. This is called classic theme. For…
if they have chosen a diverse enough clientbase.
Earlier quoted context omitted.
From a business perspective the significant part of the website costs are man-hours for setup and maintenance. Got something to say about how WP compares to others when it comes to man-hours (assuming you can buy any and all plugins you want)? Honest question, because I have no idea about CMS.
But they overprice and they forget people use multiple plugins, so I use a third-party service that leverages GPL to offer most premium themes and plugins for a low annual fee.
> they overprice and they forget people use multiple plugins
People who complain about the prices also forget that a lot of these plugins take months or years to develop. You’re (we’ll not you since you made it clear you don’t pay the devs) literally getting thousands of man hours for like 60 bucks per year.
Earlier quoted context omitted.
Are you intentionally not mentioning which country and law?
GDPR, EU. You cannot simply load third party shit on your website, without asking for consent. By downloading an SVG from a third party provider, I would need to ask the visitor, whether transmitting their IP address is OK or not, since that is personal data. Aside form all the information associated with when someone accesses the site.
That's not how the GDPR works at all. If it were, there would be no content distribution networks operating in the EU. Linking to a third party image in document markup does not involve you transmitting anything.
Quick judgments and strong opinions have unfortunately become part of the community. Having spent the last 2-3 months working excessively on WordPress development, I would like to say a word about the excellent isolation of code with blocks ("Gutenberg"). As standalone plugins or in combination with Advanced Custom Fields, these allow for perfect, modular websites and development flows (design system), where even the…
I'm doing what you're proposing literally right now. I have a fascinating error 500 on production because somehow, somewhere, today Gutenberg and ACF w/Blocks are having a disagreement on parsing the content of a nested media field. Which could be ranging from "the user added an image description where he shouldn't have" to "a global object from a plugin is polluting other global objects passed to acf_register_block_…
In a classic wordpress install this would just cause some weird garbage in the output, but given that in a gutenberg+ACF setup the content data is passed to the React/Block rendering engine, it would absolutely go crazy.
Earlier quoted context omitted.
This is stability. Stability is good. There is no need to change code that works just because it collides with modern taste. If WordPress has a stabilizing influence on php that's even better. All the breaking changes of the new versions are a nightmare for an established project I work on.
Code is never just working. The environment it runs in changes, requiring refactoring things. We’re not talking about a showcase piece of artisan algorithm here, but bug-riddled legacy code reliant on outdated system packages, SQL queries that cannot use bound parameters for historic reasons and are ever-prone to injection attacks. Code that uses broken multibyte encoding, such that it is vulnerable to several attack…
I would not hesitate to take this position. Of course it depends, on how severe the bugs are, especially for the outer code (like plugins) calling it, and on how bad the performance is. But otherwise absolutely, never break user space.
> The environment it runs in changes
The web environment Wordpress runs in did not change all that much. The JS ecosystem simulates big changes, but that's all bullshit. Server code that worked 30 years ago still works - if projects like PHP don't go out of their way to break it.
I just wish WordPress actually adhered to development standards, not actively tried to break them. Using globals everywhere and encouraging spaghetti code with its classic themes, and with its new themes it evidently learned nothing and is encouraging JSON inside HTML comments which obviously has no editor support, is very prone to errors, besides being just plain stupid (like seriously, some senior engineers I assum…
If you adhere to development standards your users aren't locked in to your platform. They could move to better working, more manageable CMSes instead of begrudgingly having to pay someone or, better yet, move to your hosted solution to keep the platform from tripping on its own feet. Unfortunately that could negatively affect your "Our platform powers 43.4% of all websites" marketing pitch.
I just wish WordPress actually adhered to development standards, not actively tried to break them. Using globals everywhere and encouraging spaghetti code with its classic themes, and with its new themes it evidently learned nothing and is encouraging JSON inside HTML comments which obviously has no editor support, is very prone to errors, besides being just plain stupid (like seriously, some senior engineers I assum…