When building WordPress plugins for myself or others, several of the things I take into account – as we all should – is the level of maintainability, scalability, and support for the plugin as WordPress continues to move forward. Specifically, I’m talking about client-side development (or, more simply, JavaScript). As the support for ES6 […]
Search: “plugins” (Page 95 of 131)
We found 653 results for your search.
[…] Mocking and bringing in WordPress is outside the scope of this post but it’s something we’ll likely look at in the future as it’s useful when testing plugins. For now, I’ll be including a simple autoloader that basically adds all files in the root of the project directory. The full source for it will […]
[…] and this post isn’t going to attempt to cover all of that. Instead, it’s going to take a more pragmatic approach to writing unit tests against WordPress-based plugins, web applications, and the like. [restrict paid=”true”] 1. Writing Unit Tests Whenever you first get into writing unit tests, you’re going to be presented with both […]
[…] but that’s outside the scope of this post. Secondly, this method guaranteed that you’ll have access to the $ as jQuery is passed as an argument into the anonymous function and then referenced by $. Finally, the anonymous function will not cause conflicts with any other plugins, libraries, or scripts as it’s fully encapsulated. jQuery.noConflict ready Function
[…] tying it to Code. This is a matter of doing two things: Installing a plugin in Code, Updating your user settings (once more). First, navigate to the plugins screen in Code and then search for phpcs. You should see something like the following: Click on Install and then Reload if you’re prompted to do […]
