Errors when using custom content url and custom content dir

  • checho_acosta

    (@checho_acosta)


    10 years, 8 months ago

    We have a non conventional folder structure in our site, we have defined these two variables in the wp-config.php:
    define( ‘WP_CONTENT_DIR’, $_SERVER[‘DOCUMENT_ROOT’] . ‘/custom’ );
    define( ‘WP_CONTENT_URL’, ‘http://mysite.com/custom’ );

    And your are not taking them in to account.
    Because since we updated the plugin to the 2.0+ we are getting these errors:

    So in /wp-admin/admin.php?page=ngg_other_options I get this error:
    RuntimeException thrown
    /workspace/mysite/wp/custom/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_other_options/templates/image_options_tab.php is not a valid MVC template

    And in /wp-admin/admin.php?page=ngg_addgallery I get this error:
    RuntimeException thrown
    /workspace/mysite/wp/custom/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_addgallery_page/templates/upload_images.php is not a valid MVC template

    So, the path mysite/wp/custom doesn’t exist the right path is mysite/custom

    http://wordpress.org/plugins/nextgen-gallery/

Viewing 2 replies - 1 through 2 (of 2 total)
  • sebastien.barre

    (@sebastienbarre)

    10 years, 1 month ago

    Same issue here, my WordPress has its own dir, I’m getting the same errors.
    Did you find a workaround?

    More specifically, my install is:

    wp-testing/wordpress
wp-testing/wp-content/plugins/nextgen-gallery

    where wp-testing/wp-config.php starts with:

    define('WP_HOME',    'http://' . $_SERVER['SERVER_NAME']);
define('WP_SITEURL', 'http://' . $_SERVER['SERVER_NAME'] . '/wordpress');
define('WP_CONTENT_DIR', realpath($_SERVER['DOCUMENT_ROOT'] . '/wp-content'));
define('WP_CONTENT_URL', 'http://' . $_SERVER['SERVER_NAME'] . '/wp-content');

    Thread Starter checho_acosta

    (@checho_acosta)

    10 years ago

    Not yet, still using and older version of NextGEN

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Errors when using custom content url and custom content dir’ is closed to new replies.