Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WordPress is now 13 years old

wordpress.org

Post reply on HN
Print view View original

61–66 of 66 posts

Re: WordPress is now 13 years old

#61

Post by blueside »

shaqbert wrote: post #28

I remember my first install. It was glorious, started posting like a madman. At some time - when gaming Google was the thing, say 2008 - had thousands of sites based on WP. Then I had my first major vuln and spend my week-end fighting fires. Then I had my first encounter with encoding mess ups... an add-on going wild... Fond memories...

I remember thinking back then, and sometimes now I still do, that I would gladly pay a fee for a togglable feature that let me exclude all wordpress sites in my search results

Re: WordPress is now 13 years old

#62

Post by jtrtoo »

jwarren wrote: post #48
falcolas wrote: post #3

A few free safety and performance tips when dealing with wordpress: - Whitelist IPs for access to your wp_admin and wp_login. - If you have the skills to automate WordPress updates yourself, remove all write access (except for the uploads folder) from the user WordPress is running as (i.e. www-data). It's all just unzip and untar over the structure of the directory anyways. - If you remove write access, you might as…

I'd also recommend looking into Bedrock, as it neatly sets you up for updating via Composer, which is quite nice once you get used to it. Good thing to fire off on a post-deploy hook. Then you can completely disable any internal updates and completely control the version of core and plugins. The folder structure also adds some minor security through obscurity. There are other niceties in there too.

Thanks for the suggestion. Looks interesting. Link for others: https://roots.io/bedrock/

Re: WordPress is now 13 years old

#63

Post by w001y »

Wordpress is, imo, the reason PHP has historically gotten a bad rap. Needle/haystack/type/performance PHP jibes aside etc etc, WP has been the single point of contact for situations where my company has had to remediate a hack/data breach/script kiddie scrawl. I've seen full hosted servers being unplugged with no comebacks, tens of thousands of dollars in rebuild costs, lost clients due to security concerns.. the culprit? pointing over there

The easy retort is "just keep it patched and up to date", natch. The ongoing costs/technical debt involved in maintaining a Wordpress install sometimes ends up being greater than what it cost to roll the thing out.

Wow, I'm getting old and complainy.

Re: WordPress is now 13 years old

#64

Post by kyriakos »

connorjburton wrote: post #31
kyriakos wrote: post #22

Earlier quoted context omitted.

Its template system is ugly. There are projects that bring modern templating to WordPress though e.g. https://github.com/tormjens/wp-blade Consider though that when its template system was "invented" there wasn't much else available and people back then used to mix code and html all the time (both PHP and ASP developers). In their attempt to keep it backwards compatible we still have to suffer through the template sy…

Timber does this too if your like your Twig. http://github.com/timber/timber Disclamer: I'm on the dev team

Timber looks good thanks

Re: WordPress is now 13 years old

#65

Post by davemac8 »

w001y wrote: post #63

Wordpress is, imo, the reason PHP has historically gotten a bad rap. Needle/haystack/type/performance PHP jibes aside etc etc, WP has been the single point of contact for situations where my company has had to remediate a hack/data breach/script kiddie scrawl. I've seen full hosted servers being unplugged with no comebacks, tens of thousands of dollars in rebuild costs, lost clients due to security concerns.. the cul…

I think it's more likely that the low barrier to entry required to build a WP site is what has caused these issues, well, in the past, anyway.

What you are describing could be attributed to any poor quality code, it's not specifically WP core that is to blame, but rather poor quality code built on top of it.

In regards to managing WP sites being costly and taking up time, I manage many WP client sites and find the opposite to be true (I did write the code for all of them, though)

Post reply on HN