Is there a plugin that allows me to install/update #WordPress plugins direct from #GitHub?
There is no shortage of advice when it comes to which tools software companies should use to run their businesses. We’ve all come across numerous “Top 100 resources for startups”-type posts at least once as we Google our way to entrepreneurial success. But after reading just one of them, it’s not hard to go from “I have no idea what’s out there” to… Read More
Automattic announced that they’re launching free HTTPS for all custom domains hosted on WordPress.com. WordPress.com has supported encryption for WordPress.com subdomains since 2014, but now it’s being expanded to over a million custom domains.
The company says users will see secure encryption automatically deployed on every new site within minutes.
“We are closing the door to un-encrypted web traffic (HTTP) at every opportunity,” writes Automattic’s Chief Systems Wrangler.
As he notes, encryption provides more than security.
“Protocol enhancements like SPDY and HTTP/2 have narrowed the performance gap between encrypted and un-encrypted web traffic, with encrypted HTTP/2 outperforming un-encrypted HTTP/1.1 in some cases,” he writes.
Earlier this year, Moz found that HTTPS URLs made up 25% of page-one Google results across 10,000 queries.
The post HTTPS Launched For All Custom Domains On WordPress.com appeared first on WebProNews.
WordPress.com is adding HTTPS support for all its blogs. If you have a custom domain or have a blog under the wordpress.com domain name (like bestcrabrestaurantsinportland.wordpress.com), you’re good to go.
While many social services like Facebook and Twitter have supported HTTPS for a while now, WordPress.com was still lagging behind for custom domain names.
Since 2014, WordPress.co Read More
Shopify announced the launch of new themes and a new plugin for WordPress to make it easier to sell on WordPress sites.
Both the themes and plugin are free. You can use them to add products to any of your pages or blogposts without leaving the content management platform.
“As usual, you’ll still manage all of your pages and posts in WordPress, but you’ll have Shopify to manage everything else: payments, secure checkout, shipping and fulfillment, inventory, and taxes—all the hard things about selling online,” says Shopify’s Daniel Patricio.
The themes are called Hype by Themezilla, Simple by Themify, and Pulse by Ultralinx. You can see them below in that order.
“Installing the plugin adds the ability to easily drop products with buy buttons into any sidebar, page or blog post,” says Patricio. “Plus, you’ll get a slick pop-out shopping cart for your site, so customers can purchase multiple products at once.”
While the plugin is free to Shopify users, it does cost $9 a month for a “lite” Shopify plan. The plan will also get you Facebook Shop, Shopify POS for iOS or Android, access to the Shopify app store, and 24/7 support.
Images via Shopify
All our plugins, including our Yoast SEO plugin, are open source. In the true meaning of open source, we don’t just open the source code, other people actively contribute to its betterment. We actively work on getting other people’s patches in and reserve time on every release to make sure we can handle community patches. We love doing that, but we also love contributing to other open source projects, most notably, WordPress. I thought I’d do a write up of the WordPress core contributions we’ve done over the last 9 (!!) years.
WordPress core contributions by team Yoast
Articles like this article on WPTavern about WordPress 4.4 and who worked on it (and the pie chart I nicked from it shown below) make me proud. We pride ourselves in contributing to WordPress core and enabling some people to do a lot of WordPress core work. I’ve been a core contributor to WordPress myself since version 2.3. That’s almost 9 years ago, and I have contributed to almost every major version since, missing only 4, marking 16 releases so far.
This pie chart shows the percentage of commits to WordPress 4.4, done by committers, grouped by their employer.
So, while I started before Sergey did, Sergey has since surpassed me completely. He was the deputy release lead on 4.4, and responsible for tons and tons of work on both core and Meta (the wordpress.org site and infrastructure). We will gladly pay for his time to work on WordPress core and meta for years to come.
Several other members of our team have been contributing for quite a while. Andrey (aka Rarst), who regularly writes on our Dev blog now and mostly spends his time working on Yoast SEO, has been a core contributor since 3.4. Of our Dutch team, Anton is probably most notable, having contributed to 5 releases, with Jip a close second with 3 releases. Taco does quite a bit of work in the i18n community and was noted as a contributor on two releases so far. Both Anton and Taco were at the most recent WordPress community summit. Caroline got her first patch in on WordPress 4.4 and 4.5 will have Andy‘s first patch.
We’re actively looking to hire more experienced WordPress developers, so if you like working on core and would like to work on some of the most popular plugins for WordPress as well, be sure to check out our jobs section. While most of our team is in the Netherlands, we’re willing to make an exception for seriously experienced developers. In fact, we’re looking to hire a full time WordPress core developer, who can, in part work on some projects we have in mind. Let me outline those projects below:
Specific WordPress core projects
Next to all the work we’re already doing, we’re looking at how we can sponsor people for a few specific projects. We’ve got three particular projects in mind that we’d gladly pay someone to do. We’d like to hire a core developer and let him / her do this, or we’ll hire someone for the individual projects. Let me run through the three things we’d like to see happen most right now:
We’ve got some ideas around this which we’ll write up on our dev blog in the coming month. The current practices lead to tons of conflicts, something we’d like to fix in a more consistent way.
XML Sitemaps in WP Core
We’d like to bring XML sitemaps to WordPress core. This is a project near and dear to my heart. When Jetpack recently added an XML sitemap module, some people on Twitter were saying “Joost/Yoast won’t like that”. Well, Joost actually does like that. XML sitemaps are now truly a commodity. Thus, they should just be in core. Our own XML sitemaps module in Yoast SEO is too tightly integrated with our own code right now to easily be moved into core, but we’ve got some very good ideas on building a module that would work, for everyone, on top of the new REST API.
Think these ideas are cool? Want to work on them? Well get yourself to our jobs section! Have other remarks? Leave them in the comments!
The upside of being at a conference in a language you only speak a tad bit is that you get to meet and talk to all kind of people that have the same ‘problem’. WordCamp Paris had about 470 visitors, and I’m guessing 440 of them are native French. Don’t get me wrong, I like speaking French with French people, but it usually takes up to two or three days before I can keep up with the speed at which they talk. It’s like WP Rocket on acid. Luckily we ran into Bénard on the evening before the congress. This English-speaking Frenchman is always laughing out loud and that basically set the mood for our days in Paris.
Language barriers are real
Regardless of that we all speak WordPress, language barriers are real at this conference. I was at a sponsor booth. It had a huge bowl of snacks to lure people to their stand, and I walked up and said “So, everybody is coming to your booth for the snacks, right? How’s your WordCamp been so far?” The guy frowned and shrugged, looked at his shrugging colleague and I simply decided to walk to the next booth, with our friends Val and Joško of Sucuri. Very nice meeting the two of you!
The thing is, that we foreigners try to blend in anyway. We make it easy for the inhabitants of the country we are visiting. But we do like to talk to others that speak a language we do as well. And these conversations might be even more useful. We had a great lunch with Chris, talking about (WordPress) business. We hang out with Rarst to talk about plugin development, shitty bug reports and more. We talked about WordCamp Torino with Francesca and talked to Petya about WordCamps and WordPress in general. We caught up with a lot of people, which in the end is equally valuable to listening to all the talks.
Hanging out with other travellers
Friday evening we had a nice walk and dined in a very small, family-run restaurant called Le Cévennes. Robert and Heinz from Inpsyde joined Rarst, Taco and me and we had a really nice time talking about France, about home and WordPress in Germany.
We joined the rest of WordCamp Paris at the party boat where the after party was. We had a nice conversation with Caspar who works at WP Media these days, for instance. We briefly met James from Ireland. We obviously had a beer with the always friendly Kristof from Belgium, and yes, Kasia, WordCamp Poland sounds like a blast WordCamp is about the people.
Drupal meets WordPress
On Saturday, we tried our best to understand the first talk by Claire Bizingre about accessibility, as Taco and both value the subject. You never know what a talk like that will bring, even at 9 in the morning. Claire pointed us to some automatic testing tools like Opquast Desktop and aXe DevTools. Although we sometimes had a hard time keeping up with the French words, luckily most slides told her story on their own. You don’t always need to talk to understand each other.
Later on we met the very enthusiastic Léon Cros, who just did a talk about Drupal, and we talked about Open Source and why a Drupal guy was attending WordCamp Paris. He actually just felt like attending a WordCamp, found out they were having one at a ten minutes walk from his home in Lyon, attended and got asked to talk at WordCamp Paris. We discussed similarities in the communities and how we can learn from each other.
Right before lunch, we ended up at the Jetpack booth, talking to Cécile Rainon and the others of Jetpack. It seems our plugin is the number one requested plugin for WordPress.com. It only seems logical. WordPress.com is packed with a lot of all the other good stuff website owners need, and we’re in a high demand niche. It makes sense, as we offer an all-in-one SEO solution. Nevertheless, it was very nice to hear.
Paris, je t’aime
That pretty much rounds it up. We ended WordCamp Paris by joining a lot of the people mentioned above for a nice dinner and drinks and strolled back to the hotel for a good night sleep. We had a nice breakfast with Val en Joško in our hotel Eiffel Seine the next day and took the Thalys back to the Netherlands, where I’m wrapping up this post.
Bottom line: nous parlons WordPress. We obviously don’t speak the same language all the time, but just being here, talking to loads of people, making new friends, made WordCamp Paris 2016 very valuable to me.
Wishing I was at #FeelingRestful to talk/learn about, IMHO, the most exciting changes in #WordPress since CPT/3.0.
At the end of last year, a new HTTP status code saw the light. This status code, HTTP 451, is intended to be shown specifically when content has been blocked for legal reasons. If you’ve received a take down request, or are ordered by a judge to delete content, this is the status code that allows you to indicate that. The upcoming Yoast SEO Premium 3.1 release will have support for this new status code, allowing you to set a HTTP 451 status code for pages.
What does HTTP 451 mean?
The HTTP 451 header is introduced with the specific meaning of making it explicitly clear when content is blocked for legal reasons. Or, in the wording of the official draft:
This status code can be used to provide transparency in circumstances where issues of law or public policy affect server operations.
While the end result is the same as for instance a 403 Forbidden status code, this status code makes it much clearer what is happening. It might make you search for something just a little bit deeper. The original idea stems from this blog post which is worth a read.
How to set an HTTP 451 header
There are two ways to set an HTTP 451 header:
Deleting the post or page
In the upcoming Yoast SEO Premium 3.1 release we’ve changed what happens when you delete a post or page. You will now get the following notice:
The link underneath “Read this post” links to my earlier article about what to do when deleting a post or page. Because we’re assuming that most of the time when you delete content, it has nothing to do with a court order (we sure hope so), we haven’t added the 451 option here.
Creating a header without deleting the post or page
You can also just keep the post or page alive, which is especially useful if the court order, injunction or whatever it is that is forcing you to block the page, has a time restraint. Simply go into the redirects screen of Yoast SEO and create a 451 header for that specific URL:
An HTTP 451 template file
Along with the changes that allow you to set a 451 HTTP header, we’ve also created the option to have an HTTP 451 template file in your theme. It’s as simple as copy pasting the 404.php file in your theme to 451.php and modifying the content to have a good message.
I honestly hope you’ll never need this HTTP error, but if you do, you know now that you can do the right thing, provided you’re using Yoast SEO Premium!