Title: Nextgen slideshow error
Last modified: February 2, 2018

---

# Nextgen slideshow error

 *  Resolved [Gemini23](https://wordpress.org/support/users/gemini23/)
 * (@gemini23)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/nextgen-slideshow-error/)
 * Just installed and the first thing I have noticed is that it ‘breaks’ the Nextgen
   slideshow and places the images one under each other… how can I get around that?
 * I suspect a JS issue but not sure which to amend or switch off.

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Thread Starter [Gemini23](https://wordpress.org/support/users/gemini23/)
 * (@gemini23)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/nextgen-slideshow-error/#post-9932555)
 * ps – I have tried this one “keep the order” of css files” but it doesn’t fix 
   the problem.
 * Neil
 *  Plugin Author [Raul P.](https://wordpress.org/support/users/alignak/)
 * (@alignak)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/nextgen-slideshow-error/#post-9933430)
 * Hi there,
 * It could either be a css or js compatibility when merging, or minifying.
 * a) Disable js processing and try again. If it fixes it, you know it’s a js related
   problem.
 * b) Do the same for the css (only) if the above doesn’t fix it.
 * c) Once you know which section (css or js) broke the slider, try do enable js
   or css processing back, but disable minification (merge only). On the status 
   page, you must purge the cache, then try again.
 * d) If this didn’t fix, then there is probably a problem merging your files (some
   incompatibility). The solution is to use the ignore list.
 * You can extract a list of files that have been merged from the status page and
   add them to the ignore list. Then remove one by one and refresh, to see if it
   works. When it works, the file you removed is the one you need to put in the 
   ignore list (others you can remove).
 * In the end, you will end up with one or two files on the ignore list.
    Once you
   know, please let me know so I can look at it in the future and think of a way.
 * Please read the faqs for more information:
    [https://wordpress.org/plugins/fast-velocity-minify/faq/](https://wordpress.org/plugins/fast-velocity-minify/faq/)
 *  Thread Starter [Gemini23](https://wordpress.org/support/users/gemini23/)
 * (@gemini23)
 * [8 years, 3 months ago](https://wordpress.org/support/topic/nextgen-slideshow-error/#post-9979759)
 * The only way I can get the Nextgen gallery to work is to tick these
    1) Inline
   all header CSS files [ If selected, the header CSS will be inlined to avoid the“
   render blocking” on pagespeed insights tests 2) Inline all footer CSS files [
   If selected, the footer CSS will be inlined to avoid the “render blocking” on
   pagespeed insights tests 3) Disable JavaScript processing [ If selected, this
   plugin will ignore JS files completely
 * I can’t seem to get any difference made by adding the js files to the ignore 
   list
 * [https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery-pro/modules/galleria/static/galleria-1.5.5.min.js](https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery-pro/modules/galleria/static/galleria-1.5.5.min.js)
   
   [https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery-pro/modules/galleria/static/ngg_galleria.min.js](https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery-pro/modules/galleria/static/ngg_galleria.min.js)
   [https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery-pro/modules/nextgen_pro_slideshow/static/theme/galleria.nextgen_pro_slideshow.min.js](https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery-pro/modules/nextgen_pro_slideshow/static/theme/galleria.nextgen_pro_slideshow.min.js)
   [https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery-pro/modules/picturefill/static/picturefill.min.js](https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery-pro/modules/picturefill/static/picturefill.min.js)
   [https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ajax/static/ajax.min.js](https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ajax/static/ajax.min.js)
   [https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_gallery_display/static/common.min.js](https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_gallery_display/static/common.min.js)
   [https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/lightbox/static/lightbox_context.min.js](https://www.staging1.londontheatre1.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/lightbox/static/lightbox_context.min.js)
 *  Plugin Author [Raul P.](https://wordpress.org/support/users/alignak/)
 * (@alignak)
 * [8 years, 3 months ago](https://wordpress.org/support/topic/nextgen-slideshow-error/#post-9979924)
 * [@gemini23](https://wordpress.org/support/users/gemini23/) after some quick testing,
   it turns out that nextgen gallery needs jquery to be render blocking, so you 
   may want to consider using it if you’re aiming at removing the render blocking
   message from pagespeed insights.
 * There are 2 ways to make the gallery work with fvm:
 * Option 1:
    Add these to the ignore list:
 *     ```
       /jquery.js
       /nextgen_basic_gallery/static/thumbnails/nextgen_basic_thumbnails.min.css
       /nextgen_basic_gallery/static/slideshow/nextgen_basic_slideshow.min.css
       ```
   
 * or, Option 2 (better):
    Add only the `/jquery.js` file to the ignore list, but
   make sure you select the “Inline all header CSS files” option.
 * —
 * What happens here is that if we merge jquery with other scripts, the gallery 
   cannot read it.
    Secondly, their css files cannot be merged into one, because
   those 2 CSS files on Option 1, are not using specificity ( [https://www.smashingmagazine.com/2007/07/css-specificity-things-you-should-know/](https://www.smashingmagazine.com/2007/07/css-specificity-things-you-should-know/))
   that allow them to overwrite others, when merged together. Without that, styles
   get broken simply by merging the css files.
 * It works when you inline, because the browser evaluates each css block individually.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Nextgen slideshow error’ is closed to new replies.

 * ![](https://ps.w.org/fast-velocity-minify/assets/icon-128x128.jpg?rev=1440946)
 * [Fast Velocity Minify](https://wordpress.org/plugins/fast-velocity-minify/)
 * [Support Threads](https://wordpress.org/support/plugin/fast-velocity-minify/)
 * [Active Topics](https://wordpress.org/support/plugin/fast-velocity-minify/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fast-velocity-minify/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fast-velocity-minify/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [Raul P.](https://wordpress.org/support/users/alignak/)
 * Last activity: [8 years, 3 months ago](https://wordpress.org/support/topic/nextgen-slideshow-error/#post-9979924)
 * Status: resolved