Benjamin

You won’t lose any settings or uploaded galleries, those are not stored in the plugin directory.

Did you download a new zip file of the plugin? It’s possible the zip file previously downloaded is what was corrupted.

Hi @dgraszka!

That sounds like there was an error during the update that corrupted that one file. Could you please delete your nextgen-gallery directory from wp-content/plugins/ and reinstall it? That should fix your issue.

Hi @shafimczayu

Adding the following to your /wp-config.php file should fix the issue:

define('NGG_DISABLE_SHUTDOWN_EXCEPTION_HANDLER', TRUE);

Hi @mohammadalib6233

I’m not certain what you mean about only NextGEN tags appearing; there’s some tags in the left column but those look like normal WordPress tags.

I am seeing several errors due to some static resources like jQuery UI being blocked from loading because they’re loaded over HTTP while the site is using HTTPS. Correcting that may fix several problems at once.

Hi @annawkbauer

That warning is coming from the Portfolio Gallery, Product Catalog – Grid KIT Portfolio plugin and should be reported to its authors.

This will be fixed with the next NextGEN release which I’m planning for the 23rd.

Galleries can be added to existing albums in the following way:

$album_id = 5; // your album ID here
$mapper = C_Album_Mapper::get_instance();
$album = $mapper->find($album_id);
$album->sortorder[] = '6';
$album->sortorder[] = '7';
$mapper->save($album);

That will add galleries 6 and 7 to the album. As before for sub-albums just prefix their ID with a lowercase ‘a’.

Thanks for your patience @wpressnl

I’ve written a quick set of examples here that covers how to create galleries, albums (with children), upload images, and how to update existing albums / galleries / images.

The internal API is a little complicated but comprehensive; let me know if you have any other questions.

Hi @wpressnl !

Please do not directly manipulate the NextGEN tables; that will cause problems and break certain aspects of NextGEN. There is an internal API you can use in the classes C_Image_Mapper, C_Gallery_Mapper, C_Album_Mapper, and C_Gallery_Storage

I’ll write some examples / documentation on how to use those classes on Monday and post them here.

Hi @sottovoce

It appears that we missed the widgets CSS when that constant was introduced; I’ll try to have that fixed in one of our upcoming releases.

Until then you can force their removal with the following PHP; I like to create a small plugin for basic site customization tweaks and store things like this in that plugin:

add_action('wp_enqueue_scripts', function() {
    wp_dequeue_style('nextgen_widgets_style');
    wp_dequeue_style('nextgen_basic_thumbnails_style');
    wp_dequeue_style('nextgen_basic_slideshow_style');
});

Sorry for the inconvenience!

Hi @odak71

The constant should be all you need to need to stop NextGEN adding scripts or styles to the frontend. If anything is being enqueued anyway please let me know.

Thanks!

Thanks @nosilver4u

I’ll have that fixed in the next NGG release; in the meanwhile just commenting out the code inside of the _track_key() method should allow your site to continue working until then.

That’s unusual; can you show me what debug_backtrace() added after line 137 results in; and what $key and $value are?

The next NGG release will include a check for the previously mentioned constant in the _track_key() method which will fix the problem, but if possible I’d like to resolve the root issue too.

Thanks!

Hi @jimk1416

You have nothing to worry about then; the old template system will be removed but the new ‘views’ includes a template that looks just like the old default style, it isn’t going to be removed.

I’m glad to help ?? With a site that old good luck on your other future updates!