1
0
Fork 0
mirror of https://github.com/inretio/WordPress-Plugin-Boilerplate synced 2024-05-19 03:32:11 +03:00

Compare commits

...

215 commits

Author SHA1 Message Date
Gytis Repečka a57e6e7460
Add shortcode support. 2020-07-17 16:58:32 +03:00
Devin a8291082b5
Merge pull request #508 from alertmybanjos/patch-2
Update README.md
2019-02-22 11:15:41 -05:00
Devin d2f6b21b80
Merge pull request #507 from alertmybanjos/patch-1
Update README.md
2019-02-22 11:15:26 -05:00
Jason Tremblay f142df8c45
Update README.md
More specific, case sensitive string changes for initial setup.
2019-02-22 06:29:41 -05:00
Jason Tremblay 611c80cce1
Update README.md
Clarify the renaming step to align with the actual file names, which are currently named with dashes, not underscores.
2019-02-22 05:56:58 -05:00
Devin 60940a9761
Merge pull request #456 from manzoorwanijk/patch-1
Typo correction
2018-01-06 15:40:49 -05:00
Manzoor Wani b02101400e
Typo correction 2017-12-07 14:29:48 +05:30
Devin bc3e07be2a
Merge pull request #453 from Ipstenu/Ipstenu-rtfm
Documentation update for Plugin Version constant. Thank you @Ipstenu
2017-11-27 17:34:45 -05:00
Ipstenu (Mika Epstein) 95844fec48
Inline doc 2017-11-27 14:09:08 -08:00
Ipstenu (Mika Epstein) 696db21ed7
Clarifying directions 2017-11-27 14:07:36 -08:00
Devin 7af6de6dd2 Merge pull request #446 from jonathanbossenger/master
Updating PLUGIN_VERSION constant. Fixes #446
2017-09-27 19:37:57 -04:00
Jonathan Bossenger 04f90ff5ff Updating PLUGIN_VERSION to PLUGIN_NAME_VERSION to follow plugin standards for renaming 2017-09-27 16:13:29 +02:00
Devin 1f36abcedd Merge pull request #443 from Tmeister/master
Wraps the PLUGIN_VERSION constant in single quotes
2017-09-12 08:53:40 -04:00
Enrique Chavez 65a87940e9 Wraps the PLUGIN_VERSION constant in single quotes
* Fix #442
* Avoids the notice output
2017-09-11 11:33:00 -05:00
Devin 1f3c2acbe2 Merge pull request #417 from davidshq/patch-1
Small Spelling / Grammar Changes
2017-08-30 09:13:14 -04:00
Devin 77baf0b2f5 Merge pull request #429 from cliffordp/patch-2
Typo: "he" to "The"
2017-08-30 09:11:44 -04:00
Devin 19809447ec Merge pull request #353 from TalAter/patch-1
Fixed mistake in comment.
2017-08-30 09:11:20 -04:00
Devin 872c67477a Merge pull request #439 from jonathanbossenger/feature/version-constant
Adding a version constant
2017-08-30 09:04:32 -04:00
Jonathan Bossenger 5af56b19a5 Adding a version constant 2017-07-17 10:04:31 +02:00
Clifford ded444099b Typo: "he" to "The" 2017-05-19 17:39:12 -05:00
Dave Mackey c719bf9fc7 Small Spelling / Grammar Changes
Corrected a few small spelling / grammar issues throughout - very minor.
2017-01-19 21:41:23 -05:00
Devin Vinson 923fbaf0c8 Merge branch 'remove-var-translation' 2015-12-11 12:58:15 -05:00
Devin Vinson 0c099e4208 Use plugin-name directly instead of passing a variable through
This should fix the incorrect pattern of using a variable where we
should be using the plugin-name instead. Same goes for any translatable
strings within the plugin (no more using $this->plugin-name etc).
2015-12-05 20:46:30 -05:00
Tal Ater 579fb9823a Fixed mistake in comment. 2015-11-25 20:48:25 -05:00
Devin 39cb7ccfb3 Merge pull request #350 from hareesh-pillai/master
Update URL for Documentation Standards
2015-11-20 11:42:26 -05:00
Devin 6f217e9efd Merge pull request #349 from pieroit/patch-1
Update plugin-name-admin.js
2015-11-20 11:42:00 -05:00
Hareesh 0ea2ae758e Update URL for Documentation Standards 2015-11-15 01:23:52 +05:30
Piero Savastano fcd4669f35 Update plugin-name-admin.js
typo in the comment
2015-11-11 16:33:27 +01:00
Devin 2508a4567b Merge pull request #340 from LeeRobertsMe/patch-1
Update class-plugin-name-public.php so the correct file type is defined.
2015-11-03 08:25:04 -05:00
Devin 1b487de0db Merge pull request #342 from LeeRobertsMe/patch-5
Update plugin-name-public.js
2015-11-03 08:24:26 -05:00
Devin 84741e2c1b Merge pull request #343 from LeeRobertsMe/patch-4
Update plugin-name-admin.js
2015-11-03 08:24:03 -05:00
Devin 4e84183fd4 Merge pull request #339 from Shelob9/loader-docs-338
Add corrected inline docs in the loader class
2015-10-21 08:36:14 -04:00
LeeRobertsMe 360c8ea6e4 Update plugin-name-admin.js 2015-10-08 13:35:24 +01:00
LeeRobertsMe a11edd3138 Update plugin-name-public.js 2015-10-08 13:29:18 +01:00
LeeRobertsMe 1fe19e455f Update class-plugin-name-public.php 2015-10-08 12:25:28 +01:00
Josh Pollock 897fa95e23 Add inline docs in the loader class #338 2015-10-02 15:35:30 -04:00
Devin 55f28eeb9f Merge pull request #324 from javy-/patch-1
Update CHANGELOG with correct year.md
2015-08-13 09:45:17 -04:00
javy- ff46923e03 Update CHANGELOG.md
Fix latest change date year (2014->2015)
2015-08-08 16:48:17 -04:00
Devin 5d51804dea Merge pull request #323 from davidshq/master
Update README.md
2015-08-01 01:01:05 -04:00
Dave Mackey 6f0aabf3be Update README.md
Changed "this feature" to "these features"
2015-07-31 12:48:05 -04:00
Devin Vinson 5391e0ca27 Remove .org parent folder structure
Flattening the folder structure for a bit easier auto-inclusion into
projects and local development.

See:
https://github.com/DevinVinson/WordPress-Plugin-Boilerplate/issues/295
2015-07-03 23:33:03 -04:00
Devin 3d3f181924 Merge pull request #266 from jancbeck/admin-area-dashboard-wording
changed wording from "dashboard" to "admin area"
2015-03-09 09:58:10 -04:00
Devin Vinson a5e181192b Updated Readme
Added a note about current project lead and pointing inquires away from
Tom’s contact form.
2015-03-04 15:21:25 -05:00
Jan Beck 9c14d6e3eb changed "dashboard" to "admin area"
dashboard-specific becomes admin-specific
2015-02-13 14:31:40 -04:00
Tom McFarlin b469237bda Merge pull request #260 from slushman/master
Function docs should be @param not @var.
2015-02-03 12:18:42 -05:00
Chris Wilcoxson 2683f494ea Function docs should be @param not @var. 2015-02-03 11:15:28 -06:00
Tom McFarlin 474e64911c Merge pull request #254 from donnapep/chore/change-loader-class-names
Fix incorrect class names
2015-01-19 09:51:22 -05:00
Donna Murphy 582ccadde0 Fix incorrect class names 2015-01-17 12:45:15 -05:00
Tom McFarlin 470d0ec13c Merge pull request #250 from swalkinshaw/CHANGELOG-fix
Fix CHANGELOG filename
2015-01-05 13:01:35 -05:00
Scott Walkinshaw 78624f6cdd Fix CHANGELOG filename 2015-01-05 11:42:45 -05:00
Tom McFarlin 629b1628ca Merge pull request #243 from tnorthcutt/patch-1
Fix minor typo in README.md
2014-12-01 14:52:30 -05:00
Travis Northcutt 411b1d19b9 Fix minor typo in README.md 2014-11-26 09:57:22 -06:00
Tom McFarlin 72cda6eeaf Merge pull request #238 from gosukiwi/patch-1
Use the same syntax for all included files.

