Category Archives: WordPress

The open source publishing platform I co-founded — development, releases, community, and the ecosystem.

A Bank Website on WordPress

There’s a thread on Quora asking “I am powering a bank’s website using WordPress. What security measures should I take?” The answers have mostly been ignorant junk along the lines of “Oh NOES WP is INSECURE! let me take my money out of that bank”, so I wrote one myself, which I’ve copied below.

I agree there’s probably not a ton of benefit to having the online banking / billpay / etc portion of a bank’s website on WordPress, however there is no reason you couldn’t run the front-end and marketing side of the site on WordPress, and in fact you’d be leveraging WordPress’ strength as a content management platform that is flexible, customizable, and easy to update and maintain.

In terms of security, there are a two simple points:

  1. Make sure you’re on the latest version of core and all the plugins you run, and update as soon as new version become available.
  2. Use strong passwords for all user accounts. For extra credit you could enable a 2-factor plugin, use Jetpack’s WordPress.com login system, or restrict logged-in users to a certain IP range (like behind a VPN).

If your host doesn’t handle it, make sure you stay up-to-date for everything in your stack as well from the OS on up. Most modern WP hosts handle this (and updates) for you, and of course you could always run your site on WordPress.com VIP alongside some of the top sites in the world. If you use any non-core third party code, no harm in having a security firm audit the source as well (an advantage of using open source).

For an example of a beautiful, responsive banking website built on WordPress, check out Gateway Bank of Mesa AZ. WordPress is also trusted to run sites for some of the largest and most security-conscious organizations in the world, including Facebook, SAP, Glenn Greenwald’s The Intercept, eBay, McAfee, Sophos, GNOME, Mozilla, MIT, Reuters, CNN, Google Ventures, NASA, and literally hundreds more.

As the most widely used CMS in the world, many people use and deploy the open source version of WordPress in a sub-optimal and insecure way, but the same could be said of Linux, Apache, MySQL, Node, Rails, Java, or any widely-used software. It is possible and actually not that hard to run WordPress in a way that is secure enough for a bank, government site, media site, or anything.

If you wanted any help on this feel free to reach out to Automattic as well, we have a decade of experience now dealing with high-risk, high-scale deployments, and also addressing the sort of uninformed FUD you see in this thread.

If you’ve developed a major bank site in WordPress leave a link in the comments.

We’re organizing an exciting new conference series focused on blogging, called Press Publish. The speaker list has some really awesome folks on it, and will include notable WordPress bloggers telling their stories as well as Automattic employees teaching tutorials and workshops. Plus, WordPress.com Happiness Engineers will be ready and waiting to help people one-on-one with their blogs.

The first two events are in Portland on March 28 and in Phoenix on April 18, and if you register with this link in the next week or so you get a discount, special for Ma.tt readers.

WordPress [actually Automattic] has scored an important victory in court against a man who abused the DMCA to censor an article of a critical journalist. The court agreed that the takedown request was illegitimate and awarded WordPress roughly $25,000 in damages and attorneys fees.

Yes! Good laws become bad when people abuse them. Here’s the source: WordPress Wins $25,000 From DMCA Takedown Abuser (s/WordPress/Automattic/).

There’s the smart publishers, and then there’s the ones going out of business. WIRED is one of the smart ones, and just launched an awesome redesign on WordPress. From their editor-in-chief:

Back in 1994 we launched Hotwired, the first site with original editorial content created for the web. It was a digital home for reporting on the future of science, business, design, and technology. You’ve come to trust us over the past two decades, but our growth online has sometimes come too quickly and with some pain. When I took over as editor in chief in 2012, WIRED had an archive of more than 100,000 stories. That’s good! But they were spread out over more than a dozen different databases, sections, and homepages tenuously connected by virtual duct tape and chewing gum. The cleanup process—onerous and without a shred of glamour—took almost 15 months. But finally, last year, our engineers rolled out a newly unified site architecture built atop a single streamlined WordPress installation. And you didn’t notice a hiccup. Maybe you saw that pages loaded a touch faster. Stories looked more WIRED.

The story of the engineering behind it from Kathleen Vignos is also cool:

The redesign gives us the third incarnation of our Curator application, which started years ago as a separate Groovy on Grails application maintained by a single Java developer. Curator once consumed articles from 35 different blogs for curation on our homepage. When we migrated our 17 active WordPress blogs into one WordPress install, we also rewrote Curator in Cake PHP to match our WordPress PHP backend. After this, anyone on our team could maintain Curator—but the architecture remained the same and lived outside of WordPress. Using this version of Curator, our web producer team manually constructed the homepage throughout each day as various stories were ready to be promoted.

Our new and improved Curator is now a custom WordPress plugin—and it’s artificially intelligent! This allows our homepage and section landing pages to be both automated and curated at the same time. Stories flow through automagically based on editorial criteria, but editors can take control of the flow by locking stories in certain slots in our card system. This means our homepage and section landing pages are constantly changing with new stories all day long.

Curator sounds cool, as does the coming “longform feature article builder.”

On WordPress.com and Bitcoin

There’s been some controversy and discussion about the fact that WordPress.com no longer support Bitcoin in our new checkout flow on signup. (It’s still there in some other flows.)

Since there has been a lot of discussion about it, I wanted to share directly some of the answers I had to Grace’s follow-up questions, since I’m not sure if they’ll be published and if they are it probably won’t be in their entirety.

In regards to your future plans for the currency, is bitcoin support definitely returning or is that just a possibility at this point?

We’re big fans of Bitcoin and hope to support it again in the future, for all of the reasons that we originally supported it in 2012, which you can read about here:

http://en.blog.wordpress.com/2012/11/15/pay-another-way-bitcoin/

Is there anything that will influence the outcome of this decision?

No, it is simply a matter of development resources, which are especially scarce for us right now as we’re trying to keep up with growth.

You mention that bitcoin has low volume compared to other payment methods, has this always been the case? Has its volume share changed over time?

The volume has been dropping since launch, in 2014 it was only used about twice a week, which is vanishingly small compared to other methods of payment we offer. We supported Bitcoin for philosophical reasons, not commercial ones.

What are the key aims of your checkout process changes?

Our goals are twofold: to refactor the code behind it which has parts that are over five years old and has grown very complex, and to make it faster and easier for people to buy our services.

When you first launched bitcoin payments WordPress’ blog post praised it as an inclusive payment method for those who cannot use PayPal. Do you worry that these people will now be excluded from the platform?

Of course, but either that number of people turned out to be smaller than we expected or they found other ways to pay. Since it’s so few people overall I’m happy to extend people’s subscription for a year, as I offered in your comments section.

What does being a ‘big believer’ in bitcoin mean to you?

I believe Bitcoin or some other blockchain-like system will be the basis of the majority of financial transactions in the future, from small remittances to multi-billion dollar corporate acquisitions. I think transaction costs should follow Moore’s law, and I don’t think we’re going to get there with the centralized gateways that currently account for the overwhelming majority of transactions. I also personally hold Bitcoin, I’m an advisor to Stellar.org, and my friends make fun of me for bringing up Bitcoin and the blockchain in unrelated conversations.

The bitcoin option still appears on the ‘WP Admin’ screen but not on ‘My Upgrades’. Is this part of the phase out, or likely to stay this way?

That’s on the old code base, and will be available for a short while if any current Bitcoin subscribers want to renew while the option is still available.

A federated Wikipedia by Jon Udell talks about the ossification happening in the Wikipedia community, caused in part by its attachment to rules that were created with the best of intentions. All open source communities, including WordPress, have to be vigilant against this. Sometimes we have to throw out what worked before to create what will work tomorrow.

Over on the BruteProtect blog they have a look at the Jetpack Bloat Myth, and find that counter-intuitively even though Jetpack has more comprehensive functionality it’s faster than using individual plugins to do the same things. There are economies of scale to Jetpack’s approach, and it doesn’t even include the impact of doing things more advanced and complex like Related Posts. There’s a reason why some web hosts like WP Engine ban most related post plugins but encourage the use of Jetpack.

The performance of the plugin code, though still faster, is still a small difference when compared to the benefit of offloading certain tasks like image resizing, related posts, stats, video transcoding, and more in the future to the WordPress.com cloud (which is now across 11 datacenters worldwide).

Of course if you don’t need the functionality at all it’s always faster to have nothing, but that’s a shrinking minority. There are still more optimizations to be had, and in line with a performance focus in 2015 look for more improvements to come in the future. In the meantime, check out the Jetpack benchmarks.