search

DevinVinson / WordPress-Plugin-Boilerplate

[WordPress] A foundation for WordPress Plugin Development that aims to provide a clear and consistent guide for building your plugins.
http://wppb.io
7.67k stars 2.25k forks source link

Merge this plugin with WordPress-Settings-Sandbox #138

Closed spacedmonkey closed 10 years ago

spacedmonkey commented 10 years ago

This plugin is an amazing base for creating plugin, but it doesn't really give you best practice for creating admin settings. @tommcfarlin you have another plugin that does this WordPress-Settings-Sandbox. Would it be possible to have a couple of example settings in the current admin within boilerplate

xVGERx commented 10 years ago

I just stopped in to check for information regarding the same issue. I also found and went through the Word-Press-Settings-Sandbox but I can't seem to get it to work in a plugin. This boilerplate has been a tremendous help while learning to write plugins using best practices. I would like to be able to take it to the next level by adding admin settings. Any help on this would be greatly appreciated.

tommcfarlin commented 10 years ago

This plugin will not be merged with the WordPress Settings Sandbox as they serve two completely different purposes.

The WordPress Settings Sandbox is primarily meant to show how to create a WordPress Theme that leverages the Settings API. That said, I'll look into compatibility issues with it for WordPress 3.7 and commit any updates that are necessary for it to work.

The Boilerplate is meant to be a starting point for creating WordPress Plugins. Merging the two would make for a rather large, unfocused project.

When creating administrative options for WordPress Plugins, you use the Options API, Plugin API, and some of the other core APIs (such as those for registering menus).

This is something that we haven't really considered too much for this Boilerplate; however, we're currently planning on working on a site that will include documentation, examples, and other things on how to achieve certain tasks with the Boilerplate.

Additionally, we're looking at creating another directory out of which common files will be stored and shared for both front end and backend functionality.