WordPress Plugin Development Part 1 | How To WordPress Development Article 2019

WordPress Plugin Development | How To WordPress Development Article 2019 :

In this article, how to build a WordPress plugin and expand the possibilities of your web site. [MUSIC PLAYING] So understanding the WordPress documentation and website is a little difficult when you're trying to develop for WordPress. Understanding the documentation for building modules can be somewhat troublesome. Yet, it's entirely straightforward. So we're demonstrating how to fabricate an extremely basic module for your WordPress site. So how about we begin. So here on ideapro.com, I have a default WordPress installation at ideapro.com/example. And we're logged into the back end here. Presently on the off chance that we go here to Plugins, on the off chance that you'll see I have no modules on this establishment. And the reason is because the default WordPress comes with Hello Dolly and A kismet. Neither one of those plugins are plugins that I use, so I immediately delete them before I even upload WordPress to the website. 

WordPress Plugin Development

So we're going to go in now and create a really simple plugin to get you started. All right, so we're going to go to Sublime which is the text editor I use. Furthermore, you can utilize Dreamweaver or Text, Notepad, or whatever you use. We're going to go into ideapro.com under the Example folder, because this is our WordPress install here. So ideapro.com under Example, WP Content and then Plugins. And as you can see here, there's just the index.php page, which comes in the Plugins folder. So on Plugins here, we're going to create a new folder. And we're going to name that folder what we want to call the plugin. So I'm going to name it Idea Pro Example. OK. So now if you look in at Plugins, I have this folder called Idea Pro Plugin. I'm sorry, I have this folder called Idea Pro Example. Now there's nothing inside of it. This index.php page is under Plugins here. 

WordPress Plugin Development

So if we close this, see there's nothing in it. So now we will make a page in that envelope. We will make another clear page. We're going to begin with our PHP sections. And after that we will complete a remark out. We'll do another star. At that point we will do star, star close. So now after this star we're going to say plugin name and we're just going to call it Idea Pro Example Plugin. OK, and then we're going to save this file. Now we're going to save it under the Idea Pro Example folder under Plugins. Also, presently we're going to spare this document indistinguishable name from the organizer above it. So .php. So thought star example.php. So now that really is all that's required to create a plugin. Now if we go into our Plugins here and refresh this page, now we have Idea Pro Example Plugin. And if we activate this plugin, it activates and now it's activated. Now this plugin isn't going to do anything because we really haven't given it anything to do. But it's activated. We can deactivate it. 

WordPress Plugin Development

We can delete it if we wanted to. We're going to keep it activated. Furthermore, presently the other thing that we can do is we can include a depiction. So we'll say Description, This is just an example plugin. If we save that, go back in here to Plugins. So now we have a description here that is the description. So there's multiple things that you can add up here in this little area that describes the plugin. You can add the author, the version number. It's imperative to include the adaptation number in there. I'm not delving to truly delve into every one of the subtleties that you can do with including this. A lot of times if it's not a plugin we're going to use on multiple sites, we may not even add a version number. It all depends. So we will now put a little bit of code in here to make the plugin actually do something. So one of the least demanding activities is to compose a capacity called- - allows simply call it Idea Pro Example Function. Now what we're going to make this function do is it's going to be a short code. So we're going to say add_short code.

WordPress Plugin Development

Presently this capacity here is a piece of the WordPress codex. What's more, we can go into more recordings and insights concerning that later on. So what this add short code does is it allows us to create a short code that we can use on pages and posts. So the first argument that we're going to pass through add_short code is what we're going to use in the page and post as a short code. So here we're just going to say example. Now this is really simple. I would recommend using something that is a little bit more detailed so that you know what it is. Maybe Idea Pro Example or whatever your function actually does. And after that the second contention is really the capacity name here. So we're going to place this in here. And after that in here is the place we put in what we need the genuine module to do. So we're going to instruct it to simply restore a string of content. 

