osamaaf

I got it fixed, Alhamdulillah (by the grace of God). All the following tables were needed to be fixed:

• wp_ngg_album
• wp_ngg_gallery
• wp_ngg_pictures

Procedure: Login to phpMyAdmin then open 1 of the above mentioned table and go to the “Structure” tab. Now open the first row “id” by clicking on the Change or Edit button on the same row. Now put the check on the checkbox under the column “A_I” (Auto_Increment). Click on the Save button. Thats it.

Still, I will complain about the developer for not responding on time. I wonder what this plugin’s worth will be why would I go pro for a plugin where the developer is sleeping and still has not replied after about 4 days.

• This reply was modified 10 months, 1 week ago by osamaaf.

WordPress database error Column 'gid' cannot be null for query INSERT INTO wp_ngg_gallery (author, extras_post_id, galdesc, gid, name, pageid, path, previewpic, slug, title) VALUES ('1', '6966', NULL, NULL, 'hello', '0', '/wp-content/gallery/hello/', '0', 'hello', 'hello') made by do_action('nextgen-gallery_page_nggallery-manage-gallery'), WP_Hook->do_action, WP_Hook->apply_filters, nggAdminPanel->show_menu, nggManageGallery->__construct, nggManageGallery->post_processor_galleries, Imagely\NGG\DataMapper\Model->save, Imagely\NGG\DataMapper\DriverBase->save, Imagely\NGG\DataMappers\Gallery->save_entity, Imagely\NGG\DataMapper\TableDriver->save_entity, Imagely\NGG\DataMapper\TableDriver->_create

This is the error when adding a new gallery

load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-polyfill-inert,regenerator-runtime,wp-polyfill,wp-hooks&ver=6.4.2:5 JQMIGRATE: Migrate is installed, version 3.4.1

/index.php?photocrati_ajax=1&action=upload_image&gallery_id=null&gallery_name=NewNew&nonce=88e614194d:1 
Failed to load resource: the server responded with a status of 500 ()

uppy.min.js?ver=1.27.0:1 [Uppy] [16:48:25] Failed to upload WhatsApp Image 2024-01-18 at 21.32.50_f2e57e76.jpg Upload error
error @ uppy.min.js?ver=1.27.0:1

These are the erros I see in the developer options console

Just updated from version 1.16.25 to version 1.16.26 and the issue is fixed. Thanks for ur response.

Just add an exclamation mark (!) in the beginning as follows:

!is_user_logged_in()