WordPress.org

Support

Support » Plugins and Hacks » NextGEN Gallery - WordPress Gallery Plugin » NextGen 2.0 update kills website

NextGen 2.0 update kills website

  • Hello, I just updated to wordpress 3.5.2 and nextgen 2.0 and having nextgen active causes my site to fail to load. Once I deactivate it, the site works fine. I can even access the nextgen setting in the wordpress admin panel. I have contact form 7 installed, but deactivating that has no effect on the problem. Also, when I click on the link to view images in the admin settings for next gen, I get an error that I don’t have permissions to view a file, but it doesn’t tell me which file it refers to. Any thoughts on how to fix this or is this a known issue? Thanks

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

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author photocrati

    @photocrati

    Hi –

    Just to clarify and get details:

    1) When you activated 2.0, you can still access your admin fine, but the front end is not loading?

    2) Are you seeing any error messages? if so, can you share them?

    3) Can you try deactivating all other plugins just for a moment, activate NG, and tell us if you still get the error. We’ve seen similar issues with plugins causing major conflicts. See: http://wordpress.org/support/topic/nextgen-20-update-kills-website?replies=1 for a list. But it may be another one not on that list.

    Thanks,
    Erick

    The website is down (www.apollosunguard.com) and I have tried to enter through the FTP route and it opens to the website, which displays the following error messages:

    Warning: is_readable() [function.is-readable]: open_basedir restriction in effect. File(D:\Inetpub\apollosunguard/wp-content/plugins/D:\Inetpub\apollosunguard\wp-content\plugins\nextgen-gallery\lang/nggallery-en_US.mo) is not within the allowed path(s): (D:\;C:\php5;C:\Temp;C:\Windows\Temp) in D:\Inetpub\apollosunguard\wp-includes\l10n.php on line 339

    Warning: require_once(D:\Inetpub\apollosunguard\wp-content\plugins\nextgen-gallery/wordpress_helpers.php) [function.require-once]: failed to open stream: No such file or directory in D:\Inetpub\apollosunguard\wp-content\plugins\nextgen-gallery\nggallery.php on line 122

    Fatal error: require_once() [function.require]: Failed opening required ‘D:\Inetpub\apollosunguard\wp-content\plugins\nextgen-gallery/wordpress_helpers.php’ (include_path=’.;c:\PHP5′) in D:\Inetpub\apollosunguard\wp-content\plugins\nextgen-gallery\nggallery.php on line 122

    Any suggestions?

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

    I am getting one of those messages too.

    Warning: is_readable() [function.is-readable]: open_basedir restriction in effect. File(C:\Inetpub\vhosts\eternityplusone.net\clinefest\pre2/wp-content/plugins/C:\Inetpub\vhosts\eternityplusone.net\clinefest\pre2\wp-content\plugins\nextgen-gallery\lang/nggallery-en_US.mo) is not within the allowed path(s): (C:\Inetpub\vhosts\eternityplusone.net\clinefest\) in C:\Inetpub\vhosts\eternityplusone.net\clinefest\pre2\wp-includes\l10n.php on line 339

    it goes away when nextGen is deactivated. I have read that it may be a permissions issue. I use IIS on 2008 server r2. Things were fine until I updated to the new version of wp and nextGen.

    I just deactivated the nextGen plugin and now I have a crashed site with the similar messages

    Warning: require_once(C:\Inetpub\vhosts\eternityplusone.net\clinefest\pre2\wp-content\plugins\nextgen-gallery/pope\lib\autoload.php) [function.require-once]: failed to open stream: No such file or directory in C:\Inetpub\vhosts\eternityplusone.net\clinefest\pre2\wp-content\plugins\nextgen-gallery\nggallery.php on line 129

    Fatal error: require_once() [function.require]: Failed opening required ‘C:\Inetpub\vhosts\eternityplusone.net\clinefest\pre2\wp-content\plugins\nextgen-gallery/pope\lib\autoload.php’ (include_path=’.;./includes;./pear’) in C:\Inetpub\vhosts\eternityplusone.net\clinefest\pre2\wp-content\plugins\nextgen-gallery\nggallery.php on line 129

    Looks like it happens because of absolute path to mo file concatenated with path to plugin dir:

    /wp-content/plugins/nextgen-gallery/nggallery.php

    function _register_hooks()
    	{
    		// Load text domain
    		load_plugin_textdomain(
    			NEXTGEN_GALLERY_I8N_DOMAIN,
    			true,
    			$this->directory_path('lang')
    		);

    $this->directory_path(‘lang’) – returns like ‘C:\Inetpub\vhosts\domain.tld\httpdocs\wordpress\wp-content\plugins\nextgen-gallery\lang’

    because it get path from __FILE__ constant.

    and than in /wp-includes/l10n.php

    function load_plugin_textdomain( $domain, $abs_rel_path = false, $plugin_rel_path = false ) {
    	$locale = apply_filters( 'plugin_locale', get_locale(), $domain );
    
    	if ( false !== $plugin_rel_path	) {
    		$path = WP_PLUGIN_DIR . '/' . trim( $plugin_rel_path, '/' );
    	} else if

    it can be easily fixed by changing in /wp-content/plugins/nextgen-gallery/nggallery.php call load_plugin_textdomain to:

    function _register_hooks()
    	{
    		// Load text domain
    		load_plugin_textdomain(
    			NEXTGEN_GALLERY_I8N_DOMAIN,
    			true,
    			plugin_basename($this->directory_path('lang'))
    		);

    _

    Thanks @oneumyvakin… it works like a charm!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘NextGen 2.0 update kills website’ is closed to new replies.
Skip to toolbar