I see a lot of geeky types thinking about ditching WordPress because it uses old-as-the-hills PHP and not flavor-of-the-month Node.js (or Ruby or Python).
I’m interested in Node-coded Ghost too, but I’ve looked at it and know that it has a very long way to go until it’s close to feature-complete.
And Node isn’t exactly easy to get going. Plus most shared-hosting companies don’t offer it, and you’ll need a VPS, or a specialized cloud environment to run it.
I’m also looking into services like AWS Elastic Beanstalk and OpenShift that offer language-specific environments to run your Node (or Python or Java or Ruby or …) applications, including things like the Ghost blogging system.
That should go a long way toward making it easier to run a Node environment, but shared-hosting is still “today,” while running apps in OpenShift and AWS Elastic Beanstalk is “today” for some people but “a faraway tomorrow” for many people.
It’s still easy as hell to get a PHP app running. That’s why WordPress is going to stick with PHP, and it’s why newer apps like OwnCloud chose it: PHP is just so easy to deploy. Sure the language is looked down upon by geeks who are into Python, Ruby and Node. But for the majority of web hosts and the majority of people who use them, PHP is standard, and apps that use it are easier to get going than those that require you to wrap your head around Node or Rails. Sure YOU can do it, but can Joe Blogger?
This system informed me that an automatic update (3.8.1) has been installed on this system.
Whether you like it or not, this is kind of a killer feature that takes care of one of the biggest problems out there in the WP world: out-of-date systems. There are all kinds of people running WordPress, and not all of them are keeping as close an eye on their installations as they might. These automatic upgrade go a long way toward keeping those systems safe.
If you’re the kind of person who’s really on top of things, this might be welcome, or an annoyance. But there are more people than you know who just aren’t getting in there and doing the updates when they should.
Every time I changed my permalink style in this WordPress install on the devio.us OpenBSD system, I get locked out of the entire blog, unable to access the dashboard or the live site. All I get is a 403 error in the browser.
I deleted the blog and its database multiple times but kept falling into the same trap: Change permalinks, get locked out, clear database, reinstall …
Then I went for help, and found it from moderator Samuel B the WordPress.org forum. The hack to fix this lies in the .htaccess file, both what’s in it and its permissions. From the above forum post, here is the hack:
delete present .htaccess
upload blank .htaccess
set permalinks to desired (in the WordPress Dashboard)
chmod .htaccess back to 644 for security
I did this in the
command line). In my setup I don’t need rootly privileges to do any of this, so my shell lines begin with
$ instead of
#, and I don’t need to use
The first line gets me to my blog directory, the rest is the same wherever you are:
$ cd /public_html/blog
$ rm .htaccess
$ touch .htaccess
$ chmod 666 .htaccess
(Now reset permalinks in the WordPress Dashboard)
$ chmod 644 .htaccess