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

New plugin-name/trunk folder structure at odds with instructions in README.md #213

Closed pjohanneson closed 10 years ago

pjohanneson commented 10 years ago

README.md states:

  1. Copy the plugin-name directory into your wp-content/plugins directory.
  2. In the WordPress dashboard, navigation to the Plugins page Locate the menu item that reads “The WordPress Plugin Boilerplate.”
  3. Click on Activate.

But with the new plugin-name/trunk directory structue, this doesn't work. The plugin doesn't appear in my backend plugins list. (I grabbed WP 4RC1 just in case it's supported there, but the plugin doesn't show up there either.)

Is it necessary to create a .php file in the plugin-name directory to load everything? Am I missing something?

nathanmarks commented 10 years ago

Try a symlink

On 2014-09-02, at 11:16 PM, "Patrick Johanneson" notifications@github.com<mailto:notifications@github.com> wrote:

README.md states:

  1. Copy the plugin-name directory into your wp-content/plugins directory.
  2. In the WordPress dashboard, navigation to the Plugins page Locate the menu item that reads "The WordPress Plugin Boilerplate."
  3. Click on Activate.

But with the new plugin-name/trunk directory structue, this doesn't work. The plugin doesn't appear in my backend plugins list. (I grabbed WP 4RC1 just in case it's supported there, but the plugin doesn't show up there either.)

Is it necessary to create a .php file in the plugin-name directory to load everything? Am I missing something?

Reply to this email directly or view it on GitHubhttps://github.com/tommcfarlin/WordPress-Plugin-Boilerplate/issues/213.

Japh commented 10 years ago

You're right, @vodou. The README.md probably needs updating. It does clarify the directory structure further down though under the Assets heading.

Basically, the new structure is designed for plugins that are to be uploaded to the WordPress.org plugin directory.

For use in a WordPress install, you may be able to try @nathanmarks' suggestion of a symlink. Something like this:

ln -s /path/to/plugin-name/trunk /path/to/wordpress/wp-content/plugins/plugin-name

I hope that helps!

grappler commented 10 years ago

@tommcfarlin - Could you also add a version for Windows. too?

mklink /J path\to\wp-content\plugins \path\to\WordPress-Plugin-Boilerplate\plugin-name

tommcfarlin commented 10 years ago

Sure!

Although should the command be (with trunk included) instead?

Like this: mklink /J path\to\wp-content\plugins \path\to\WordPress-Plugin-Boilerplate\trunk\plugin-name

grappler commented 10 years ago

Yea, Sorry, I missed that.

tommcfarlin commented 10 years ago

No worries - wanted to double-check before the commit!