WordPress.org

Support

Support » Plugins and Hacks » NextGEN Gallery - WordPress Gallery Plugin » [Resolved] array(1) { ["source"]=> array(1) { [0]=> string(24) "source should be present&q

[Resolved] array(1) { ["source"]=> array(1) { [0]=> string(24) "source should be present&q

Viewing 15 replies - 1 through 15 (of 17 total)
  • Hi karenfya

    I have the same problem since I’ve uptated the version of nextgen-gallery
    I don’t know the solution

    Plugin Author photocrati

    @photocrati

    Hi – are either of you using WordPress multisite? if so, can you please go ahead and update to our latest beta, the first with full multisite support:

    http://www.nextgen-gallery.com/nextgen-gallery-latest-beta

    If you are not on multisite, can you please consider submitting a bug report with WordPress and FTP login credentials so we could troubleshoot? Link to this thread and say Erick asked for credentials. Thanks.

    http://www.nextgen-gallery.com/report-bug/

    Hi

    Same problem after uptated in 2.0.18

    When nextgen is activated, slideshow gallery send me the error message

    array(1) { [“source”]=> array(1) { [0]=> string(24) “source should be present” } }

    ‘Invalid Displayed Gallery’

    When I déactivate nextgen, slideshow gallery are ok

    Same here (error went away upon deactivation – thanks for mentioning that, faribole). Not on a multisite. Using http://demo.studiopress.com/minimum/ child theme for Genesis. Bug report submitted.

    I had posted this in another entry but it seems nobody saw it, so I’ll repost here. Having the same issue, started at 2.0.14. Not on multisite.

    It can actually be found happening on NextGEN’s own website at: http://www.nextgen-gallery.com/nextgen-gallery-extension-plugins/

    I’m not running multisite, but I can’t give out login credentials without risking losing my job, sorry.

    @vmounier I got a kick out of it on their site too. A google search for the string shows quite a number of sites that are also affected by NextGEN.

    Same problem here. All slideshows disappeared and the above code is showing up instead.

    Thanks vmounier for noticing it in their own website.

    Please help!

    I notice this has now been fixed on NextGEN site at the link above, I wonder if 2.0.20 beta has taken care of that or it a conflict was found and removed, but it would be great if they could report here…

    Funny, I’m getting this same error, but it’s being triggered via shortcode for my Striking theme slider! Shortcode starts with “slideshow” (see code below) which is not in the NextGen shortcode as far as I can see. See here for example.

    I’m running NextGen Gallery 2.0.17 and NextGen Pro 1.0.6, with Striking 5.2.1 as our theme.

    Thanks,

    Jim P.

    echo str_replace(array('[raw]','[/raw]'),'',do_shortcode('[slideshow type="nivo" category="'.$cat.'" width="640" height="360" number="6" effect="random" slices="10" boxCols="8" boxRows="4" animSpeed="500" pauseTime="5000" controlNav="true" pauseOnHover="true" caption="true"]'));

    Hey all, I got the same error and discovered it was because I’d not typed the shortcode properly.

    I was using nggallery=1 instead of nggallery id=1.

    Hope that helps someone.

    @chadmaestro

    Thanks, you’re on the right track! This indeed solves the error. I thought version 2.0 would remain backward-compatible but maybe not after all.

    In any case it has helped me sort things out because I was only keeping the NG shortcode in there for later options – I use Justified Image Grid and Lightbox Evolution to display my thumbs and galleries; NG is only present in the background.

    So I removed the NG shortcode altogether and error is gone.

    Yes, well in my case (see above), I have just verified that NextGen has introduced a new shortcode function “slideshow,” which is not documented on their shortcode page and interferes with my Striking theme shortcode of the same name. What I’ve done as a temporary workaround is I’ve changed the Striking shortcode function name; but NextGen, please please do a comprehensive documentation of your shortcode!!

    Jim P.

    Yes, well in my case (see above), I have just verified that NextGen has introduced a new shortcode function “slideshow,” which is not documented on their shortcode page and interferes with my Striking theme shortcode of the same name. What I’ve done as a temporary workaround is I’ve changed the Striking shortcode function name; but NextGen, please please do a comprehensive documentation of your shortcode!!

    Jim P.

    See line 129, photocrati_nextgen/modules/nextgen_basic_gallery/module.nextgen_basic_gallery.php:

    C_NextGen_Shortcode_Manager::add('slideshow', array(&$this, 'render_slideshow'));

    This is what’s conflicting with Striking theme, and possibly other themes that reserve the term “slideshow” for their slider shortcode.

    Jim P.

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘[Resolved] array(1) { ["source"]=> array(1) { [0]=> string(24) "source should be present&q’ is closed to new replies.
Skip to toolbar