Fixes #238
2014-11-19 13:59:21 -05:00
Federico Ramirez 042c13b7b1 Use the same syntax for all included files
I was having issues activating the plugin, and it was because of the way the files were beeing included, this fixes it.
2014-11-19 09:25:59 -03:00
Tom McFarlin ec4c52c115 Merge pull request #237 from feskehau/master
Create functions for activation and deactivation hooks.
2014-11-17 12:32:39 -05:00
Tony Hesjevik e015b9cd7c Create functions for activation and deactivation hooks.
Moving the activation and deactivation hooks into its own functions, makes so we dont have to include class-plugin-name-deactivator and class-plugin-name-activator on every page load.
2014-11-17 23:33:00 +11:00
Tom McFarlin 3c47bc0b5a Merge pull request #235 from barryceelen/patch-1
Fix code comment typo
2014-11-10 14:15:37 -05:00
Barry Ceelen f51ee23a1f Fix code comment typo 2014-11-10 16:57:08 +01:00
Tom McFarlin f11711f07e Merge pull request #231 from NikV/patch-1
Fixing require() vs require_once()
2014-11-05 12:08:34 -05:00
Nikhil Vimal 2960b6c1c8 Fixing require() vs require_once()
See : https://github.com/tommcfarlin/WordPress-Plugin-Boilerplate/issues/222. I believe this was in favor of doing it "correctly"?
2014-11-04 16:47:16 -06:00
Tom McFarlin 025d61efee Merge pull request #224 from mAAdhaTTah/variable-fix
Change name -> plugin_name for consistency
2014-10-07 16:46:49 -04:00
mAAdhaTTah dbf2c73757 Change name -> plugin_name for consistency 2014-10-07 16:43:55 -04:00
Tom McFarlin f112840426 Merge pull request #220 from iamdmitrymayorov/master
Minor comment fix.
2014-10-07 16:34:23 -04:00
Dmitry Mayorov 7a12d6aa66 Update class-plugin-name-public.php
Updated @subpackage from 'admin' to 'public'
2014-10-05 19:36:55 +06:00
Dmitry Mayorov 163c2a86c1 Update class-plugin-name-admin.php
Changed @subpackage from 'includes' to 'admin'.
2014-10-05 19:35:03 +06:00
Tom McFarlin b08802742d Merge pull request #216 from JustinSainton/please-stop-shouting-at-me
Please stop shouting at me. I do hate when my parents shout.
2014-09-11 06:46:59 -04:00
Justin Sainton 50bc541455 Please stop shouting at me. I do hate when my parents shout.
But in all seriousness, shouting types is bad form.
2014-09-10 21:19:37 -07:00
Tom McFarlin f4bbb821c2 Merge branch 'master' of https://github.com/tommcfarlin/WordPress-Plugin-Boilerplate 2014-09-04 09:45:48 -04:00
Tom McFarlin 16c93f8548 Adding instructions for Windows symlinks
Fixes #213
2014-09-04 09:44:54 -04:00
Tom McFarlin d5bb3c526f Merge pull request #214 from jessertaylor/master
Fixed deactivation hook in plugin_name.php
2014-09-03 10:57:25 -04:00
jessertaylor 8f002bfc4d Fixed deactivation hook in plugin_name.php 2014-09-03 15:11:55 +01:00
Tom McFarlin 06605429d3 describe how to install the Boilerplate.
Updating the `README` to describe how to install the Boilerplate.

Fixes #213
2014-09-03 09:26:49 -04:00
Tom McFarlin c8bd2e38af Merge pull request #211 from rob/patch-1
Fix typo in plugin-name.php
2014-09-02 13:55:18 -04:00
Rob Gabaree 50f2a612f8 Fix typo in plugin-name.php 2014-09-02 13:16:20 -04:00
Tom McFarlin 097afb19b7 Merge pull request #210 from rob/patch-1
Fix incorrect date in ChangeLog.md
2014-09-02 12:27:35 -04:00
Rob Gabaree d2a71ed513 Fix incorrect date in ChangeLog.md 2014-09-02 12:26:08 -04:00
Tom McFarlin cda33620e7 Merge remote-tracking branch 'origin/master' into develop
Conflicts:
	ChangeLog.md
	README.md
	plugin-name/admin/class-plugin-name-admin.php
	plugin-name/plugin-name.php
	plugin-name/public/class-plugin-name.php
	plugin-name/trunk/README.txt
	plugin-name/uninstall.php
2014-09-01 20:42:08 -04:00
Tom McFarlin c3c95e0a81 updating credits 2014-09-01 10:38:09 -04:00
Tom McFarlin e387eabfc1 update to the README 2014-09-01 10:33:51 -04:00
Tom McFarlin 0d21f63eda Adding the initial version of the README 2014-09-01 10:32:22 -04:00
Tom McFarlin 436ca4a72b cleaning up the changelog 2014-09-01 10:30:10 -04:00
Tom McFarlin 39275f0cbf Merge branch 'develop' of https://github.com/tommcfarlin/WordPress-Plugin-Boilerplate into develop 2014-09-01 09:46:44 -04:00
Tom McFarlin 15de548f39 adding a placeholder for the plugin icon 2014-09-01 09:45:57 -04:00
Tom McFarlin 0694bf9302 Merge pull request #206 from michaelbeil/patch-2
added periods in first list for consistency
2014-08-21 12:32:11 -04:00
Michael Beil fc2a90f412 added periods in first list for consistency 2014-08-21 11:30:45 -05:00
Tom McFarlin f62930975f Merge pull request #203 from michaelbeil/patch-1
Us to use
2014-08-21 10:05:38 -04:00
Michael Beil 4a092e1a77 Us to use 2014-08-20 17:42:18 -05:00
Tom McFarlin 56a494c944 Merge pull request #202 from douglsmith/patch-1
Fix minor typo in plugin-name.php description text
2014-08-19 16:07:17 -04:00
Doug Smith b8a357b336 Fix minor typo in plugin-name.php description text 2014-08-19 15:06:09 -05:00
Tom McFarlin b421ddaaaa Updating notes and updated date. 2014-08-19 08:51:56 -04:00
Tom McFarlin ef28c5a351 Updating the docblock 2014-08-18 17:08:36 -04:00
Tom McFarlin 4d6a0dfa3e Finalizing code for beta
* Updating DocBlocks
* Fixing typos
* Adjusting whitespace
2014-08-18 17:00:09 -04:00
Tom McFarlin 6782bb5ec3 Updating a comment 2014-08-16 16:30:16 -04:00
Tom McFarlin bcc1d91782 Update the 'last updated' date 2014-08-05 16:43:31 -04:00
Tom McFarlin 2e9ae6ac99 Populating the DocBlock
Fixes #123
2014-08-05 16:43:08 -04:00
Tom McFarlin 96f957d6e9 Updating doc block
* class-plugin-name now includes different file and class documentation
* changing a URL to an example URL
2014-08-01 17:06:09 -04:00
Tom McFarlin 35650c1b7b Setting the reference using the proper variable 2014-08-01 16:59:31 -04:00
Tom McFarlin aea004af54 Chaing the doc from 'slug' to 'string' 2014-08-01 16:59:19 -04:00
Tom McFarlin ef63ff4a91 Merge branch 'develop' of https://github.com/tommcfarlin/WordPress-Plugin-Boilerplate into develop 2014-08-01 16:56:38 -04:00
Tom McFarlin f3133d8cb5 Improving docblocks
* Documenting the plugin file
* Changing the docblock to read 'class', not 'file'

Related #199
2014-08-01 16:47:08 -04:00
Tom McFarlin 6d6f6399f7 Removing a duplicate line of code
Related #199
2014-08-01 16:44:57 -04:00
Tom McFarlin bfb7e6fb58 Merge pull request #197 from grappler/plugin-header
Move text domain lower down
2014-07-30 16:15:43 -04:00
Tom McFarlin 9b5afad159 Merge pull request #198 from grappler/uninstall-header
Update uninstall header for consistency
2014-07-30 16:14:59 -04:00
Tom McFarlin 0eb25eefba Merge pull request #200 from grappler/duplicate-doc
Remove duplicate documentation
2014-07-30 16:14:36 -04:00
Ulrich Pogson 3067be69b5 Remove duplicate documentation 2014-07-30 21:59:15 +02:00
Ulrich Pogson 67dc6fb7a2 Update uninstall header for consistency 2014-07-30 21:55:26 +02:00
Ulrich Pogson 836d85d1c8 Move text domain lower down 2014-07-30 21:52:41 +02:00
Tom McFarlin efa4d08df3 Updating code comments for require and function
Fixes #192
2014-07-30 15:23:18 -04:00
Tom McFarlin 57205587af Making the file headers more conssitent
Improving the documentation for each file, as well.

