Live data from Hacker News

WordPress is now 13 years old

wordpress.org

31–40 of 66 posts

Re: WordPress is now 13 years old

#31

The problem I have with wordpress - and any php project for that matter - is that I'm afraid of the code. I've done some template editing for WP and it already scarred me enough. But maybe I just prefer writing and working in my own familiar codebases instead of spending a small amount of time in that of others, a curse that a lot of PHP developers have (the "I'll write my own framework / cms" curse)

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

Re: WordPress is now 13 years old

#32
I only recently tinkered with wordpress/buddypress plugins for a hobby site. I can see why it became so popular. It's dead easy to start tinkering because it forces you to learn very little. Just find the place where you want to hook your code, and dump tons of godawful code in there. That means that people use 1000 different styles in their plugins, but its the big price to pay. In comparison, try tinkering with oxwall without digging deep into their object-oriented code.

Re: WordPress is now 13 years old

#33
At this point I don't think Wordpress is going to change their codebase into something more modern and secure. Is there any other easy to use blogging platform like it? PHP based because PHP is everywhere, based on a modern framework (symfony2, laravel, etc), jinja-like template system, support for databases other than mysql?

Re: WordPress is now 13 years old

#34
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…

Another safety tip: don't install any plugins unless you're very, very sure that they're safe. Most security problems with WordPress originate in badly written plugins, not in the core product.

Re: WordPress is now 13 years old

#35
post #29

The fundamental lesson WordPress taught me is that the product wins over technology. Even back in 2004 it was clear that the internal code wasn't that great. So what? It installed delightfully quickly, and let me create posts with valid markup and good typography right out the box. And then the community management and plugin/theme ecosystem. For example, Drupal may have a more programmer-approved API, but (at least…

I was always a little bit weirded out by features for ease-of-use that required you to go against what the documentation described as security best practices.

Re: WordPress is now 13 years old

#36
post #34
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…

Another safety tip: don't install any plugins unless you're very, very sure that they're safe. Most security problems with WordPress originate in badly written plugins, not in the core product.

If you're not going to install plugins, doesn't it neuter one of the big draws to using WordPress in the first place? Ideally there would be better separation between the plugin and core stuff, but oh well.

Re: WordPress is now 13 years old

#38

At this point I don't think Wordpress is going to change their codebase into something more modern and secure. Is there any other easy to use blogging platform like it? PHP based because PHP is everywhere, based on a modern framework (symfony2, laravel, etc), jinja-like template system, support for databases other than mysql?

> and secure

Given it's popularity , i would assume wordpress is (by sheer force of Trial and error ) the safest choice.

Re: WordPress is now 13 years old

#39

Earlier quoted context omitted.

It's a much safer platform these days... ...most of the sites with really important data have long since migrated away. Haha

WordPress itself is not as insecure as people make it to be. Its code base gets a lot of scrutiny and security issues are fixed promptly. The problem begins when you start installing plugins... which most of them are coded by designers-turned-programmers who needed to add a new function to a client#s WordPress site. Reading their code its obvious that they are build by mix and matching tutorial and example code they…

I haven't dug into any of this stuff, but wouldn't a smartly designed plugin system give plugin code fewer permissions to prevent precisely this sort of issue?

Re: WordPress is now 13 years old

#40
post #38

At this point I don't think Wordpress is going to change their codebase into something more modern and secure. Is there any other easy to use blogging platform like it? PHP based because PHP is everywhere, based on a modern framework (symfony2, laravel, etc), jinja-like template system, support for databases other than mysql?

> and secure Given it's popularity , i would assume wordpress is (by sheer force of Trial and error ) the safest choice.

Yet the Panama Papers thing happened.
Post reply on HN