So we're going to say $information = "This is a very basic plugin." Now on a plugin, you always want to return the content. You never want to print it out. You never want to print out the content of the short code. And I'll explain why in just a second. So we're going to save this. We're going to go back into our plugins here. And you see that our plugin hasn't changed. However at this point on the off chance that we go to Posts, Hello World. I'm going to use this one since this is the default here on this front page. Now if we go in here to our short code and we add square brackets and we say example and update. If we go back and we refresh this page, this is a very basic plugin. So there it goes through that tad of content that we place here in this module. 

What's more, we got a capital H. We're going to change that. Okay, and change that. So now this is an essential module. Presently the motivation behind why we return the data here- - and you can consider this string anything you desire - content, as long as you return it here, content. It's as yet going to restore a similar data. The reason why we return it instead of printing it is because the way the structure's set up is you want this information to show up wherever you put in the short code. So if we go back in here after the short code, and this is the text after the short code. We hit Update. Refresh the page. Now this is the text I have for the short code. So we have Welcome to WordPress. This is your first post. Edit or delete it, then start writing. So we have that text here. We have our short code, which appears here. And afterward we have this tad of content after the short code that appears here. So in the event that we return into our code and we don't restore this- - we revive - it won't demonstrate anything by any stretch of the imagination. It will vanish. What's more, on the off chance that we go into here and instruct it to print substance, or reverberation the substance, presently it will put it over any of the other data. As it won't return it in the middle of this two bits of content. It will put it above anything in this substance territory here. 

With the goal that's the motivation behind why it's vital to return rather than print. We'll in reality simply take this out. Furthermore, invigorate, so now it's down here. So now in the event that you know HTML or you know PHP, you can compose a basic module. Presently within this, you can do a wide range of things. So in the event that we need to go in and include more data. So content is equivalent to- - we'll include a div. Also, we'll state this is a div. Also, we'll include substance and this is a square of section content. So now on the off chance that we revive, that data appears. This is the essential module. This is a div. What's more, this is a square of passage content. So within this, insofar as you're restoring this data, it will appear on the page. 

What's more, that is as simple all things considered to make a module. Presently I propose making a module for nearly everything that you do, in case you're going to utilize that on another site. Or on the other hand if it's a great deal of code. The motivation behind why is on the grounds that in the long run you will introduce a module that another person has assembled that could break your site. So it makes it extremely simple to kill modules until you've made sense of which module is clashing with the other, or clashing with your site. Presently what we simply did is extremely basic code. Furthermore, we could have effectively quite recently taken this code- - and we'll remove it from here. We could have effectively quite recently went into the subject that we're utilizing - 17- - and went to the Functions page here and included this the Functions page. So right now we removed it from our module here. So on the off chance that we revive, it's gone. Presently it says model, since it doesn't have the foggiest idea how to manage that short code. 

Thus now in the event that we go into the Functions page, we'll go down here to the exceptionally base, and we'll glue in this capacity. Furthermore, we'll invigorate. Furthermore, presently this data is back. So it doesn't really - we didn't really need to fabricate a module to do what we simply did. But at the same time it's dirtied up our functions.php page. So anything, particularly in case you're utilizing a pre-fabricated topic or a standard subject that accompanied the WordPress introduce, I would propose doing everything as a module. In such a case that you do it in the default functions.php page, when the subject updates, it will overwrite any capacities that you put on this page. Presently you can make what's known as a kid subject of the present topic. So we're utilizing 2017 here as our default subject that accompanies WordPress. In the event that we needed to make a youngster subject of 2017, we would do that. And after that on the Functions page of that page, we could really include the code and that would work. Be that as it may, I would recommend doing it as a module. That way you can turn it on and off. It's likewise great on the off chance that you ever choose to change subjects, you're not losing that data. So you can change subjects. 

WordPress Plugin Development

You're not going to lose the module. So a ton of times we construct modules for pretty much everything, in light of the fact that the customer may change the subject later on. Tell me your inquiries in the remarks. Expectation this video helped some of you manufacture a module. It's fundamental. It's not as hard as the documentation and different recordings describe it. It's very easy to assemble modules.

What's more, trust this article helped you.

Make a point to like it and buy in for the following article.

Visit the WordPress codex http://ideapro.com/url/wordpress-codex for more functions that can be used in your plugin.