We wanted to do this for a long time and finally managed to. VersionPress is now free & OSS on GitHub.
It is my great pleasure to announce that VersionPress goes fully Open Source today. While the software itself has been GPL’d since the first releases, we’ve been developing it privately and Early Access was a paid-for program. All of that goes away today. VersionPress’ new home is now on GitHub are we’re not just making it freely available there, VersionPress will truly be developed out in the open and run as an open source project, hopefully with the help of a broader WordPress community over time. We encourage you to star / watch the repo and join us in the mission to turn WordPress into a fully versioned platform.
Oh, and “by the way”, we’re also releasing VersionPress 3.0-beta today.
This is a big moment in the project’s history so let me share a bit of a background story.
The early days
VersionPress started as an internal research project between me and Jan a couple of years back. We were solving our own workflow issue where we couldn’t easily synchronize WordPress sites between environments because database merging was virtually impossible. We decided to use Git (not SVN) as an internal engine of what we started calling VersionPress, and the results were pretty amazing. This tool
"Thesis, Automattic, and WordPress. A 10,000 word story to describe a conflict of ideology." by Brian Krogsgard
Chris Pearson and Matt Mullenweg have hardly communicated with one another in the last five years, but they are ideological enemies. They have very strong personalities and unshakable beliefs on business and software. This is a story of their dispute, their idealism, and the implications it will have on the WordPress project. Chris Pearson and Matt Mullenweg have hardly communicated with one another in the last five years, but they are ideological enemies. They are both wealthy individuals (though of different magnitudes) thanks to their online endeavors, with very strong personalities and unshakable beliefs on business and software. This is a story of their dispute, their idealism, and the implications it will have on the WordPress project.
Matt Mullenweg co-founded WordPress, founded Automattic, and is one of the most successful entrepreneurs of his generation. He runs a billion dollar “unicorn” startup centered on a culture of embracing open source technology and has achieved incredible success embracing principles counterintuitive to either Silicon Valley or big corporate culture. He’s paving a new path for how to create a valuable software company while religiously defending and
When we launched this website two and a half years ago (oh my was that so far back?), together with a lot of novelties in the way we follow WordPress news we introduced a unique algorithm that measures member contribution to the site. It is somewhat based on Google's PageRank algo and it awards users that upvote good content and punishes those that upvote spammy stuff.
Tom Harrigan is first and Ryan and Donna are soon going to be in the 10.00 club too. As a reminder, vote strength of 10 means that Tom's vote counts as 10 new account votes. So if a bad article is shared, and a spammer creates nine accounts and upvote it, an article that Tom shares around that same time would still outrank it. Same goes for voting on an another article.
If a WordPress news organization wants a new editor they know where to look :)
Congrats Tom and thanks to all members for making this website a great one!
ps. full list of members is available here
I'm Pippin Williamson, founder of numerous plugins, a reviewer for WordPress.org/plugins, a cyclist, and avid craft beer lover. Ask me anything!
I'm Pippin Williamson, founder of numerous plugins, a reviewer for WordPress.org/plugins, a cyclist, and avid craft beer lover. Ask me anything!
I am a WordPress plugin developer living in Hutchinson Kansas.
6 years ago I began my journey working in WordPress and today I am the owner and CEO of three companies and the founder of several large eCommerce based plugins, including Easy Digital Downloads, AffiliateWP, and Restrict Content Pro. I have also written well over 200 plugins, I help review plugin submissions on WordPress.org, and frequently contribute back to WordPress core. I also co-host a podcast about WordPress development called ApplyFilters
Outside of WordPress and development, I love cycling, hiking, great coffee, and craft beer. I'm an avid homebrewer and a lover of sour beers.
My wife and two daughters are the heart soul of everything I do.
Ask me anything!
Quite a few people have asked me how WP Site Care started and I finally sat down and wrote it all out. I shared some of my mistakes along the way, and some of the most valuable things I've learned too. Hope you all find it interesting/useful :)
After reading Josh Pigford’s post on the Baremetrics blog last week about his journey from Maker to Manager, I had a flood of memories come to me about the time I’ve spent building WP Site Care, and all of the lessons I’ve learned along the way. My role at the company has changed a lot since the early days, and I thought it’d be fun to not only take a look back and where we’ve been, but also to figure out a lesson or two that I’ve learned along the way. Where it Began
I started to think about how far we’ve really come in just a few short years, and realized that I’ve never even shared our company’s origin story with the world.
Origin stories are generally reserved for superheroes, but why can’t a hip (ok, this could be subjective) and growing brand have an origin story too? The truth is that it can, and I’d like to share ours with you today.
Humble Beginnings, Hold the Krypton
I’ll apologize in advance for all of the terrible puns I’ll be using throughout the post. It’s a cheesy theme, but I’m gonna roll with it, mainly because I can. And because superheroes are pretty awesome.
WP Site Care has been 100% bootstrapped from day 1.
When I left my corporate job in IT, I wanted to build
HTTP/2 is awesome, but requires HTTPS, which is hard to setup. Let's Encrypt and WordPress can make HTTPS setup simple and help achieve a faster web sooner.
TL;DR — HTTP/2 is awesome, but requires HTTPS, which is hard to setup. Let’s Encrypt and WordPress can make HTTPS setup simple and help achieve a faster web sooner. My eyes are heavy, my head foggy. Kind of feels like I’m in a dream right now. A couple of hours ago I got home from Philadelphia, where I attended the WordPress Community Summit and the first annual WordCamp US over the past 7 days. And man, what a time.
There will be plenty of recap posts published this week, so instead, I thought I’d dig into one thing I got very excited about at the summit.
Weeks ago I got really excited about HTTP/2 while researching it for
an episode of Apply Filters. (If you haven’t learned about HTTP/2 yet, I urge you to listen to that episode. I’m very proud of the work Pippin and I did on it.) I learned that adding support for HTTP/2 on your site gives it an instant performance boost. And if you already have HTTPS setup, enabling HTTP/2 is as easy as updating Nginx to version 1.9.6+ and adding http2 to the config file:
listen 443 ssl http2;
If you don’t have HTTPS setup, you have do that in order to get HTTP/2 as it is only supported over HTTPS.
Unfortunately setting up and managing
Read thoughts of Tom McFarlin about The WordPress Community which he believes is a Comedy of Drama, Ego, Oligarchies, and More
I don’t know why I feel compelled to begin a post like this, but this is going to be a lengthy as it covers quite of a bit of the state of the culture of WordPress right now. As someone who loves the software, makes a living off of it, and tries to follow along with everything going on with it, things have gotten really intense over the past few weeks – more intense than usual, that is – and it’s kind of a bummer to see.
Secondly, I’ve been told on a couple of occasions in the past that I don’t do a good job of staking my own claim in terms of how I perceive a given situation. That is, I’ve been told that I tend to hang out in the gray versus the black or white of a issue (so I try to weigh both sides of an issue – big deal :) – but I thought maybe I’d take this time to lean in one direction or the other a little harder than I usually do.
Like I said, I don’t know why I should preface what I opt to write about in this post (as it kind of enforces the point above), but I figured it was worth giving some background of where I’m coming from.
And my experience won’t be the same as yours and yours won’t be the same as mine or the next persons, but this is my take on what I’ve seen over the
Nick Haskins is putting up Aesopinteractive for sale. Aesop Story Engine, Lasso, Story.AM, etc.
A couple weeks ago I moved the entire family across a few states from Texas to North Carolina, in search of something better in life. You see in Texas, there just isn’t anything to do, or see. You can drive for eight hours (no exaggeration) and the land stays flat, and you’ll still be in Texas. Sure you can hike, for maybe 10 minutes out of the year when it’s not 200 degrees. Sure you can swim in the river, for a couple months out of the year and you’re guaranteed to have 3000 other people there too, because it’s the only place to go. You surely can’t live off the land very easily, and seasons? Yeah right, there’s two. Really hot, or really cold.
So we’ve been here in North Carolina for a couple of weeks, and we couldn’t be happier. My kids are happy. My wife is happy, and the weather is just amazing. During this time, I’ve learned one important lesson.
Family. Is. Everything.
But unfortunately the last couple of years I’ve been putting my code before my family. That stopped two weeks ago. At 3 o’clock I turn the computer off, and I spend time with my family. I’m committed to my job at CG Cookie, and at the end o the day I really don’t want to spend any more time on the computer than
It's that time! Proposal to merge into core. A 2-parter though. Whatcha think?
Hello everyone! This is the post you’ve all been waiting for. We on the REST API team (myself, @rachelbaker, @joehoyle, @danielbachhuber, and newest member and core committer @pento) would like to propose merging the REST API into WordPress core. We’ve been working a while on this, and think it’s now ready to get your feedback.
This is our first iteration of the proposal, and we’re actively looking for feedback. If you have thoughts on the project, or on this proposal, let us know! Only with your feedback can we make progress.
What is the REST API?
The REST API differs from existing WordPress APIs in that it is explicitly designed from the ground up for modern mobile and browser usage, using the lightweight and widely-supported JSON data serialization format with a modern REST interface.
Pippin shares the highs and the lows of building his business around eCommerce platform. Pretty insightful to say the least.
At this time three years ago, I released a small eCommerce plugin to the world called Easy Digital Downloads, and now it’s anything but a small plugin. During the last few years, I have had some of the best highs of my life, and a few of the deepest lows. For my own reflection, I would like to look back at a few of hardships and a few of the peaks I encountered along the way. The team
First, I cannot thank enough the team of people that have helped propel us to where we are today. It may have started as a one man journey, but it was only that way for a short while. Today the Easy Digital Downloads team consists of four full-time developers and support staff, two part time support staff, and two very active contributing developers, and on May 1 we are bringing on another full time team member to manage documentation. To each of these individuals, I must express my most sincere gratitude for believing in the platform, trusting me to lead it, and sticking along side the rest of the team through good and bad. Without the hard work of everyone on the team, Easy Digital Downloads would only be a shadow of what it is today.
Growth of a code base
Easy Digital Downloads began as a relatively
Huge news! Wow, this came as a big surprise, but congrats to them, and best of luck to all.
Today marks the beginning of the next exciting chapter in our journey as WooThemes. The short and sweet of it – we are joining the Automattic family! Read more about this from WooThemes co-founders, Mark and Magnus and from Matt Mullenweg of Automattic. What does this mean for our customers? If you’re using WooThemes products (extensions, themes, or other) your licenses and experience will continue as before and there is no reason to worry. In the coming weeks and months you can expect business as usual from WooThemes, now with the added power of Automattic behind everything we do. For support, continue to reach out to us in the same way you always have done.
What does this mean for our team? The Woo ninjas are not going anywhere! They’ll continue working all around the world, with exciting opportunities for learning and growth through the cross-pollination of Automattic’s and our engineering, support and marketing teams.
In 2008, as three strangers in three countries, we set out on a quest to pioneer WordPress commercial theming, never dreaming of the rocket-propelled voyage into the self-hosted eCommerce unknown that lay ahead. It’s been an incredible ride, backed by a unique community,
Good luck on your new adventures Vid. Now.. well isn't this interesting...
Automattic has taken over a majority stake in Pressable, the managed WordPress hosting company, with a purchase of Pressable CEO Vid Luther’s shares of the company. They were already a significant investor. Automattic has purchased a majority stake in Pressable, one of the earliest managed WordPress hosting companies, founded in 2010. They were first known as ZippyKid, and rebranded in 2013.
Automattic was already a shareholder in Pressable, most recently as the primary investor of a $1.5 million round in April of 2015.
Technically, Automattic purchased common stock shares from Vid Luther, the CEO of Pressable. The monetary value of that common stock was, “enough to be debt free,” according to Vid. He owned about 37% of the company, or 4.5 million shares of 7 million shares of common stock (versus preferred shares). The company has also been in debt, reportedly close to $1 million worth.
Automattic is now the majority owner of Pressable, and since Vid sold his shares, this is effectively an acquisition, and Automattic will be able to set the direction of the company from now on. Chris Lauzon, a Happiness Engineer at Automattic, is the interim CEO. There are other smaller investors in
Alex King, one of the original contributors to WordPress, founder of CrowdFavorite, and all around nice guy has passed away after a battle with cancer.
Big news for the WordPress core leadership team: Andrew Nacin has joined the United States Digital Service.
Andrew Nacin now works at the U.S. Digital Service, the federal government service that aims to “redefine public service for a new generation.” Nacin continues his role as WordPress lead developer, but is stepping back from working on the project full time. Andrew Nacin hasn’t worked at Audrey Capital since January. At Audrey, he has worked for more than four years for WordPress co-founder Matt Mullenweg, exclusively on the WordPress project. He has joined the White House’s new U.S. Digital Service.
The U.S. Digital Service is a new organization that operates from the White House, with an aim to modernize and transform the way the federal government operates digitally.
When I was approached, I have to admit that I was nervous to step back from the day-to-day buzz of WordPress because I’ve invested so much. But the community stepped up, in most cases not even knowing about my life change. That’s the beauty of open source, and the fantastic WordPress community in particular. WordPress continues to play an important role in my life. With Matt Mullenweg’s support and encouragement, I’m taking time away from Audrey, where I’ve worked since 2010. I’m still actively involved in the project,
If you run a WordPress business, then this info on Pippin’s Plugins will be a good read. You can't get much bigger or better than Pippin’s Plugins, and overall a taste of WordPress plugin industry in general.
It is that time of year again! As in years past, I like to look back on the previous twelve months and see how we did. In this year’s review, I will share revenue numbers, challenges, achievements, insights, and more about my business building and selling WordPress plugins. Previous year in review posts:
There are a lot of great things that happened in 2016, but it was also easily one of the most difficult years I can remember in my adult life. 2016 put before me challenges and decisions I did not expect. For the most part, each of the challenges was overcome, though some of them are still being battled with, and I believe I’m a better person and a better business owner for having faced them. I’ll talk more on the challenges below.
When I started this plugins business 5-6 years ago, I never envisioned I’d have a team working with me, much less a team of 15!
I started bringing on people to help me with customer support in 2013 and doing that was easily one of the best things I’ve ever done. One became two, two became three, and now we have 16 members (counting myself) of the Sandhills Development team. These 15 are comprised of full time and part time
Great news! The website and code are all coming in under the WordPress.org umbrella and financial support is also involved.
WP Rollback lets you rollback any theme or plugin to any version published on the Repo. There's no settings, it's built to be a seamless WordPress update experience. Great for those times when an update just doesn't go the way you wanted it to.
Quickly and easily rollback any theme or plugin from WordPress.org to any previous (or newer) version without any of the manual fuss. Works just like the plugin updater, except you're rolling back (or forward) to a specific version. No need for manually downloading and FTPing the files or learning Subversion. This plugin takes care of the trouble for you. Rollback WordPress.org Plugins and Themes
While it's considered best practice to always keep your WordPress plugins and themes updated, we understand there are times you may need to quickly revert to a previous version. This plugin makes that process as easy as a few mouse clicks. Simply select the version of the plugin or theme that you'd like to rollback to, confirm, and in a few moments you'll be using the version requested. No more fumbling to find the version, downloading, unzipping, FTPing, learning Subversion or hair pulling.
Muy Importante (Very Important): Always Test and Backup
Important Disclaimer: This plugin is not intended to be used without first taking the proper precautions to ensure zero data loss or site downtime. Always be sure you have first tested the rollback on a staging or development site prior to using WP
Hello there! I currently reside in the wonderful state of Ohio and host the WordPress Weekly podcast. I'm the founder of WP Tavern, one of the largest sites devoted to WordPress and I've been writing about the software for more than eight years, it's one of the few things in life I'm good at. I enjoy watching trains, the Back to The Future movies, meteorology, the 90s, especially the grunge music era, and good food. What more do you want to know?
WP.org no longer redirects to WP Beginner. Owner Syed Balkhi transferred ownership to the WP Foundation.
Over the last year and a half, if you typed in the domain wp.org, then you were redirected to WPBeginner. This was an unexpected and unpleasant surprise for many because you really wanted to visit WordPress.org, home of the popular content management system. Today, I’m pleased to announce that we have donated the domain to the WordPress Foundation. For majority of you, this doesn’t mean anything and life goes on as usual. For those who’re more involved in the WordPress community, this is a huge deal because now you can type wp.org in your Tweets, Slack messages, Facebook statuses, etc without cursing at me or WPBeginner.
I know this redirect was frustrating because many of you tweeted at me or sent us angry emails. To all of you and even those who took the high road, I want to apologize for my actions.
Now you’re probably wondering what changed?
The short answer is A LOT.
My wife and I are pregnant with our first baby. This has given me a new perspective on life as whole.
From ironing out a new will to working on expanding my life insurance coverage, there’s a lot happening. For the first time in my life, I’m thinking about unforseen circumstances.
A new benchmark of the 10 most popular WordPress caching plugins.
A speedy website attracts more traffic, reduces bounce rates, and ranks better on search engines. Maybe it’s time to re-evaluate your site’s caching needs and invest in an upmarket plugin to reap the rewards of your hard work. High page load times have an adverse effect on your WordPress website and caching ensures that you never have to face them head on. In this article, we’ll aim for the lowest possible page load times with the right caching plugin by evaluating several different available options and ranking them based on page load times conducted in a real-world testing environment.
Let’s put this all into context before we move on to the tests.
A Note on Caching
In a nutshell, a cache is a component that stores data so future requests for that data can be served faster.
Generally, data is cached to reduce site speed and improve data fetching times. This is immensely useful in cases where a user frequently returns to a particular website. The site is cached and the browser doesn’t have to retrieve the entire site – it restores the cached version and receives the fresh information thus resulting in faster page load times.
Search engines take site speed seriously in their ranking
Nice to see another European WordPress team getting an investment. Congrats to Borek and his team in Prague. I hope larger investments in WordPress businesses in general become a more common thing throughout the world.
Anybody who has ran or developed a WordPress-powered site, be it a humble blog or something more complex, knows that it’s pretty easy to make undesirable changes. This can be either content-related or a change to the WordPress theme or plugin you’re running. While backing up is crucial, a primitive backup doesn’t always let you roll back to the exact point where everything was fine. Enter VersionPress, a Prague-based startup that offers version control for WordPress. The company essentially wants to create an ‘undo button’ for changes you make to a WordPress site, with software built on top of Git, the popular open source version control system. To help further develop its offering, VersionPress has picked up $400,000 backing from Prague’s Credo Ventures.
“WordPress is a great publishing platform but has certain drawbacks that affect almost any website powered by it,” VersionPress founder Borek Bernard tells TechCrunch. “One example is that if something breaks a site, be it a failed update or a human mistake, there is no easy way back. It’s like if MS Office had all the rich functionality but no undo button. It’s hard to imagine but WordPress is like that today, which we aim to fix.”
I'm a WordPress plugin developer, educator and entrepreneur.
I am the founder of CalderaWP. We make Caldera Forms, an awesome drag and drop, responsive form builder and many other awesome plugins. I am also a co-founder and developer for Ingot, an awesome A/B testing tool for WordPress. I also write a lot about WordPress and wrote a book on the WordPress REST API and am a core contributor to WordPress.
Besides WordPress, I'm really into music, science fiction and coffee.
Ask me anything...
BTW Find me on the interwebs here:
A pretty candid review of WP Engine by one of the most well-known affiliate bloggers. I kind of wish he hadn't turned it into an affiliate play, but that's really his style so it's nothing out of the ordinary.
When I first moved my hosting over to WP Engine I was highly impressed. They were very helpful, support took ownership of problems and site speed was incredible. As someone that has been in the game as long as I have it is rare to find a hosting company that provided the level of support they did.
But over the past 8 months things have really started to go downhill with WPEngine in a serious way. I have gone from singing their praises to everyone I meet to telling everyone to avoid them.
Here is an example of just some of the things they have done-
Deleting live customer data without taking a backup
Injecting a link to their homepage in my footer without permission
Lots of site down time/slow loading
Losing connecting to the server in the post editor
Disabled fulltext mysql indexing without notification – this broke my RSS feed costing 60% of subscribers
Repeat broken promises from their co-founder
Support is a rolling joke
If I could write a list of things that a web host should never do – WP Engine has done them all. They are no longer the hassle-free wordpress hosting experts they claim to be.
In this post I will share my WPEngine experience across the last 18 months and above all,
With left-pad removed from NPM, applications and widely used bits of open-source infrastructure were unable to obtain the dependency, and thus fell over. Thousands, worldwide. Left-pad was fetched 2,486,696 downloads in just the last month, according to NPM. It was that popular. To 'fix the Internet', Laurie Voss, CTO and cofounder of NPM, took the unprecedented step of restoring the unpublished left-pad 0.0.3 that apps required.
And so the internet broke.
People confirmed their biases:
And people got angry:
Everyone involved here has my sympathy. The situation sucks for everyone, not least Azer (who owes none of you ingrates a damn thing!). But reading the GitHub thread should leave you thoroughly exasperated, because this problem is very easily solved.
Bundle your code, even if it’s not for the browser
Just to recap:
left-pad was unpublished
Babel uses fixed versions of its dependencies, one of which (transitively) was left-pad
When you install Babel, you also install all its dependencies (and their dependencies)
Therefore all old versions of Babel were hosed (until left-pad was un-unpublished)
People blame Azer
The key item here is number 3. Suppose that instead of listing all those dependencies in package.json,