The past couple of weeks, I’ve been discussing the challenge of supporting free WordPress plugins. Though I’ve done this in the past, I’ve retired those projects, but am looking to get back into doing so all the while documenting the process here. But first, for those who haven’t been reading the articles up to […]
Search: “plugins” (Page 26 of 132)
We found 656 results for your search.
Lately, one of the questions that I find myself wrestling with is what’s considered respectful and acceptable for charging for support or accepting donations for open source plugins? Or, more simply, what’s an ideal model for open source profit sharing when you’ve received contributions to open source plugins? A Disclaimer (For The Paranoid!) To […]
[…] of the functions and their types that exist in the installation, and even what file and where the functions are located within the file. And since WordPress plugins, themes, core, and associated tools are open source, we can refactor the ways in which prove useful to us, it allows us to modify the code, […]
[…] it’s successfully activated. To do this, make sure the plugin’s file contains the following code: View the code on Gist. And then save it. Next, navigate to Plugins > Installed Plugins in the WordPress administration area and activate Ray for WordPress. Assuming all has gone well, you should see a success notification that the […]
[…] the original output from GrumPHP. If you look through, the output you’ll see a line like this: You can fix all errors by running following commands: ‘/Users/tommcfarlin/Dropbox/Projects/trunk/wp-content/ plugins/WordPress-Widget-Boilerplate/vendor/bin/php-cs-fixer’ ‘–allow-risky=yes’ ‘–config=.php_cs.dist’ ‘–using-cache=yes’ ‘–verbose’ ‘fix’ So, at this point, let’s look at running the recommended command and see what happens. Specifically, enter this into your terminal: […]
