Viewing 2 replies - 1 through 2 (of 2 total)
  • Please consider your review policy.

    This causes the plugin not to work if a custom content directory has been set.

    For a custom modification, that this free plugin is not compatible with, and you don get answers for your private needs, You are Rating this plugin with ONE STAR

    I get sad when I see this kind of reviews. This is a community with people who contributes and offer solutions and their work. Please be constructive in your footprints on this respority.

    [ Signature moderated. ]

    Thread Starter B.

    (@bandonrandon)

    Jonas,

    It was never my intention to make you sad or to hurt your feelings in any way. However, respecting the wp-content directory is part of the WordPress coding standards and something I (and others) feel that should be part of any plugin.

    From the Codex:

    It’s important to remember that WordPress allows users to place their wp-content directory anywhere they want, so you must never assume that plugins will be in wp-content/plugins, or that uploads will be in wp-content/uploads, or that themes will be in wp-content/themes.

    The ability to move the wp-content directory has been avalible to users since WP 2.6 (released July 2008) and is not a “custom modification” at least not an unusual one.

    I’d be happy to change my rating once this issue has been resolved. I really do think this is a great plugin. Yet as it is, this bug make the plugin not function for my users.

    I feel I should also point out I attempted to contact the Plugin authors and posted a support request a full month before writing the review.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Hard Coded wp-content Directory’ is closed to new replies.