Support » Plugin: WordPress Gallery Plugin - NextGEN Gallery » blolck editor screws up posts with ngg gallery

  • this page is a good example of what the BS block editor does to ngg galleries in posts. And it is not fixable by switching to the classic editor as far as I can see. I would really like to use some !@$#%^ words about the block editor but I won’t here. Another fine example of what arrogance does to what used to be an easy to use CMS system.

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support mweichert

    (@mweichert)

    Hi there!

    It looks like a plugin is causing a conflict. NGG and a few of your other plugins rely on jQuery, which isn’t available on that page for some reason. The most likely reason though is a plugin conflict.

    I’d suggest try disabling all of your plugins other than NGG, and then reactivating one-by-one to determine which one is breaking things.

    Cheers,
    Mike

    1/3
    Actually I think this is a problem with the NGG settings. I have gone thru gallery settings and picked the legacy carosel. Then chose a basic slideshow for the galley on the page with a problem. I inserted that gallery into a test post and all I get is the images in the gallery instead of the carosel.

    Apparently with using the classic editor plugin you an only insert one gallery into a post. I inserted two and only the 1st one inserted shows in the preview. This I think is due to the block editor change because it was not a problem on the original classic editor before 5.0

    Plugin Support mihai-imagely

    (@mihaiimagely)

    Hi @flyfisher842

    I couldn’t replicate any of the specified issues using the latest version of WordPress and Classic Editor plugin so I still would lean on a plugin conflict.

    Have you had a any chance to test that?

    Mihai

    flyfisher842

    (@flyfisher842)

    https://www.fly-fishing-colorado.com/nggallery/slideshow?p=8105
    here is the code with ngg set to a slide show using the insert ngg gallery block from the block editor.

    <p>&nbsp;+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++</p>
    <p>&nbsp;</p>
    <p>&nbsp;</p>
    
    <!-- wp:imagely/nextgen-gallery -->
    [ngg src="galleries" ids="3" display="basic_slideshow"]
    <!-- /wp:imagely/nextgen-gallery -->

    using the same classic editor to insert an ngg gallery set to the basic slide show produces the same display a column of images instead of the nice nggs slideshow that used to be their before all this gutenberg crap.

    when clicking on an image I get the black display and the start of a slide show without any arrows to move forward or backward int he show.

    If there are two galleries on the same page, the last one is overlaid over the top of the top gallery on the page. Really great programming here.

    NGG is now so complicated to use that I need a degree in ngg just to put a gallery on my post.

    Easier I think to find a different working gallery plugin. The support page bears proof to the myriad of problems plaguing this plugin currently.

    flyfisher842

    (@flyfisher842)

    1/14/19
    After further testing, NGG does not play nice with autoptimize and speed booster pack and probably wp super cache too. Any plugin that moves scripts to the footer to optimize load speeds will likely mess up the basic slideshow display and default it to one column of gallery images.

    on two different sites I ran tests. On site one I disabled speed booster pack and on site two I disabled autoptimize beta to make the basic slide show work as an automatic fade slide between images. If I have to choose performance over using NGG, I will go to a different gallery plugin that does not have these problems with the script being at the bottom of the html to avoid the render blocking issue.

    Plugin Support gabyimagely

    (@gabyimagely)

    Hi @flyfisher842

    Reading the whole report, I noticed that there is no only one problem but more than one.

    First of all the issue, you are currently having with the block editor, and the classic editor could be linked with an existing report.
    While changing from the block editor to the classic editor, NextGen Gallery shortcode it’s being transformed into “block” and you can’t edit it back.

    We want to take a closer look at the problem. We may need to deactivate plugins and switch the theme while troubleshooting temporarily. Would you feel OK with that? If so, please send us a bug report here: http://www.imagely.com/report-bug, refer back to this forum thread and let them know Gaby referred you.

    About the other issue that you are describing with Autoptimize and Speed booster, we are not aware of any reports at the moment. Could you please check if you have the latest version of our plugin and see if the problem is solved?

    Many thanks

    – Gaby, Customer Support Imagely

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.