Bug: plugin does not support non standard project structures

  • ralcus

    (@ralcus)


    12 years, 10 months ago

    Hi,

    In the WordPress install i work on we don’t use the standard directory structure. WordPress allows you to move the wp-content, plugins and themes directory as long as you tell wordpress in the wp_config file where you’ve moved them too.

    Inside a plugin to get the plugins url or directory the plugin needs to use the WordPress plugin url or plugin directory functions.

    On line 168 of /modules/module.post-type.php file and line 599 of /modules/module.ab-testing.php some path variables are setup using the string “wp-content”.

    This sets up the path variable incorrectly in my WP project because my content folder is not called “wp-content”. WordPress not only allows you to move the wp-content folder but also rename it to whatever you want. That’s why it’s best to rely on the WP helper functions relating to the plugin directory path.

    Thanks,

    carl.

    http://ww.wp.xz.cn/plugins/landing-pages/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author David Wells

    (@davidwells)

    12 years, 10 months ago

    Do you know how to reference the custom wp-content directory?

    Thread Starter ralcus

    (@ralcus)

    12 years, 6 months ago

    I’m not sure the best way to do that. Wouldn’t you only need the plugin directory? or do you store files in wp-content?

    If you do store stuff in the actual wp-content folder maybe you can get the plugin directory using plugin_dir_url() and then go up one.

    Not sure if this is the most ideal way to do it but as far as i know plugins always have to be in the wp-content folder whether of not that wp-content folder has been moved somewhere else or renamed.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Bug: plugin does not support non standard project structures’ is closed to new replies.