As many of you already know, WDS folks are regulars at the tech events around the world–particularly when it comes to WordPress. We love teaching, we love learning, and we love meeting people in our community. Recently, though, Lisa received an invitation to something unexpected, and it was an opportunity that she couldn’t pass up.
Lisa was invited to speak at the Design Bloggers Conference later this month! Now, this isn’t a conference focusing on web design, but on interior design. It does seem a little outside of our purview, doesn’t it? Considering the new reports that WordPress is hosting almost a quarter of the sites worldwide, it may not be as surprising as you (and we) initially thought!
In this post, I’ll show you how I handle AJAX in WordPress:
When I was just a little girl, I asked my mother, “What will I be?”
I used to think that the only jobs for women included only nursing, teaching, or being a mother. I had no clue that there would be something called the Internet, and that I would be making websites for it and teaching others how to code. Since its inception, the technology fields have always been under-represented by women, and there is a lack of positive female role models in the computer and IT Industry as a whole. One place where the balance is more equal is within the WordPress Community.
Have you ever wanted to add a filterable portfolio to your personal site to showcase your content? In this post, we’re going to include simple scripts for you to add to your existing theme to help make it easy to add a filterable portfolio to your project.
Tools you’ll need:
Custom Post Type UI has been around for the better part of five years and is one of WebDevStudios’ oldest plugins in the WordPress.org repo. It has amassed over 640,000 downloads and maintains a rating of 4.6 out of 5 stars.
Since its initial release, it has largely maintained the same user interface and has only had minor tweaks through its evolution. However, that consistency meant it hasn’t kept up with the evolution of the WordPress admin since the days of WordPress 3.0, including the huge change from WordPress 3.8.
As a result, I wanted to give the the plugin a UI overhaul for the next major release, and I hope the new version provides a better, more easy to use user experience for our existing and future users. I also used it as a chance to refactor the existing code and make it more maintainable and customizable by 3rd parties. Everyone wins!
However, I need beta testers to make sure the upgrade goes smoothly and no settings are lost in the transition from 0.8.5 to 0.9.0. I also need new users to make sure it’s usable and not confusing.
That’s where YOU come in!
Things I need tested by both current and new users include:
- Seemless migration from 0.8.x to 0.9.0. No behavior lost. The migration will be automatic, but making sure the provided settings match in the new UI needs to be checked.
- If you have existing post types or taxonomies registered by CPTUI 0.8.x, check that their behavior remains as it was before.
- Importing and exporting between sites using 0.9.0. This will be one of the new menu items available, and all of the data should be provided for you automatically–you just need to have a post type or taxonomy set up on one site, and not on another before clicking import.
- Get code functionality. This one should be familiar to you already from the previous versions, but we need it to provide all of the expected values when set, and not empty values when not set.
- General usability of the new UI. Is it more clear how to do things? Worse?
- If you have multisite, that needs a really good tire kick that I will be doing myself as well soon.
- Any bugs you find.
- Translation updates, if you’re fluent in more than one language.
There I was. Working on adding PHP docblocks to widgets.php in /wp-includes, like you do, when I came across this:
So I set about trying to figure out the appropriate
@since parameter to use. Do I base the
@since on when the
WP_Widget function was first added (2.8)? Or from when the time it was downgraded to a PHP4 compatibility wrapper for the
__construct function (3.2)? I decided to ask the almighty Ben Lobaugh, my dev lead, to see what he thought. And Ben says:
I think you should erase the PHP4 constructor as PHP5 is required by WP now and submit it in another patch.
Done! Patch created and ticket submitted. That was easy.
[Chris]…are you going to update [your] custom widgets to not use WP_Widget?
WHADDYAMEAN? Surely I’m not using some old PHP4 compatibility wrapper function!Continue Reading
As a Front-end WordPress Developer, I’ve become an avid reader of WordPress Tavern; their articles are always relevant to me and of a very high quality with just the right amount of new information. Their recently published article, 6 WordPress Things I’m Thankful For by Jeff Chandler is no exception, and got me inspired to ponder about what in WordPress I am most grateful for and write this article. The obvious answer that most people who I know would give is the community that surrounds WordPress, which I would definitely agree with. I have met amazing new friends and have felt a strong community of support and encouragement from my peers. But what about the application itself, the one software that all the fuss is about? It must be the marvelous piece of magic open-source code to support and inspire more smart and passionate group of professionals, business owners, and hobbyists to continue create amazing and increasingly bigger and more complex websites with this community-developed software.
To truly appreciate the grace and elegance of WordPress the application, you must first consider when web publishing was not so graceful; and most times, down-right clumsy. Around 1996, there was Geocities, and for a while that was the way for the average person to have any kind presence on the internet. There was a WYSIWYG page builder, or you could upload your own files via File Transfer Protocol (FTP). Tables were used for advanced layouts and obnoxious animated .gifs littered the entire webosphere. The worst part, however, was not the blink tag, but the enormous amount of black Times New Roman text on gray backgrounds that were displayed by most browsers then when a default font or page color was not specified. Not that there were many choices at the time. CSS, as we know it today, did not become widely supported by most modern browsers until 2004.Continue Reading
At the end of September, Matt Mullenweg published a blog post outlining his vision of Five for the Future. DradCast interviewed Matt at WordCamp San Francisco 2014, here’s what he had to say:
WebDevStudios is Dedicated to the Future of WordPress
Since the start of WebDevStudios, we have always been big advocates of giving back to the WordPress project and community. Over the years we’ve tried various official ways to contribute as a company, but have never figured out the best way to do it.
Are you a school administrator, municipality representative, or local government agency stuck wondering why you’re burdened with an antiquated, expensive and proprietary content management system that is simply impossible to manage at scale?
If that sounds like you, then you’ll be happy to hear that WebDevStudios And WP Engine are coming together to bring you a free event you don’t want to miss out on — NYC Happy Hour
Join us Thursday, December 4th (5PM-8PM EST) at the Marriott Marquis in Times Square.
UPDATE: This event has been postponed. A new date will be set in early 2015. Please register below to continue receiving event updates.
The NYC Happy Hour is a social gathering to chat WordPress with local leaders in education, and government. The event is focused around the large-scale use of WordPress in schools, and local agencies. We have some great speakers lined up to talk to you about their experiences working together to leverage the world’s most used (24% of the internet) content management platform.
WordPress has had no formal REST API. There is the crude XMLRPC, but we won’t go into the gory details of the past.
As part of Google Summer of Code (GSOC), Ryan McCue submitted a proposal for creating a formal JSON API to be included in WordPress core and therefore available to every WordPress.org install.
For those who may not know what a REST API is; it stands for Representational State Transfer. In short, it separates client from the server. Each request from any client contains all the information necessary to service the request, and session state is held in the client.