It's nice to see such a high profile site using WordPress. There is not a ton of content yet, but I imagine more will be added as time goes on.
The Obama Foundation launched its new WordPress-powered website today. The future presidential center, which will be located in Chicago, will manage projects both in the city and other places around the world. “More than a library or a museum, it will be a living, working center for citizenship,” President Obama said. “That’s why we want to hear from you. Tell us what you want this project to be and tell us what’s on your mind.”
The website integrates the Typeform service for collecting feedback from citizens on their hopes and dreams, as well as the people and organizations that inspire them.
WordPress developers were excited to see that the former President is using the WP REST API introduced in WordPress 4.7.
Oh hai WP REST API pic.twitter.com/EBGDexNwRA
— Daniel Bachhuber (@danielbachhuber) January 20, 2017
The custom theme for the Obama Foundation is built using ZURB’s Foundation as its front-end framework. It integrates the jQuery Cycle Plugin for galleries.
The website was created by Blue State Digital, an agency that got its start on the campaign trail and now focuses on serving causes and brands.
President Obama is the first president
This is good discussion of very old topic, if we should pay WordCamp Speaker. Look specially at the comments, here Josepha just started the discussion, participate if you are involve with foundation or organizing team.
It’s been many years since we last openly discussed the question of whether or not to pay for the travel and expenses of out-of-town speakers for WordCamps. I’ve seen a few discussions around (and have had quite a few with people, myself), so I thought it was time to have a post about it. The Background Info
Speaking at a WordCamp has always been considered a volunteer contribution. In the same way that developers donate their time writing a patch for core, speakers donate their time sharing knowledge with the greater WordPress community. If a speaker chooses to submit their talks to WordCamps where travel would be required, the expectation is that they will cover their own expenses.
The global community team stresses a local focus for WordPress events, to not only keep costs manageable, but also to foster that sense of community that makes our project so unique. We ask organizers to do the following things:
Focus on having primarily local speakers at your event
Choose high quality speakers (and presentations) over quantity
Crowdsource potential speaker suggestions from your Meetup members
The Current Info
The conversations I’ve been seeing/having lately often are
Rather than just correcting its licensing mistake, Wix over-compensated and introduced other issues when it created a new license. The process is turning out to be a learning experience for Wix. Good reporting and analysis by Sarah Gooding.
In October 2016, Matt Mullenweg called out Wix for using GPL-licensed code from the WordPress mobile app and distributing it in its proprietary app. After identifying a path for Wix to comply with the license, Mullenweg confirmed he would be willing to go to court to protect the GPL. Wix CEO Avishai Abrahami’s response to the allegations failed to address the issue of licensing, dodging the question with references to other open source contributions. Abrahami seemed to indicate that Wix would open source its mobile app but was not clear whether it would be GPL licensed:
“We always shared and admired your commitment to give back, which is exactly why we have those 224 open source projects, and thousands more bugs/improvements available to the open source community and we will release the app you saw as well,” Abrahami said.
The Wix Twitter account also gave the impression that the entire app would be released under the GPL:
@yairwein We'll release the code on Github, where we also shared our previous projects: https://t.co/FBhp2Kd5wn
— Wix.com (@Wix) October 30, 2016
Publicly communicating these intentions bought the company time to educate its developers on the
It seems that Wix is spending tons of money to advertise their platform.
Wix has released the first of its teaser ad series for Super Bowl LI, coming out strong with actors Jason Statham and Gal Gadot in an action-packed fight scene. The spot is a departure from the brand’s Super Bowl 50 ad which was a joint campaign between the web development platform and the “Kung Fu Panda” movie franchise (although both campaigns do contain a certain element of martial arts).
Wix launched the campaign on Facebook and YouTube Live last night at 6:00 p.m. ET — releasing the video simultaneously on both platforms. According to an announcement from Wix, its Super Bowl LI campaign will include a series of teaser ads leading up to its official 30-second Super Bowl spot.
“We are so excited about this campaign because this time we are telling our own story,” says Wix CMO Omer Shai in the announcement.
The CMO says the campaign is about more than just the commercial, “It is an ongoing narrative about Wix and our customers, and our message about always enabling our users in a world that is often disruptive so that they can be heroes.”
The ads are directed by Louis Leterrier, the same director behind the “Transporter”
Interesting: Ghost is offering $45k journalism development program to "build exciting, sustainable publications”. Although not as "big" as Medium, it's an interesting move in the same space as WordPress.
We believe journalism and its role in creating an informed society is one of the most important ideas in the world. It impacts everything from what we think, to what we buy and who we vote for. Ghost is a fully open source platform for independent publishers, founded three and half years ago after a runaway $300,000 Kickstarter campaign.
Since then it has been downloaded over 1.2million times by thousands of publishers from Square, Tinder and Zappos, to Vevo, Mozilla and many others. Last year, Sir Richard Branson called it "incredible" and "a very important idea".
Now, as our technology has grown and been successfully used by so many personal and company blogs, we’re turning our primary focus to where our heart and our mission has always really been: Journalism.
Our goal for this year is to find three fantastic new publishers to work with and help them grow their audiences throughout 2017, as we build out these features (and others) explicitly around their needs.
In addition, we'll be offering up $45,000 in Ghost(Pro) credit, along with access to our internal tools, data, and technology partners.
We care deeply about making a difference. Our greatest ambition
SiteGround was one of the first hosts to offer Let's Encrypt SSL certificates with their shared hosting plans. It is very easy to setup if you are starting a new site. Now they pushing forward plans to make it even easier.
SiteGround is now auto-issuing Let’s Encrypt certificates for every domain hosted on its shared servers. The company has also begun issuing and installing certificates on new accounts automatically after customers register domains or direct new domains to SiteGround’s servers. This also includes add-on domains added in cPanel. The certificates are also auto-renewed as long as the domains are pointed to the host’s servers. “Since the launch of Let’s Encrypt our customers have installed nearly 40,000 such certificates,” said Hristo Pandjarov, WordPress specialist at SiteGround. “This is less than 10% of the 500,000 domains we host. Together with the paid certificates we may say that 15% of the domains we host were using the HTTPS protocol before we started the auto-issuing procedure.”
SiteGround is a sponsor of Let’s Encrypt and one of the first to auto-issue certificates to self-hosted WordPress customers. Let’s Encrypt passed 20 million active certificates in 2016 and the pressure is on for more sites to adopt SSL in 2017 with Google marking insecure sites in Chrome and using HTTPS as a ranking signal.
As we start looking at the editor from a technical perspective it’s important we identify the main obstacles and requirements we face before we start conjecturing solutions.
Wow, that’s quite an essay on the content editor. We’ve been doing this for a long time and know the lay of the land. We even built a WYSIWYG editor we can’t give up (we tried for two years). First in praise of the WordPress editing experience: the Media Library has grown to be very powerful and easy to use. It’s awesome. We were delighted to retire the original image editing module we were using last year and fully integrate the Media Library. Still what are the issues with WordPress content editing which drive us to maintain a separate WYSWIYG editor?
Hint, it’s not the money, thousands of hours have gone into this purely GPL and non-commercial product. It’s not boredom. We have too much to do in three lifetimes and very short weekends already.
It’s not shortcodes. Shortcodes are great and reliable ways to easily and visibly add content to posts. As soon as you start trying to hide the pieces, reliability falls through the cracks. It’s why lawyers still use WordPerfect.
Google is pushing forward with its plans to promote SSL. This article discusses what WordPress site owners can expect and what users might see in their browsers.
On approximately January 31st of this month, version 56 of the Chrome web browser will be released. There is a significant change in the way it displays websites that are not using HTTPS, also known as SSL. This change may confuse your site visitors or surprise you if you are not expecting it. Starting with the release of Chrome 56 this month, any website that is not running HTTPS will have a message appear in the location bar that says “Not Secure” on pages that collect passwords or credit cards. It will look like this:
This is the first part of a staged rollout that encourages websites to get rid of plain old HTTP.
In an upcoming release Google Chrome will label all non-HTTPS pages in incognito mode as “Not secure” because users using this mode have an increased expectation of privacy.
The final step in the staged rollout will be that Chrome will label all plain HTTP pages as “Not secure”. It will look like this:
So, once again, starting on approximately January 31st of this month, any page on your website that is non-HTTPS and has a password form or credit card field will be labeled as “Not secure” in the location bar by Google Chrome.
Founder of Theme Hybrid. Co-author of the book Professional WordPress Plugin Development. An active WordPress community member.
I started messing around with WordPress back in 2007. Justin Tadlock was already an active member of the, way less crowded back then, WordPress community. 10 years later, I asked Justin if he’d be interested in answering 10 questions. These are his answers. Hi could you tell us a little about yourself and background?
I grew up in Alabama and am now currently living here. I earned a B.A. in English from Auburn University with primary concentration in creative writing and a secondary concentration in journalism. I’ve worked all sorts of jobs like grocery store stockboy, field hand who picked watermelons and baled hay, English teacher in Korea, and all kinds of other things.
My interests are far and wide. I garden and hope to run my own farm one day. I plan to publish at least one best-selling novel. I’m currently relearning how to write using the Spencerian Cursive method. I’m also just starting to use fountain pens, which are a joy to write with (no idea why ballpoints ever became more popular).
When did you first stumble upon WordPress?
I first started using WordPress in 2005. I had given it a try once before that. Primarily, I was looking for something easy
Jason has rebranded Postmatic to Replyable a much better word and is back with a snack — I meant a WP SaaS-based Commenting service. Cool beans! Try it out.
What makes Replyable different from it’s big brother, Postmatic? Postmatic is a full engagement platform for WordPress with a focus on delivering content to users where they are and making it easy for them to talk about it. Replyable focuses only on letting them talk about it.
Want to see it work?
Click here to spawn a new email message. Write something. Hit send.
Your email will be converted to a comment and show up down there in a few seconds time.
The full version of Replyable is a bit more complicated (think opt-ins etc), but this will give you the idea of how fun it is!
Here's a new video tutorial on adding a Facebook pixel tracker using a plugin.
Have you closed the Amazon website before buying the item you were looking at, only to have it reappear in your Facebook feed? That’s powered by a Facebook remarketing pixel, and in today’s tutorial, I’m going to show you how to add that Facebook tracker to your WordPress website. It’s a fairly easy process, and can become quite powerful to help sell your product — maybe. Before we dive into learning the ins-and-outs of configuring this within your WordPress website, let’s talk about remarketing from a high-level.
Why Facebook remarketing?
Now more than ever, getting people to visit your website feels like a monumental task. Gone are the days of “build it and they will come”, or increase your traffic by sprinkling in a few keywords into your title tag. Content marketing is at the top of everyone’s game plan, and creating great content is key for that plan to become successful.
Imagine a situation where you’re using your blog as the cornerstone to driving organic traffic to the site. You spend hours creating content, planning out a content roadmap, and shaping that storyline around why people should trust & buy from you.
Post script to the Wix/GPL #drama from last year. Wix has now forked from the editor WordPress originally forked from, which has an MIT licence, so basically everything is now fine.
In late October 2016 Matt Mullenweg, the co-creator of the WordPress blogging platform attacked the company Wix for not complying with the GPL License. The rich text editor in their competitor, Wix, app was using GPL code - which was itself a fork of an MIT licensed code. The problem was that the Wix app was using a GPL licensed library released by the WordPress project, that would have essentially meant that the entire Wix mobile app's source code be released. This is what lead Mullenweg (rightfully) to announce:
This explicitly contravenes the GPL, which requires attribution and a corresponding GPL license on whatever you release publicly built on top of GPL code. The GPL is what has allowed WordPress to flourish, and that let us create this code. Your app’s editor is built with stolen code, so your whole app is now in violation of the license.
- Wix and the GPL
This then lead to a minor shit storm among the GPL and WordPress faithful against a commercial entity abusing Open Source code. As things usually go, this calmed down in a few days and people forgot about it. What went largely unnoticed was the fact that, while Wix was technically breaching the GPL license, the WordPress
A good collection of how-to steps to resolve WP's dreaded white screen of death.
Is it as scary as the name sounds? Well, the only thing that dies is your morale when you figure that you don’t know exactly what to do when the White Screen of Death strikes.
Sure, it is an error which makes most of us exasperated, and even get us all panicky, because why not? You don’t get any error messages when it takes over your life, which makes it horribly difficult to identify the problem and trouble shoot.
But once you are able to discover the problem, and how to tackle it, you are sortedJ And here we are going to show you just how you can sort this super annoying problem.
This article is constantly updated with new tips and tricks, so you can be rest assured that what you are seeing here is the latest info. Our experts keep updating the article through their own experiences and trial-and-error methods.
Here’s everything we’ve got in this article at a glance:
What is White Screen of Death?
So what is this big super annoying problem we are talking about? What is White Screen of Death?
It’s an error most of the users face where the user feels helpless and is welcomed by a blank screen. What it does is this:
It makes your website look like a blank
Aaron is a fantastic guy, I'm looking forward to seeing him make an even larger impact on WordPress. Curious why Nikolay stepped down, tho.
Aaron D. Campbell, WordPress Core Contributor at GoDaddy, is replacing Nikolay Bachiyski as WordPress’ Security Czar or WordPress Core Security Team Lead. The role was created in 2015 to provide more structure and focus around incident responses. According to Campbell, “The responsibilities of the position include, organizing the security team and making sure all security concerns and reports get triaged and ultimately fixed, coordinating the security side of releases, and being a point of contact for any security related things that need one.”
Matt Mullenweg, co-creator of the WordPress project, thanked Bachiyski for being the first to accept the role and putting the foundation in place for future team leads, “This is also a good time to thank the dozens of volunteers who participate in the security group, and the researchers and reporters who bring issues to our attention,” he said.
Campbell says he plans to finish what Nikolay started by getting WordPress.org onto HackerOne, “Nikolay did a lot of work around expanding our team as well as getting the foundation laid for moving over to HackerOne,” he said.
“We aren’t quite ready
The editor will be a big focus in 2017, so let’s chat about what makes a great editor. Perhaps it’s good to look at what’s there, and compare that with the goals we mean to achieve.
The editor will be a big focus in 2017, so let’s chat about what makes a great editor. Perhaps it’s good to look at what’s there, and compare that with the goals we mean to achieve: The editor will endeavour to create a new page and post building experience that makes writing rich posts effortless, and has “blocks” to make it easy what today might take shortcodes, custom HTML, or “mystery meat” embed discovery.
Here’s what the editor looks like today, with everything enabled:
Obviously not all of that is ever shown to users, but a lot of it is. Even then, it’s not immediately obvious just how many things you can actually embed right out of the box in WordPress, which is what mystery meat embed discovery refers to.
And so when looking at how to improve the editor to both improve but also surface the wealth of features already there, we’ll need to add new UI. To balance that out in an already busy configuration, we need to find a way to also reduce and revisit existing UI, so we don’t end up with something overwhelmingly complex. That could mean combining where we can, minimizing where we can, deprioritizing in places,
Rachel shortly discusses the 2 main risks we run when we move our words to Medium, our photos to Instagram and our code to CodePen. She has decided to bring her content "back home" in 2017.
“In order to expand audience awareness and redefine Possible, there have to be places where these new capabilities exist; and lacking a client willing to take the chance that the audience will be equipped to do so, we need to provide the environment so the audience equips itself and creates that demand to use newer standards. I propose, therefore, that the environment already exists and it lives in the collective personal sites that don’t give a damn about return on investment.” Personal sites, our blogs, these were once our playgrounds. My own site was the first place I added rollover images, CSS for fonts, tried out a “table free” design. I wrote about the web, surrounded by my own experiments with the web. We all did, and it was only in reading those words from 1999 that I realised there was more to owning your own content than simply not publishing your words elsewhere.
As we move our code to CodePen, our writing to Medium, our photographs to Instagram we don’t just run the risk of losing that content and the associated metadata if those services vanish. We also lose our own place to experiment and add personality to that content, in the context
This has become one of my favorite plugins, especially for setting up new blogs that need good looking stock photography.
Gone are the days of those generic stock photos of “young professionals” smiling at fake presentations around a corporate meeting room. We all know that’s not what a busy work day looks like, anyway. If you’re still stuck in the stone-age of stock photography, or simply don’t know where to look, you’re in luck today. Adding free images to your WordPress blog posts just got a lot easier thanks to Instant Images. It’s a free plugin that connects to popular photography sharing website, Unsplash.
Using Instant Images
I use Instant Images here on PluginTut, and on my other blog The Matt Report.
After you install and activate the plugin, you’ll be able to access the Instant Images search box in two places:
Media > Instant Images
In the editor > Instant Images button in the toolbar
Search results are fast, and at the bottom of the window, you’ll be able to access “quick-load” features like newest, oldest, and most popular photos. It’s a joy to use.
Search results are quick and easy, as well, returning roughly 20 images per search with a “load more” button depending on your search term.
Tom McFarlin to Launch Marketplace for Blogging Plugins, Finds New Maintainer for WordPress.org Plugins
A good article by Sarah Gooding about the adoption of Tom McFarlin's plugins from the WordPress repository. Tom plans to open a blogging plugin marketplace and wanted to make sure his old plugins had a good home.
Tom McFarlin to Launch Marketplace for Blogging Plugins, Finds New Maintainer for WordPress.org Plugins
Daily blogger and plugin author Tom McFarlin has found a new maintainer for five of his WordPress.org plugins. Within two days of putting the plugins up for adoption, McFarlin announced that Philip Arthur Moore will be taking over Category Sticky Post, Comment Tweets, Single Post Message, Tag Sticky Post, and Tipsy Social Icons. Moore, who is currently working as CTO at Professional Themes, has inherited roughly 10,000 users overnight in the transfer of maintainership. WordPress.org plugin adoption stories are few and far between. The most common scenario for an orphaned plugin is to languish in the directory until it disappears from search results (with the exception of exact matches) after two years of no updates. In McFarlin’s case, he was looking to tie up some loose ends before shifting Pressware’s focus to launching Blogging Plugins, a marketplace for extensions that streamline WordPress for regular bloggers.
“Last year, I had a few false starts when trying to launch what was originally called Pressware Plugins,” McFarlin said. “Fast-forward a few months and we’re going to focus on something called Blogging Plugins. We already have two free
Give is more than a great tool for accepting donations, it's a way to control your donation process and data -- you know, like WordPress.
You might know me from church, or from academia. You might only know me from within the world of WordPress. What you might not know is how both of those worlds have collided in such a wonderful way in my current vocation. I’m now a partner, co-author, and Head of Support and Community Outreach at GiveWP.com. Give is a WordPress plugin designed for one thing: to empower you to get more donations on your WordPress website. Over the past few years, I’ve been on a very personal journey from changing my aspirations of being a University Professor, to … something else. I didn’t really have a plan or a vision for what that “something else” was. I just knew that Professorship wasn’t for me for a wide variety of reasons that took a long time to become real for me.
I didn’t plan to become a partner at our company. It kinda just happened. But as I look back I realize that it’s a better fit than I could have imagined, primarily because it allows me to synthesize a couple important things for me:
Personal coaching/teaching/training as a supervisor and a support technician
Empowering GOOD in the world through our platform
Having insight into
It is not hard to glean live lessons from the reddit post. Chris shares advice for the person who spent a year developing a WordPress theme and could not sell it. The WordPress thread on reddit is: https://www.reddit.com/r/Wordpress/comments/5mvz02/did_i_waste_a_year_of_my_life_developing_a/
This is an open letter to the and couldn’t sell it anywhere. An Open Letter to Chris
My name is Chris too. And that’s not the only thing we have in common. I’ve been in the exact same spot you’ve been in. And the good news, right at the front end of this post, is that the answer is that you’ve not wasted your life. In fact, this may have been the very best year of your life professionally, if you learn the right lessons from it.
Unfortunately, much of life is filled with complex relationships between cause and effect and as a result, we often take away the wrong lesson from a situation. We get confused and make promises to ourselves that aren’t the right ones.
“I’m never going to create another WordPress-related product again. The competition is too tough.”
So instead of hoping that you’ll take away the right lessons, let me share with you, outside of the Reddit set of comments (some of which are ridiculous), why I think this may have been the best year of your life.
It’s always great to figure out something you don’t understand with whatever resources are around.
There are tons of folks who don’t
One of the most intriguing new features announced in this release, is the integration with WordAds, WordPress.com’s advertising program.
Jetpack is starting 2017 with a major release that is heavy on enhancements and improvements. Version 4.5 includes more than a dozen new shortcodes and widgets, along with revamped support for VideoPress. One of the most intriguing new features announced in this release, however, is the integration with WordAds, WordPress.com’s advertising program. Jetpack users are required to be on the Premium plan ($9.00/month or $99/year) in order to sign on with WordAds. The feature is then available within the Engagement tab along with settings for adjusting ad placement.
Eligibility for WordAds was previously limited to sites that had thousands of page views per month, but this requirement is lifted for those who have purchased a Premium or Professional Jetpack plan. Unlike Adsense, which pays for clicks, WordAds pays based on the number of impressions combined with many other factors. According to Derek Springer, an Automattic employee who has worked on WordAds for several years, the traffic requirement was given to set earnings expectations and to ensure support resources were adequately available.
How Much Can Publishers Earn through WordAds?
It’s difficult to to gauge how much
Jeff Paul, a deputy release lead for WordPress 4.7, offers a bunch of ideas for ways you can begin contributing to WordPress.
Me: Do you regularly use WordPress? You: Yes, I love it, it’s fantastic!
Me: Have you ever thought about helping contribute to WordPress?
You: No, I am not a developer.
Me: Well, good news, you do not have to be!
You: Ok, tell me more…
Whether you have considered it or not, I am so certain that you CAN contribute to WordPress that I will personally offer to help you find a way to do so. I will outline some options below, but feel free to reach out to me directly and I promise to help!
But first, a little background on me…
I graduated from college in 2001 with a degree in Computer Science, but have not spent any significant time coding since then. I have held roles in project management, product management, and team and customer management. The way I tell it, no one would realistically hire me these days to do development. And yet, there has been a fantastic opportunity for me to help contribute to WordPress as a deputy release lead on WordPress 4.7. While this was a significant time commitment for me, there are ways you can contribute with minimal time commitment.
Now let us focus on how you could contribute…
I am going to give you some options to describe
Here CodeInWP is sharing their finding from WordCamp US i Philly last month. hey spoke to multiple people about their thoughts and expectation about 4.8 and created this roundup.
I should probably add a little context before we jump into this one and talk “our hopes and fears for WordPress 4.8.” This article is not exactly what it looks like. Everything started back in December when I and the rest of the team traveled to Philadelphia to take part in 2016’s WordCamp US. Getting there was a big deal for us so we wanted to make the most out of the whole experience. One of the ideas was to meet some of the WordPress people who we only knew online, and do speed interviews with them.
This was a success and a failure both at the same time.
Let’s start with the success. First off, I want to thank everybody who took part and was kind enough to push their shyness away and talk with me in front of the camera. Yes, we filmed the interviews, professional and all, with separate tracks for video and audio. It was supposed to come out right after the conference, and … this is where the failure part comes into play.
As it turned out, the SD card that held the audio track was corrupted, and there was nothing that could be done about it. And we tried … we even contacted two separate data recovery firms. Both said the card was doomed.
WordPress 4.7.1 is now available. Please update immediately as this is a security release for all previous versions.
WordPress 4.7 has been downloaded over 10 million times since its release on December 6, 2016 and we are pleased to announce the immediate availability of WordPress 4.7.1. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.7 and earlier are affected by eight security issues:
Remote code execution (RCE) in PHPMailer – No specific issue appears to affect WordPress or any of the major plugins we investigated but, out of an abundance of caution, we updated PHPMailer in this release. This issue was reported to PHPMailer by Dawid Golunski and Paul Buonopane.
The REST API exposed user data for all users who had authored a post of a public post type. WordPress 4.7.1 limits this to only post types which have specified that they should be shown within the REST API. Reported by Krogsgard and Chris Jean.
Cross-site scripting (XSS) via the plugin name or version header on update-core.php. Reported by Dominik Schilling of the WordPress Security Team.
Cross-site request forgery (CSRF) bypass via uploading a Flash file. Reported by Abdullah Hussam.
Cross-site scripting (XSS) via theme name fallback. Reported