My first Calypso Pull Request

Today was my first ever pull request to Calypso, the Javascript re-make of WordPress.com.  Even though the pull request ended up being a duplicate and therefore not getting committed into the master branch I think this was a good step 🙂 Before today I was nervous and intimidated about trying to contributor to Calypso and after going through my first Pull Request I think it broke the ice for me. Continue reading “My first Calypso Pull Request”

Contributing to WordPress Core

I have been wanting to become more involved with WordPress core by contributing code or documentation but it has been a little bit more overwhelming than I first thought.

At the time of writing this post I would not consider myself an active contributor but rather someone who is jut staring out trying to become a great contributor.  I am not really sure how to do this but I will share what I have learned so far so maybe you can not be so overwhelmed. Continue reading “Contributing to WordPress Core”

Is Atom a viable IDE?

I just came across Atom created by Github and I thought, wow what a great open source IDE let me see if I can use this instead of Coda 2.

The only thing is that it’s not going to easily replace Coda 2 or any other premium IDE right now, but even saying that it is a great tool to use 🙂 Continue reading “Is Atom a viable IDE?”

Headless CMS and the WordPress API

The WordPress 4.4 release is the beginning of the WordPress API and from there developers have been determining how to best use this new API that is being inserted into core over the coming releases after 4.4. A Headless CMS using the WordPress API was one of first applications of this new API and probably the best one. Continue reading “Headless CMS and the WordPress API”

How To get a WordPress Widget ID for Multiple Instances

Supporting Multiple Widget Instances

Just recently I was developing a WordPress widget, and as I began coding of all my use cases I realized that I needed to be able to support multiple widget instances.  Supporting multiple widget instances is not a big deal, unless you plugin depends on knowing the widget id from the front-end.  By this I mean after your page has loaded, you need to perform client-side scripting that depends on knowing the id of each widget instance.

Where is the Widget’s Instance ID stored?

/** @see WP_Widget::widget */
function widget($args, $instance) {
    echo $this->id;
}

Continue reading “How To get a WordPress Widget ID for Multiple Instances”

WordPress General Plugin that is Open Source on GitHub

Open Source WordPress Plugin for the Community

As a WordPress plugin developer I understand the struggles that all developers face.  Whether you are a beginner or advanced WordPress plugin developer I hope that this general plugin will help you start your project.  The main reason I have created this WordPress general plugin repository is to give you, the developer, a base to work off of.

Get it on Github

I am constantly improving this general plugin, but please send me pull requests or fork it as you want to help create a great base plugin for everyone to work from.  So check it out on Github!

Comment below with input on how to improve this general plugin.

Include Builtin scripts from WordPress using wp_enqueue_script()

Since we already showed you how to Include Javascript and CSS files through your WordPress Plugin, this post will be about how to include builtin scripts from WordPress. Why would we use these pre-registered scripts?

Two Reasons Why to use Builtin scripts from WordPress

There are two main reasons why using the pre-registered scripts is beneficial. First, this method will help to prevent jQuery conflicts. Second, it is a lot easier to use dependencies. Here is a list of all default scripts included and registered by WordPress. First lets look at an example to help prevent jQuery conflicts: if your plugin uses jQuery 1.9.2 and WordPress uses jQuery 1.11 then some features, like the drag and drop, might not work. So instead of doing this: Continue reading “Include Builtin scripts from WordPress using wp_enqueue_script()”

Create Local Version Control in your WordPress Plugin

We think its best to start this post of with an example. Lets say you develop and publish version 1 of a plugin, and within this first version you create a custom table in the WordPress database. Your plugin becomes successful and you release version 2 with changes to the table schema. Finally you release version 3 with more changes to the table schema and add a new table that relates to the first table.

What is the Problem and How can we solve it?

If you don’t have local version control, then you cant know what version of your plugin the client currently has installed on their site. This is a problem because you have to make different changes in your plugin depending on which version the client currently has and which one they are updating to.  Look at the follow table schemas below for each hypothetical version of your plugin. Continue reading “Create Local Version Control in your WordPress Plugin”