Fix #193
2014-07-30 15:16:32 -04:00
Tom McFarlin 43ee54a0ee Adding documentation to two missing functions
Fixes #192
2014-07-30 15:03:33 -04:00
Tom McFarlin 918ee9e5f9 Removing public @access tags
Following the guide of the PHPDoc Block Formatting

> @access (for functions: only use if private)

Fix #191
2014-07-30 15:00:57 -04:00
Tom McFarlin 4d9f666e0f Merge pull request #196 from grappler/remove-spaces
Remove spaces before code
2014-07-30 14:57:11 -04:00
Tom McFarlin 8ee0c49bd7 Fixes #195
Updating the header so that it conforms to PHP DocBlock standards and WP Plugin Standards
2014-07-30 14:56:37 -04:00
Tom McFarlin ec29ebc95b Renaming the plugin slug to the plugin name
Also renaming the text domain in the header of the core plugin file to match that of the plugin name

Fixes #194
2014-07-30 13:58:41 -04:00
Ulrich Pogson 48e0a373dd Remove spaces before code 2014-07-30 16:04:18 +02:00
Tom McFarlin 81b3c8bd6d Updating the arguments passed to the classes 2014-07-29 17:10:31 -04:00
Tom McFarlin 0f4aaa9693 Updating the docblocks for this function 2014-07-29 17:10:09 -04:00
Tom McFarlin 370c439bb2 Adding the plugin slug to the constructor args 2014-07-29 17:09:55 -04:00
Tom McFarlin 560e5959a5 Documenting classes
Documenting classes that are core to each plugin, while also leaving other classes undocumented for an implementation-specific basis.
2014-07-29 16:56:18 -04:00
Tom McFarlin f09ca373d8 Removing the trailingslash from the URL 2014-07-29 16:55:10 -04:00
Tom McFarlin b706dc3291 Updating code comments
Making sure that the code comments strictly follow that of the WordPress PHP Documentation Standards
2014-07-29 16:03:09 -04:00
Tom McFarlin 2af01cf653 Updating the code comments
Making sure that the code comments strictly follow that of the WordPress PHP Documentation Standards
2014-07-29 15:56:12 -04:00
Tom McFarlin 2a66ff4d50 finalizing docblocks
Making sure that the code comments strictly follow the WordPress PHP Documentation Standards
2014-07-29 15:48:33 -04:00
Tom McFarlin 3154e38822 updating the 'last updated' date 2014-07-07 16:59:02 -04:00
Tom McFarlin 3ae56a6460 adding a comma that was preventing a syntax problem 2014-07-07 16:56:54 -04:00
Tom McFarlin a3cce1d965 updating 'last updated' dates 2014-06-26 16:46:14 -04:00
Tom McFarlin 23235f94d7 completing the initial round of PHP documentation as per the WPCS
http://make.wordpress.org/core/handbook/inline-documentation-standards/php-documentation-standards/#1-functions-and-class-methods
2014-06-26 16:19:57 -04:00
Tom McFarlin 9f5ffbf597 adding a priority argument to the loader (defaulting to 10 as per wordpress codex) 2014-06-26 15:43:18 -04:00
Tom McFarlin 547319a8b6 Merge pull request #187 from defries/master
Added grunt-wp-i18n solution for i18n-ing the plugin
2014-06-10 10:48:59 -04:00
Remkus de Vries ddc916762b Added grunt-wp-i18n solution for i18n-ing the plugin 2014-06-10 14:25:26 +02:00
Tom McFarlin 5efc89dc3b Merge pull request #186 from grappler/activate-deactivate
Move restore_current_blog in the correct position
2014-05-31 22:05:10 -04:00
Ulrich Pogson e75e6e2c57 Move restore_current_blog in the correct position 2014-06-01 00:06:29 +02:00
Tom McFarlin 7d71114f81 updating the change log to reflect the latest tag 2014-05-09 09:36:06 -04:00
Tom McFarlin 2c29f1ca04 moving $wpdb outside of the conditional so both cases work
Fixes #182
2014-05-09 09:35:11 -04:00
Tom McFarlin b7caa3e958 updating last updated dates 2014-05-08 23:35:44 -04:00
Tom McFarlin f89752180f adding TODO docblocks 2014-05-08 23:34:38 -04:00
Tom McFarlin bb3c56b0c2 adding TODO code docblocks 2014-05-08 23:34:29 -04:00
Tom McFarlin f332130569 moving all bootstrap code into this file, adding some getters for dependencies
setting up this file to fire the plugin so that it's prepared to handle any hooks given to the loader
2014-05-08 23:34:16 -04:00
Tom McFarlin e29a775e76 completely refactoring the main plugin file
* leaving the de/activation code here for now
* moving all bootstrap code into class-plugin-name.php
* setting up this file to fire the plugin so that it's prepared to handle any hooks given to the loader
2014-05-08 23:33:47 -04:00
Tom McFarlin 9a23715ba7 de-subclassing this class and defining a domain attribute provided by setter injection 2014-05-08 18:10:22 -04:00
Tom McFarlin 0d63ec21e5 adding getters for the protected properties 2014-05-08 18:10:04 -04:00
Tom McFarlin 0fdaeaa67c fixing a small type, documentation the imports, changing the way in which the plugin is instantiated 2014-05-08 18:09:50 -04:00
Tom McFarlin cc6df31722 de-subclassing the file, adding a version attribute, setting it in the constructor 2014-05-08 18:09:10 -04:00
Tom McFarlin 00c5f7d733 adding a public getter for the plugin slug so that external classes can reference it
ht @garyjoes b5549d5f9c (commitcomment-6236733)
2014-05-08 16:50:23 -04:00
Tom McFarlin 71f40d5e7a updating the calls to the plugin loader so that they appropriately call add_action and add_filter 2014-05-06 09:54:13 -04:00
Tom McFarlin d5bb1de8fb adding a collection for hooks and filters to distinguish between the hooks being added 2014-05-06 09:53:16 -04:00
Tom McFarlin 7e64091fd4 updating the foreach loop from a previous version of the loop 2014-05-05 00:28:02 -04:00
Tom McFarlin 5265d1f0ae introducing the single, shared loader class 2014-05-05 00:18:13 -04:00
Tom McFarlin b5549d5f9c defining a base class from which all other components can inherit
also getting rid of the version constant in place of a properly, defining a single entry point with the run function, and defining the plugin slug as a property
2014-05-05 00:18:04 -04:00
Tom McFarlin d29ebf7dc8 extending the new plugin name base class and implementing localization 2014-05-05 00:17:23 -04:00
Tom McFarlin f6a587372a extending the new plugin name base class 2014-05-05 00:17:13 -04:00
Tom McFarlin e503be7e38 changing the working name and URL of the plugin so not to conflict with another file in the repository.
changing the ways in which the plugin loader, plugin components, and plugin works
2014-05-05 00:16:52 -04:00
Tom McFarlin 6e46a1f439 removing the individual loaders in order to consolidate them into a single, shared loader 2014-05-05 00:16:13 -04:00
Tom McFarlin 24c1cca493 updating the read me and change log to reflect the latest changes of the plugin 2014-05-03 15:29:17 -04:00
Tom McFarlin 8c0b11ca1b adding a @TODO tag for localization class 2014-05-03 15:28:23 -04:00
Tom McFarlin c83aa5434d updating the docblocks 2014-05-03 15:28:04 -04:00
Tom McFarlin ee79eb4582 adding type hinting to the run function's arguments 2014-05-03 15:27:38 -04:00
Tom McFarlin 0abff96cfc removing whitespace 2014-05-03 15:27:15 -04:00
Tom McFarlin 8cfee0e67a updating the docblocks and actually registering the demo scripts and styles 2014-05-03 15:27:01 -04:00
Tom McFarlin b3451b717f instantiating and loading the dashboard-specific and public-facing areas of the plugin
also updating the docblocks to explain what each hooked function is doing
2014-05-03 15:26:22 -04:00
Tom McFarlin 91273f37d4 updating the docblocks 2014-05-03 15:07:38 -04:00
Tom McFarlin 135920036b updating the docblocks with clearer descriptions as to what each tag and line should contain. 2014-05-03 15:07:24 -04:00
Tom McFarlin 4114ad703e updating the docblocks 2014-05-03 15:07:05 -04:00
Tom McFarlin 821e24a9ea updating the docblocks 2014-05-03 15:06:57 -04:00
Tom McFarlin af315d7145 adding whitespace and additional instructions 2014-05-03 15:06:50 -04:00
Tom McFarlin c10b371d67 updating the docblocks and adding whitespace to the end of the file 2014-05-03 15:06:38 -04:00
Tom McFarlin 4f2719b2eb updating the docblocks 2014-05-03 15:06:13 -04:00
Tom McFarlin f6917437fc Merge pull request #181 from BlueTeck/patch-1
gramar mistake
2014-05-02 10:00:59 -04:00
Timo 9555d7bd46 grammar mistake 2014-05-02 15:58:45 +02:00
Tom McFarlin 96018e57b0 updating the change log to reflect notes on the version of the boilerplate 2014-05-01 23:44:12 -04:00
Tom McFarlin ecb940ed22 defining a constant for use throughout the boilerplate 2014-05-01 23:43:32 -04:00
Tom McFarlin a9e071aef8 removing the original example functions and replacing them with functions that use existing boilerplate files 2014-05-01 23:43:07 -04:00
Tom McFarlin 40fd22a297 adding hooks to include the styles and scripts for the dashboard 2014-05-01 23:42:46 -04:00
Tom McFarlin 92e4693a8f updating the last updated date and what the final tag name will be 2014-05-01 23:27:41 -04:00
Tom McFarlin d5446ad5c1 updating the date in the core README 2014-05-01 23:26:55 -04:00
Tom McFarlin 793797ae71 removing all of the @TODO references
as per GaryJones notes, "You can't have tags come before the short / long description, otherwise the descriptions end up as part of a multiline tag."

