Also i have seen this error:
Warning: is_readable() [function.is-readable]: open_basedir restriction in effect. File(C:\Inetpub\vhosts\xyz.de\httpdocs\wordpress/wp-content/plugins/C:\Inetpub\vhosts\xyz.de\httpdocs\wordpress\wp-content\plugins\nextgen-gallery\products\photocrati_nextgen\modules\i18n\lang/nggallery-en_US.mo) is not within the allowed path(s): (C:/Inetpub/vhosts/xyz.de\;C:\Windows\Temp\) in C:\Inetpub\vhosts\xyz.de\httpdocs\wordpress\wp-includes\l10n.php on line 457
What should i do to solve this problem?
@daniel7 – This may need to be addressed with your web host service as it appears there is a configuration issue with what paths are accessible in your WordPress installation.
Have you brought this issue to their attention?
Thanks!
– Cais.
Ok. u mean something like this.
add the ../../wordpress directory to open_base_dir in the phpconfig file?
now i have WP installed in root/httpdocs directtory…
if i install the plugin i got an error:
500 – Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
What to do?
memory_limit : 128 MB
open_basedir : C:/Inetpub/vhosts/domain\;C:\Windows\Temp\
@daniel7 – Server configuration are a bit out of my scope of support, I always recommend going to the web host provider for suggestions and recommendation on how best to make any changes to a specific site’s configuration. They should know their equipment best and be able to provide a direct answer (rather than me giving some sort of WAG recommendation).
Thanks!
– Cais.
can u tell me what i´ve to check on server settings.
what is exactly needed fpr NextGen Gallery?
@daniel7 – What are the details you see under Gallery > Overview (in the right sidebar)?
– Cais.
if i activate the nextgen plugin, i get an internal 500 server error..
so i cannot see details in Gallery…
best regards
@daniel7 – Does the site work correctly for all other plugins and your theme when NextGEN Gallery is deactivated?
Have you confirmed with your web hosting service the server environment will properly handle a WordPress installation?
Have you tried deactivating all of your plugins and temporarily switching to a default WordPress Twenty series theme then activating NextGEN Gallery?
– Cais.
I´ve tried a new WP installation and then activated only the NextGen Plugin. I got this error also.
Already tried to disable other plugins and then install the NextGen.
After this error i must delete or rename the NextGen folder.
What is exactly necessary for the NextGen plugin?
best regards
@daniel7 – Aside from a correctly configured server environment for a WordPress installation and a theme that meets WordPress Best Practices there is not much more that should be necessary.
– Cais.
I don’t think there’s a permission problem with the directory allowed by the open_basedir restriction in effect… The file it’s complaining about simply doesn’t exist because the path is wrong:
“C:\Inetpub\vhosts\xyz.de\httpdocs\wordpress/wp-content/plugins/C:\Inetpub\vhosts\xyz.de\httpdocs\wordpress\wp-content\plugins\nextgen-gallery\products\photocrati_nextgen\modules\i18n\lang/nggallery-en_US.mo”
This looks like two paths concatenated together. Note the two instances of “C:” in the path. If it’s supposed to specify two different paths to search, shouldn’t there be a delimiter between the two? It’s also suspicious that there’s a mix of directions for the slashes. I think it looks like the path wasn’t formed properly and then the system then can’t find the file in that bad path.
@alightner – Thanks for that observation and it is most likely indicative of the issue to some degree, but as it is that “duplicate” path also tends to point to a server environment concern as well which is not easily diagnosed resolved via these forums.
@daniel7 – If you are still experiencing these issues please feel free to submit a Bug Report (http://www.nextgen-gallery.com/report-bug/ … please reference this topic) with your site specifics so we can try to help you with this.
We will likely need log in (and FTP) credentials for your WordPress installation to have a closer look at what is going on, please include those with your Bug Report.
Thanks!
– Cais.
I figured it out… my apologies to the NextGen team as this is really a pretty nasty WP bug for the windows platform that it appears you got blamed for 😉 The latest WP 3.9.1 (and who knows when this began) has hard coded slashes in their directory paths.
For example:
Edit both: {DOCROOT}\wp_load.php & {DOCROOT}\wp_config.php
Find: define( 'ABSPATH', dirname(__FILE__) . '/' );
Replace with: define('ABSPATH', dirname(__FILE__) . DIRECTORY_SEPARATOR);
Be careful with the following “finds” you are looking for things that end in _DIR NOT _URL!!!
Edit {DOCROOT}\wp-includes\default_constants.php
Find: define( 'WP_PLUGIN_DIR', WP_CONTENT_DIR . '/plugins' );
Replace with: define( 'WP_PLUGIN_DIR', WP_CONTENT_DIR . DIRECTORY_SEPARATOR . 'plugins' );
Find: define( 'PLUGINDIR', 'wp-content/plugins' );
Replace with: define( 'PLUGINDIR', 'wp-content'.DIRECTORY_SEPARATOR .'plugins' );
Find: define( 'WPMU_PLUGIN_DIR', WP_CONTENT_DIR . '/mu-plugins' );
Replace with: define( 'WPMU_PLUGIN_DIR', WP_CONTENT_DIR . DIRECTORY_SEPARATOR .'mu-plugins' );
Find: define( 'MUPLUGINDIR', 'wp-content/mu-plugins' );
Replace with: define( 'MUPLUGINDIR', 'wp-content'.DIRECTORY_SEPARATOR .'mu-plugins' );
I can’t say for certain how many places where the wrong slash may be used in the WP software after finding this mess, but you get the idea what to do to fix it from that sampling of edits.
@alightner – Thanks, again! That is some good investigative work on your part.
We have tried to address all of the various issues we have found with “DIRECTORY_SEPARATOR” related issues and believe we have them addressed in our next release but I will still suggest to our developers to have a read over your findings.
As it is, if you see this as a WordPress core issue/bug I would suggest submitting it to core for review.
Thanks!!
– Cais.