removing these @TODO's until the team decides whether or not to replace them with something clearer, or to discuss it to the documentation
2014-05-01 23:26:16 -04:00
Tom McFarlin 6271822cb1 adding simple public-facing code comments 2014-04-30 22:56:27 -04:00
Tom McFarlin 98b6bf3f65 adding simple code comments for the public-facing code comments 2014-04-30 22:56:17 -04:00
Tom McFarlin fc2b3109dd defining the loader functionality to be used via dependency injection 2014-04-30 22:56:05 -04:00
Tom McFarlin a5864a9d96 adding whitespace 2014-04-30 22:55:42 -04:00
Tom McFarlin 0896f0836c defining the core shared plugin name
this file is used to be shared between the dashboard and public-facing functionality. it's hooks should be defined in the specific loader
2014-04-30 22:55:34 -04:00
Tom McFarlin c05ae57e91 defining the basic code comments for the dashboard-specific 2014-04-30 22:55:06 -04:00
Tom McFarlin 4b7dde5553 defining the basic code comments and the public facing partial 2014-04-30 22:54:48 -04:00
Tom McFarlin a392f3f9db updating the documentation for the core public plugin file
updating the documentation for the core admin plugin file with docblocks and example functions for how they should be used and their relationship to the public loader
2014-04-30 22:54:25 -04:00
Tom McFarlin 71ff4b6ec7 updating the documentation
updating the documentation for the core admin plugin file with docblocks and example functions for how they should be used and their relationship to the admin loader
2014-04-30 22:54:00 -04:00
Tom McFarlin 4504d3a4fd adding example documentation
adding example documentation and code for how to user the admin loader via dependency injection
2014-04-30 22:53:22 -04:00
Tom McFarlin fbf09acbdb spacing out the code in the docblock 2014-04-30 22:34:39 -04:00
Tom McFarlin a4fc32fa59 providing a first pass at the docblocks for the admin loader
eventually, this class will be responsible for defining all of the hooks for the admin-facing side of the plugin
2014-04-30 22:34:19 -04:00
Tom McFarlin 284dc26054 adding basic comments to the admin stylesheets
this may eventually be removed and placed into the boilerplate's documentation on the official website, but until that exists, it will remain here.
2014-04-30 22:33:30 -04:00
Tom McFarlin deadcc668b adding basic documentation for the admin javascript file
this may eventually be removed and placed into the boilerplate's documentation on the official website, but until that exists, it will remain here.
2014-04-30 22:33:06 -04:00
Tom McFarlin 5666bb7ddc Completing the first round of docblocks for the activation / deactivation classes 2014-04-30 22:32:27 -04:00
Tom McFarlin b7d17e4122 updating the docblocks for proper use of TODO and @TODO 2014-04-30 22:06:19 -04:00
Tom McFarlin b8132f4b9d removing unnecessary closing parens.
Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-26 17:42:21 -04:00
Tom McFarlin 9f71476166 updating the docblocks to the match the wpcs
http://make.wordpress.org/core/handbook/inline-documentation-standards/php-documentation-standards/
Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-25 19:00:08 -04:00
Tom McFarlin 026515da85 adding docblocks consistent with the wpcs for the files in includes
http://make.wordpress.org/core/handbook/inline-documentation-standards/php-documentation-standards/
Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-25 18:58:07 -04:00
Tom McFarlin 2cf4ba8223 adding a trailing whitespace to all of our defined files
this helps with cleaner diffs. It's also on one of the PSRs, and it's one of the WPCS rules. (ht @garyjones for the reminder)

Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-25 18:39:31 -04:00
Tom McFarlin 72690b6771 introducing the empty loader files
this are the files that will be used to define the actions and filters for their respective area of the plugin

Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-25 18:35:52 -04:00
Tom McFarlin 5ab1805db8 removing '@TODO' in favor of 'TODO'
WordPress doesn't like '@TODO' and doesn't honor it when displaying it in the dashboard

Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-25 18:21:25 -04:00
Tom McFarlin 25337b6477 Merge pull request #179 from nextgenthemes/patch-1
Support PHP 5.2.x by dropping __DIR__
2014-04-15 10:46:27 -04:00
nextgenthemes b744549d3b Support PHP 5.2.x by dropping dir __DIR__
As per https://github.com/nextgenthemes/advanced-responsive-video-embedder/issues/7 I was informed that this would make my plugin work with PHP 5.2.x. I personally have not tested this code yet but I assume @andrejpavlovic did so I thought if this is the only thing that makes the Boilerplate require PHP 5.3 this might be a good change since WordPress itself only requires PHP 5.2.4.
2014-04-15 14:07:41 +02:00
Tom McFarlin e91be4101d updating the code comments as per the handbook
Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-11 10:36:57 -04:00
Tom McFarlin 3bee4f4272 updating the code comments as per the handbook
Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-11 10:36:47 -04:00
Tom McFarlin b426fbe514 renaming the plugin activation and deactivation classes
Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-11 10:36:13 -04:00
Tom McFarlin 766b47b643 Updating the text of the index file so that it matches all other WordPress files
Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-11 10:35:40 -04:00
Tom McFarlin 28da2f7c41 checking in the start of the docblocks for the various PHP files of the boilerplate
Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-09 16:22:44 -04:00
Tom McFarlin b868c5da02 initial commit of the skeletons for the javascript files
Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-09 16:10:27 -04:00
Tom McFarlin 0c6d8418f6 adding the index.php files for protecting directory contents
Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-09 15:51:18 -04:00
Tom McFarlin b690a0cb63 adding a copy of the gpl
Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-09 15:47:56 -04:00
Tom McFarlin 2c359bad76 adding the read me skeleton
Signed-off-by: Tom McFarlin <tom@tommcfarlin.com>
2014-04-09 15:44:22 -04:00
Tom McFarlin db289e2284 Merge pull request #176 from emeraldjava/master
Issue#175 Add WordPress-Plugin-Boilerplate version
2014-03-26 12:04:17 -04:00
emeraldjava 4a73e7615a Issue#132 Add a reference to the WordPress Plugin Boilerplate project in
the readme file of the new plugin.
2014-03-26 16:02:27 +00:00
emeraldjava aa38893520 Issue#117 - Update the plugin description 2014-03-26 15:57:44 +00:00
emeraldjava 96edc6e0b1 Issue#175 Add WordPress-Plugin-Boilerplate version 2014-03-26 15:47:51 +00:00
Tom McFarlin 4beb185a90 Merge pull request #172 from robertharm/dev
enhance uninstall.php template
2014-03-25 08:49:39 -04:00
Robert Harm 17b4d608ed expand uninstall.php to also delete transient, options, custom database tables and files 2014-03-25 13:25:08 +01:00
42 changed files with 1487 additions and 25 deletions

5
CHANGELOG.md Normal file
View file

@ -0,0 +1,5 @@
# Changelog
* (3 July 2015). Flattened the folder structure so there is no .org repo parent folder.
* (4 September 2014). Updating the `README` with Windows symbolic link instructions.
* (3 September 2014). Updating the `README` to describe how to install the Boilerplate.
* (1 September 2014). Initial Release.

View file

@ -1,21 +0,0 @@
# ChangeLog
* Last updated 18 March 2014
## About This Branch
The WordPress Plugin Boilerplate is being rewritten from the ground up and will be officially released in the `master` branch as `2.7.0`.
In order to prevent any interference with the latest stable version, the `develop` branch was created starting with `0.1.0` as per [semver](http://semver.org/).
Once `develop` reaches it's official stable state (that is, `1.0.0`), it will be merged into `master` as `2.7.0`.
## 0.1.0 (18 March 2014)
* Initial commit
## Author Information
The WordPress Plugin Boilerplate was originally written by [Tom McFarlin](http://twitter.com/tommcfarlin/), but is now under development thanks to the contributions from the many WordPress developers throughout the world.
The current `develop` branch is maintained by Tom McFarlin, Ulrich Pogson, Josh Eaton, and Brad Vincent.

View file

@ -1,9 +1,99 @@
# WordPress Plugin Boilerplate
* **Last Updated:** 18 March 2018
A standardized, organized, object-oriented foundation for building high-quality WordPress Plugins.
This branch is currently for a rewrite of the WordPress Plugin Boilerplate.
## Contents
This is experimental code and is not intended for us until it's been merged into the `master` branch.
The WordPress Plugin Boilerplate includes the following files:
Please review the [ChangeLog](https://github.com/tommcfarlin/WordPress-Plugin-Boilerplate/blob/develop/ChangeLog.md) for more information.
* `.gitignore`. Used to exclude certain files from the repository.
* `CHANGELOG.md`. The list of changes to the core project.
* `README.md`. The file that youre currently reading.
* A `plugin-name` directory that contains the source code - a fully executable WordPress plugin.
## Features
* The Boilerplate is based on the [Plugin API](http://codex.wordpress.org/Plugin_API), [Coding Standards](http://codex.wordpress.org/WordPress_Coding_Standards), and [Documentation Standards](https://make.wordpress.org/core/handbook/best-practices/inline-documentation-standards/php/).
* All classes, functions, and variables are documented so that you know what you need to change.
* The Boilerplate uses a strict file organization scheme that corresponds both to the WordPress Plugin Repository structure, and that makes it easy to organize the files that compose the plugin.
* The project includes a `.pot` file as a starting point for internationalization.
## Installation
The Boilerplate can be installed directly into your plugins folder "as-is". You will want to rename it and the classes inside of it to fit your needs. For example, if your plugin is named 'example-me' then:
* rename files from `plugin-name` to `example-me`
* change `plugin_name` to `example_me`
* change `plugin-name` to `example-me`
* change `Plugin_Name` to `Example_Me`
* change `PLUGIN_NAME_` to `EXAMPLE_ME_`
It's safe to activate the plugin at this point. Because the Boilerplate has no real functionality there will be no menu items, meta boxes, or custom post types added until you write the code.
## WordPress.org Preparation
The original launch of this version of the boilerplate included the folder structure needed for using your plugin on WordPress.org. That folder structure has been moved to its own repo here: https://github.com/DevinVinson/Plugin-Directory-Boilerplate
## Recommended Tools
### i18n Tools
The WordPress Plugin Boilerplate uses a variable to store the text domain used when internationalizing strings throughout the Boilerplate. To take advantage of this method, there are tools that are recommended for providing correct, translatable files:
* [Poedit](http://www.poedit.net/)
* [makepot](http://i18n.svn.wordpress.org/tools/trunk/)
* [i18n](https://github.com/grappler/i18n)
Any of the above tools should provide you with the proper tooling to internationalize the plugin.
## License
The WordPress Plugin Boilerplate is licensed under the GPL v2 or later.
> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License, version 2, as published by the Free Software Foundation.
> This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
> You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
A copy of the license is included in the root of the plugins directory. The file is named `LICENSE`.
## Important Notes
### Licensing
The WordPress Plugin Boilerplate is licensed under the GPL v2 or later; however, if you opt to use third-party code that is not compatible with v2, then you may need to switch to using code that is GPL v3 compatible.
For reference, [here's a discussion](http://make.wordpress.org/themes/2013/03/04/licensing-note-apache-and-gpl/) that covers the Apache 2.0 License used by [Bootstrap](http://twitter.github.io/bootstrap/).
### Includes
Note that if you include your own classes, or third-party libraries, there are three locations in which said files may go:
* `plugin-name/includes` is where functionality shared between the admin area and the public-facing parts of the site reside
* `plugin-name/admin` is for all admin-specific functionality
* `plugin-name/public` is for all public-facing functionality
Note that previous versions of the Boilerplate did not include `Plugin_Name_Loader` but this class is used to register all filters and actions with WordPress.
The example code provided shows how to register your hooks with the Loader class.
### What About Other Features?
The previous version of the WordPress Plugin Boilerplate included support for a number of different projects such as the [GitHub Updater](https://github.com/afragen/github-updater).
These tools are not part of the core of this Boilerplate, as I see them as being additions, forks, or other contributions to the Boilerplate.
The same is true of using tools like Grunt, Composer, etc. These are all fantastic tools, but not everyone uses them. In order to keep the core Boilerplate as light as possible, these features have been removed and will be introduced in other editions, and will be listed and maintained on the project homepage.
# Credits
The WordPress Plugin Boilerplate was started in 2011 by [Tom McFarlin](http://twitter.com/tommcfarlin/) and has since included a number of great contributions. In March of 2015 the project was handed over by Tom to Devin Vinson.
The current version of the Boilerplate was developed in conjunction with [Josh Eaton](https://twitter.com/jjeaton), [Ulrich Pogson](https://twitter.com/grapplerulrich), and [Brad Vincent](https://twitter.com/themergency).
The homepage is based on a design as provided by [HTML5Up](http://html5up.net), the Boilerplate logo was designed by Rob McCaskill of [BungaWeb](http://bungaweb.com), and the site `favicon` was created by [Mickey Kay](https://twitter.com/McGuive7).
## Documentation, FAQs, and More
If youre interested in writing any documentation or creating tutorials please [let me know](http://devinvinson.com/contact/) .

339
plugin-name/LICENSE.txt Normal file
View file

@ -0,0 +1,339 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License.

114
plugin-name/README.txt Normal file
View file

@ -0,0 +1,114 @@
=== Plugin Name ===
Contributors: (this should be a list of wordpress.org userid's)
Donate link: http://example.com/
Tags: comments, spam
Requires at least: 3.0.1
Tested up to: 3.4
Stable tag: 4.3
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Here is a short description of the plugin. This should be no more than 150 characters. No markup here.
== Description ==
This is the long description. No limit, and you can use Markdown (as well as in the following sections).
For backwards compatibility, if this section is missing, the full length of the short description will be used, and
Markdown parsed.
A few notes about the sections above:
* "Contributors" is a comma separated list of wp.org/wp-plugins.org usernames
* "Tags" is a comma separated list of tags that apply to the plugin
* "Requires at least" is the lowest version that the plugin will work on
* "Tested up to" is the highest version that you've *successfully used to test the plugin*. Note that it might work on
higher versions... this is just the highest one you've verified.
* Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use `/trunk/` for
stable.
Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, so
if the `/trunk/readme.txt` file says that the stable tag is `4.3`, then it is `/tags/4.3/readme.txt` that'll be used
for displaying information about the plugin. In this situation, the only thing considered from the trunk `readme.txt`
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk `readme.txt` to reflect changes in
your in-development version, without having that information incorrectly disclosed about the current stable version
that lacks those changes -- as long as the trunk's `readme.txt` points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where
you put the stable version, in order to eliminate any doubt.
== Installation ==
This section describes how to install the plugin and get it working.
e.g.
1. Upload `plugin-name.php` to the `/wp-content/plugins/` directory
1. Activate the plugin through the 'Plugins' menu in WordPress
1. Place `<?php do_action('plugin_name_hook'); ?>` in your templates
== Frequently Asked Questions ==
= A question that someone might have =
An answer to that question.
= What about foo bar? =
Answer to foo bar dilemma.
== Screenshots ==
1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from
the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets
directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png`
(or jpg, jpeg, gif).
2. This is the second screen shot
== Changelog ==
= 1.0 =
* A change since the previous version.
* Another change.
= 0.5 =
* List versions from most recent at top to oldest at bottom.
== Upgrade Notice ==
= 1.0 =
Upgrade notices describe the reason a user should upgrade. No more than 300 characters.
= 0.5 =
This version fixes a security related bug. Upgrade immediately.
== Arbitrary section ==
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated
plugins where more information needs to be conveyed that doesn't fit into the categories of "description" or
"installation." Arbitrary sections will be shown below the built-in sections outlined above.
== A brief Markdown Example ==
Ordered list:
1. Some feature
1. Another feature
1. Something else about the plugin
Unordered list:
* something
* something else
* third thing
Here's a link to [WordPress](http://wordpress.org/ "Your favorite software") and one to [Markdown's Syntax Documentation][markdown syntax].
Titles are optional, naturally.
[markdown syntax]: http://daringfireball.net/projects/markdown/syntax
"Markdown is what the parser uses to process much of the readme file"
Markdown uses email style notation for blockquotes and I've been told:
> Asterisks for *emphasis*. Double it up for **strong**.
`<?php code(); // goes in backticks ?>`

View file

@ -0,0 +1,103 @@
<?php
/**
* The admin-specific functionality of the plugin.
*
* @link http://example.com
* @since 1.0.0
*
* @package Plugin_Name
* @subpackage Plugin_Name/admin
*/
/**
* The admin-specific functionality of the plugin.
*
* Defines the plugin name, version, and two examples hooks for how to
* enqueue the admin-specific stylesheet and JavaScript.
*
* @package Plugin_Name
* @subpackage Plugin_Name/admin
* @author Your Name <email@example.com>
*/
class Plugin_Name_Admin {
/**
* The ID of this plugin.
*
* @since 1.0.0
* @access private
* @var string $plugin_name The ID of this plugin.
*/
private $plugin_name;
/**
* The version of this plugin.
*
* @since 1.0.0
* @access private
* @var string $version The current version of this plugin.
*/
private $version;
/**
* Initialize the class and set its properties.
*
* @since 1.0.0
* @param string $plugin_name The name of this plugin.
* @param string $version The version of this plugin.
*/
public function __construct( $plugin_name, $version ) {
$this->plugin_name = $plugin_name;
$this->version = $version;
}
/**
* Register the stylesheets for the admin area.
*
* @since 1.0.0
*/
public function enqueue_styles() {
/**
* This function is provided for demonstration purposes only.
*
* An instance of this class should be passed to the run() function
* defined in Plugin_Name_Loader as all of the hooks are defined
* in that particular class.
*
* The Plugin_Name_Loader will then create the relationship
* between the defined hooks and the functions defined in this
* class.
*/
wp_enqueue_style( $this->plugin_name, plugin_dir_url( __FILE__ ) . 'css/plugin-name-admin.css', array(), $this->version, 'all' );
}
/**
* Register the JavaScript for the admin area.
*
* @since 1.0.0
*/
public function enqueue_scripts() {
/**
* This function is provided for demonstration purposes only.
*
* An instance of this class should be passed to the run() function
* defined in Plugin_Name_Loader as all of the hooks are defined
* in that particular class.
*
* The Plugin_Name_Loader will then create the relationship
* between the defined hooks and the functions defined in this
* class.
*/
wp_enqueue_script( $this->plugin_name, plugin_dir_url( __FILE__ ) . 'js/plugin-name-admin.js', array( 'jquery' ), $this->version, false );
}
}

View file

@ -0,0 +1,4 @@
/**
* All of the CSS for your admin-specific functionality should be
* included in this file.
*/

View file

@ -0,0 +1 @@
<?php // Silence is golden

View file

@ -0,0 +1,32 @@
(function( $ ) {
'use strict';
/**
* All of the code for your admin-facing JavaScript source
* should reside in this file.
*
* Note: It has been assumed you will write jQuery code here, so the
* $ function reference has been prepared for usage within the scope
* of this function.
*
* This enables you to define handlers, for when the DOM is ready:
*
* $(function() {
*
* });
*
* When the window is loaded:
*
* $( window ).load(function() {
*
* });
*
* ...and/or other possibilities.
*
* Ideally, it is not considered best practise to attach more than a
* single DOM-ready or window-load handler for a particular page.
* Although scripts in the WordPress core, Plugins and Themes may be
* practising this, we should strive to set a better example in our own work.
*/
})( jQuery );

View file

@ -0,0 +1,16 @@
<?php
/**
* Provide a admin area view for the plugin
*
* This file is used to markup the admin-facing aspects of the plugin.
*
* @link http://example.com
* @since 1.0.0
*
* @package Plugin_Name
* @subpackage Plugin_Name/admin/partials
*/
?>
<!-- This file should primarily consist of HTML with a little bit of PHP. -->

View file

@ -0,0 +1,36 @@
<?php
/**
* Fired during plugin activation
*
* @link http://example.com
* @since 1.0.0
*
* @package Plugin_Name
* @subpackage Plugin_Name/includes
*/
/**
* Fired during plugin activation.
*
* This class defines all code necessary to run during the plugin's activation.
*
* @since 1.0.0
* @package Plugin_Name
* @subpackage Plugin_Name/includes
* @author Your Name <email@example.com>
*/
class Plugin_Name_Activator {
/**
* Short Description. (use period)
*
* Long Description.
*
* @since 1.0.0
*/
public static function activate() {
}
}

View file

@ -0,0 +1,36 @@
<?php
/**
* Fired during plugin deactivation
*
* @link http://example.com
* @since 1.0.0
*
* @package Plugin_Name
* @subpackage Plugin_Name/includes
*/
/**
* Fired during plugin deactivation.
*
* This class defines all code necessary to run during the plugin's deactivation.
*
* @since 1.0.0
* @package Plugin_Name
* @subpackage Plugin_Name/includes
* @author Your Name <email@example.com>
*/
class Plugin_Name_Deactivator {
/**
* Short Description. (use period)
*
* Long Description.
*
* @since 1.0.0
*/
public static function deactivate() {
}
}

View file

@ -0,0 +1,47 @@
<?php
/**
* Define the internationalization functionality
*
* Loads and defines the internationalization files for this plugin
* so that it is ready for translation.
*
* @link http://example.com
* @since 1.0.0
*
* @package Plugin_Name
* @subpackage Plugin_Name/includes
*/
/**
* Define the internationalization functionality.
*
* Loads and defines the internationalization files for this plugin
* so that it is ready for translation.
*
* @since 1.0.0
* @package Plugin_Name
* @subpackage Plugin_Name/includes
* @author Your Name <email@example.com>
*/
class Plugin_Name_i18n {
/**
* Load the plugin text domain for translation.
*
* @since 1.0.0
*/
public function load_plugin_textdomain() {
load_plugin_textdomain(
'plugin-name',
false,
dirname( dirname( plugin_basename( __FILE__ ) ) ) . '/languages/'
);
}
}

View file

@ -0,0 +1,155 @@
<?php
/**
* Register all actions and filters for the plugin
*
* @link http://example.com
* @since 1.0.0
*
* @package Plugin_Name
* @subpackage Plugin_Name/includes
*/
/**
* Register all actions and filters for the plugin.
*
* Maintain a list of all hooks that are registered throughout
* the plugin, and register them with the WordPress API. Call the
* run function to execute the list of actions and filters.
*
* @package Plugin_Name
* @subpackage Plugin_Name/includes
* @author Your Name <email@example.com>
*/
class Plugin_Name_Loader {
/**
* The array of actions registered with WordPress.
*
* @since 1.0.0
* @access protected
* @var array $actions The actions registered with WordPress to fire when the plugin loads.
*/
protected $actions;
/**
* The array of filters registered with WordPress.
*
* @since 1.0.0
* @access protected
* @var array $filters The filters registered with WordPress to fire when the plugin loads.
*/
protected $filters;
/**
* The array of shortcode registered with WordPress.
*
* @since 1.0.0
* @access protected
* @var array $shortcodes The shortcode registered with WordPress to fire when the plugin loads.
*/
protected $shortcodes;
/**
* Initialize the collections used to maintain the actions and filters.
*
* @since 1.0.0
*/
public function __construct() {
$this->actions = array();
$this->filters = array();
$this->shortcodes = array();
}
/**
* Add a new action to the collection to be registered with WordPress.
*
* @since 1.0.0
* @param string $hook The name of the WordPress action that is being registered.
* @param object $component A reference to the instance of the object on which the action is defined.
* @param string $callback The name of the function definition on the $component.
* @param int $priority Optional. The priority at which the function should be fired. Default is 10.
* @param int $accepted_args Optional. The number of arguments that should be passed to the $callback. Default is 1.
*/
public function add_action( $hook, $component, $callback, $priority = 10, $accepted_args = 1 ) {
$this->actions = $this->add( $this->actions, $hook, $component, $callback, $priority, $accepted_args );
}
/**
* Add a new filter to the collection to be registered with WordPress.
*
* @since 1.0.0
* @param string $hook The name of the WordPress filter that is being registered.
* @param object $component A reference to the instance of the object on which the filter is defined.
* @param string $callback The name of the function definition on the $component.
* @param int $priority Optional. The priority at which the function should be fired. Default is 10.
* @param int $accepted_args Optional. The number of arguments that should be passed to the $callback. Default is 1
*/
public function add_filter( $hook, $component, $callback, $priority = 10, $accepted_args = 1 ) {
$this->filters = $this->add( $this->filters, $hook, $component, $callback, $priority, $accepted_args );
}
/**
* Add a new shortcode to the collection to be registered with WordPress
*
* @since 1.0.0
* @param string $tag The name of the new shortcode.
* @param object $component A reference to the instance of the object on which the shortcode is defined.
* @param string $callback The name of the function that defines the shortcode.
*/
public function add_shortcode( $tag, $component, $callback, $priority = 10, $accepted_args = 1 ) {
$this->shortcodes = $this->add( $this->shortcodes, $tag, $component, $callback, $priority, $accepted_args );
}
/**
* A utility function that is used to register the actions and hooks into a single
* collection.
*
* @since 1.0.0
* @access private
* @param array $hooks The collection of hooks that is being registered (that is, actions or filters).
* @param string $hook The name of the WordPress filter that is being registered.
* @param object $component A reference to the instance of the object on which the filter is defined.
* @param string $callback The name of the function definition on the $component.
* @param int $priority The priority at which the function should be fired.
* @param int $accepted_args The number of arguments that should be passed to the $callback.
* @return array The collection of actions and filters registered with WordPress.
*/
private function add( $hooks, $hook, $component, $callback, $priority, $accepted_args ) {
$hooks[] = array(
'hook' => $hook,
'component' => $component,
'callback' => $callback,
'priority' => $priority,
'accepted_args' => $accepted_args
);
return $hooks;
}
/**
* Register the filters and actions with WordPress.
*
* @since 1.0.0
*/
public function run() {
foreach ( $this->filters as $hook ) {
add_filter( $hook['hook'], array( $hook['component'], $hook['callback'] ), $hook['priority'], $hook['accepted_args'] );
}
foreach ( $this->actions as $hook ) {
add_action( $hook['hook'], array( $hook['component'], $hook['callback'] ), $hook['priority'], $hook['accepted_args'] );
}
foreach ( $this->shortcodes as $hook ) {
add_shortcode( $hook['hook'], array( $hook['component'], $hook['callback'] ), $hook['priority'], $hook['accepted_args'] );
}
}
}

View file

@ -0,0 +1,220 @@
<?php
/**
* The file that defines the core plugin class
*
* A class definition that includes attributes and functions used across both the
* public-facing side of the site and the admin area.
*
* @link http://example.com
* @since 1.0.0
*
* @package Plugin_Name
* @subpackage Plugin_Name/includes
*/
/**
* The core plugin class.
*
* This is used to define internationalization, admin-specific hooks, and
* public-facing site hooks.
*
* Also maintains the unique identifier of this plugin as well as the current
* version of the plugin.
*
* @since 1.0.0
* @package Plugin_Name
* @subpackage Plugin_Name/includes
* @author Your Name <email@example.com>
*/
class Plugin_Name {
/**
* The loader that's responsible for maintaining and registering all hooks that power
* the plugin.
*
* @since 1.0.0
* @access protected
* @var Plugin_Name_Loader $loader Maintains and registers all hooks for the plugin.
*/
protected $loader;
/**
* The unique identifier of this plugin.
*
* @since 1.0.0
* @access protected
* @var string $plugin_name The string used to uniquely identify this plugin.
*/
protected $plugin_name;
/**
* The current version of the plugin.
*
* @since 1.0.0
* @access protected
* @var string $version The current version of the plugin.
*/
protected $version;
/**
* Define the core functionality of the plugin.
*
* Set the plugin name and the plugin version that can be used throughout the plugin.
* Load the dependencies, define the locale, and set the hooks for the admin area and
* the public-facing side of the site.
*
* @since 1.0.0
*/
public function __construct() {
if ( defined( 'PLUGIN_NAME_VERSION' ) ) {
$this->version = PLUGIN_NAME_VERSION;
} else {
$this->version = '1.0.0';
}
$this->plugin_name = 'plugin-name';
$this->load_dependencies();
$this->set_locale();
$this->define_admin_hooks();
$this->define_public_hooks();
}
/**
* Load the required dependencies for this plugin.
*
* Include the following files that make up the plugin:
*
* - Plugin_Name_Loader. Orchestrates the hooks of the plugin.
* - Plugin_Name_i18n. Defines internationalization functionality.
* - Plugin_Name_Admin. Defines all hooks for the admin area.
* - Plugin_Name_Public. Defines all hooks for the public side of the site.
*
* Create an instance of the loader which will be used to register the hooks
* with WordPress.
*
* @since 1.0.0
* @access private
*/
private function load_dependencies() {
/**
* The class responsible for orchestrating the actions and filters of the
* core plugin.
*/
require_once plugin_dir_path( dirname( __FILE__ ) ) . 'includes/class-plugin-name-loader.php';
/**
* The class responsible for defining internationalization functionality
* of the plugin.
*/
require_once plugin_dir_path( dirname( __FILE__ ) ) . 'includes/class-plugin-name-i18n.php';
/**
* The class responsible for defining all actions that occur in the admin area.
*/
require_once plugin_dir_path( dirname( __FILE__ ) ) . 'admin/class-plugin-name-admin.php';
/**
* The class responsible for defining all actions that occur in the public-facing
* side of the site.
*/
require_once plugin_dir_path( dirname( __FILE__ ) ) . 'public/class-plugin-name-public.php';
$this->loader = new Plugin_Name_Loader();
}
/**
* Define the locale for this plugin for internationalization.
*
* Uses the Plugin_Name_i18n class in order to set the domain and to register the hook
* with WordPress.
*
* @since 1.0.0
* @access private
*/
private function set_locale() {
$plugin_i18n = new Plugin_Name_i18n();
$this->loader->add_action( 'plugins_loaded', $plugin_i18n, 'load_plugin_textdomain' );
}
/**
* Register all of the hooks related to the admin area functionality
* of the plugin.
*
* @since 1.0.0
* @access private
*/
private function define_admin_hooks() {
$plugin_admin = new Plugin_Name_Admin( $this->get_plugin_name(), $this->get_version() );
$this->loader->add_action( 'admin_enqueue_scripts', $plugin_admin, 'enqueue_styles' );
$this->loader->add_action( 'admin_enqueue_scripts', $plugin_admin, 'enqueue_scripts' );
}
/**
* Register all of the hooks related to the public-facing functionality
* of the plugin.
*
* @since 1.0.0
* @access private
*/
private function define_public_hooks() {
$plugin_public = new Plugin_Name_Public( $this->get_plugin_name(), $this->get_version() );
$this->loader->add_action( 'wp_enqueue_scripts', $plugin_public, 'enqueue_styles' );
$this->loader->add_action( 'wp_enqueue_scripts', $plugin_public, 'enqueue_scripts' );
$this->loader->add_shortcode( 'plugin-name-shortcode', $plugin_public, 'plugin_name_shortcode_func' );
}
/**
* Run the loader to execute all of the hooks with WordPress.
*
* @since 1.0.0
*/
public function run() {
$this->loader->run();
}
/**
* The name of the plugin used to uniquely identify it within the context of
* WordPress and to define internationalization functionality.
*
* @since 1.0.0
* @return string The name of the plugin.
*/
public function get_plugin_name() {
return $this->plugin_name;
}
/**
* The reference to the class that orchestrates the hooks with the plugin.
*
* @since 1.0.0
* @return Plugin_Name_Loader Orchestrates the hooks of the plugin.
*/
public function get_loader() {
return $this->loader;
}
/**
* Retrieve the version number of the plugin.
*
* @since 1.0.0
* @return string The version number of the plugin.
*/
public function get_version() {
return $this->version;
}
}

View file

@ -0,0 +1 @@
<?php // Silence is golden

1
plugin-name/index.php Normal file
View file

@ -0,0 +1 @@
<?php // Silence is golden

View file

@ -0,0 +1,82 @@
<?php
/**
* The plugin bootstrap file
*
* This file is read by WordPress to generate the plugin information in the plugin
* admin area. This file also includes all of the dependencies used by the plugin,
* registers the activation and deactivation functions, and defines a function
* that starts the plugin.
*
* @link http://example.com
* @since 1.0.0
* @package Plugin_Name
*
* @wordpress-plugin
* Plugin Name: WordPress Plugin Boilerplate
* Plugin URI: http://example.com/plugin-name-uri/
* Description: This is a short description of what the plugin does. It's displayed in the WordPress admin area.
* Version: 1.0.0
* Author: Your Name or Your Company
* Author URI: http://example.com/
* License: GPL-2.0+
* License URI: http://www.gnu.org/licenses/gpl-2.0.txt
* Text Domain: plugin-name
* Domain Path: /languages
*/
// If this file is called directly, abort.
if ( ! defined( 'WPINC' ) ) {
die;
}
/**
* Currently plugin version.
* Start at version 1.0.0 and use SemVer - https://semver.org
* Rename this for your plugin and update it as you release new versions.
*/
define( 'PLUGIN_NAME_VERSION', '1.0.0' );
/**
* The code that runs during plugin activation.
* This action is documented in includes/class-plugin-name-activator.php
*/
function activate_plugin_name() {
require_once plugin_dir_path( __FILE__ ) . 'includes/class-plugin-name-activator.php';
Plugin_Name_Activator::activate();
}
/**
* The code that runs during plugin deactivation.
* This action is documented in includes/class-plugin-name-deactivator.php
*/
function deactivate_plugin_name() {
require_once plugin_dir_path( __FILE__ ) . 'includes/class-plugin-name-deactivator.php';
Plugin_Name_Deactivator::deactivate();
}
register_activation_hook( __FILE__, 'activate_plugin_name' );
register_deactivation_hook( __FILE__, 'deactivate_plugin_name' );
/**
* The core plugin class that is used to define internationalization,
* admin-specific hooks, and public-facing site hooks.
*/
require plugin_dir_path( __FILE__ ) . 'includes/class-plugin-name.php';
/**
* Begins execution of the plugin.
*
* Since everything within the plugin is registered via hooks,
* then kicking off the plugin from this point in the file does
* not affect the page life cycle.
*
* @since 1.0.0
*/
function run_plugin_name() {
$plugin = new Plugin_Name();
$plugin->run();
}
run_plugin_name();

View file

@ -0,0 +1,117 @@
<?php
/**
* The public-facing functionality of the plugin.
*
* @link http://example.com
* @since 1.0.0
*
* @package Plugin_Name
* @subpackage Plugin_Name/public
*/
/**
* The public-facing functionality of the plugin.
*
* Defines the plugin name, version, and two examples hooks for how to
* enqueue the public-facing stylesheet and JavaScript.
*
* @package Plugin_Name
* @subpackage Plugin_Name/public
* @author Your Name <email@example.com>
*/
class Plugin_Name_Public {
/**
* The ID of this plugin.
*
* @since 1.0.0
* @access private
* @var string $plugin_name The ID of this plugin.
*/
private $plugin_name;
/**
* The version of this plugin.
*
* @since 1.0.0
* @access private
* @var string $version The current version of this plugin.
*/
private $version;
/**
* Initialize the class and set its properties.
*
* @since 1.0.0
* @param string $plugin_name The name of the plugin.
* @param string $version The version of this plugin.
*/
public function __construct( $plugin_name, $version ) {
$this->plugin_name = $plugin_name;
$this->version = $version;
}
/**
* Register the stylesheets for the public-facing side of the site.
*
* @since 1.0.0
*/
public function enqueue_styles() {
/**
* This function is provided for demonstration purposes only.
*
* An instance of this class should be passed to the run() function
* defined in Plugin_Name_Loader as all of the hooks are defined
* in that particular class.
*
* The Plugin_Name_Loader will then create the relationship
* between the defined hooks and the functions defined in this
* class.
*/
wp_enqueue_style( $this->plugin_name, plugin_dir_url( __FILE__ ) . 'css/plugin-name-public.css', array(), $this->version, 'all' );
}
/**
* Register the JavaScript for the public-facing side of the site.
*
* @since 1.0.0
*/
public function enqueue_scripts() {
/**
* This function is provided for demonstration purposes only.
*
* An instance of this class should be passed to the run() function
* defined in Plugin_Name_Loader as all of the hooks are defined
* in that particular class.
*
* The Plugin_Name_Loader will then create the relationship
* between the defined hooks and the functions defined in this
* class.
*/
wp_enqueue_script( $this->plugin_name, plugin_dir_url( __FILE__ ) . 'js/plugin-name-public.js', array( 'jquery' ), $this->version, false );
}
/**
* Shortcode processing function.
* Shortcode can take arguments like [plugin-name-shortcode argm='123']
*/
public function plugin_name_shortcode_func($atts) {
$a = shortcode_atts( array(
'argm' => '0',
), $atts
);
return (
$a['argm']
);
}
}

View file

@ -0,0 +1,4 @@
/**
* All of the CSS for your public-facing functionality should be
* included in this file.
*/

View file

@ -0,0 +1 @@
<?php // Silence is golden

View file

@ -0,0 +1,32 @@
(function( $ ) {
'use strict';
/**
* All of the code for your public-facing JavaScript source
* should reside in this file.
*
* Note: It has been assumed you will write jQuery code here, so the
* $ function reference has been prepared for usage within the scope
* of this function.
*
* This enables you to define handlers, for when the DOM is ready:
*
* $(function() {
*
* });
*
* When the window is loaded:
*
* $( window ).load(function() {
*
* });
*
* ...and/or other possibilities.
*
* Ideally, it is not considered best practise to attach more than a
* single DOM-ready or window-load handler for a particular page.
* Although scripts in the WordPress core, Plugins and Themes may be
* practising this, we should strive to set a better example in our own work.
*/
})( jQuery );

View file

@ -0,0 +1,16 @@
<?php
/**
* Provide a public-facing view for the plugin
*
* This file is used to markup the public-facing aspects of the plugin.
*
* @link http://example.com
* @since 1.0.0
*
* @package Plugin_Name
* @subpackage Plugin_Name/public/partials
*/
?>
<!-- This file should primarily consist of HTML with a little bit of PHP. -->

31
plugin-name/uninstall.php Normal file
View file

@ -0,0 +1,31 @@
<?php
/**
* Fired when the plugin is uninstalled.
*
* When populating this file, consider the following flow
* of control:
*
* - This method should be static
* - Check if the $_REQUEST content actually is the plugin name
* - Run an admin referrer check to make sure it goes through authentication
* - Verify the output of $_GET makes sense
* - Repeat with other user roles. Best directly by using the links/query string parameters.
* - Repeat things for multisite. Once for a single site in the network, once sitewide.
*
* This file may be updated more in future version of the Boilerplate; however, this is the
* general skeleton and outline for how the file should work.
*
* For more information, see the following discussion:
* https://github.com/tommcfarlin/WordPress-Plugin-Boilerplate/pull/123#issuecomment-28541913
*
* @link http://example.com
* @since 1.0.0
*
* @package Plugin_Name
*/
// If uninstall not called from WordPress, then exit.
if ( ! defined( 'WP_UNINSTALL_PLUGIN' ) ) {
exit;
}