capecross

As I explained just above, I am using a shotcode within WP itself :
In a block [/] short code, I place a Nextgen shortcode of this type : [singlepic id=403 w=584 float=center template=no_exif].
But once again, I am using a template and I think this why it works.
Doing like this, you need to know the image number you want to put inside your post, no interactive way to choose the image as it was before Gutenberg and WordPress 5.

So it is still not solved !

The only way with wordpress 5 and Gutenberg I could find, is to use the “old” method.
I have different templates placed in a directory “nggallery” in the directory of my child theme.
Exemple with a template named : singlepic-no_exif.php
Then I use the shortcode : [singlepic id=403 w=584 float=center template=no_exif]
It works for me.

I am using this plugin since several years, when it was just Alex Rabe who developed it. I have done so many modifications inside this plugin for my own use, and to have it to my taste, that I cannot confirm using a template will work on a today version of this plugin.
I don’t care anymore to update the versions coming from Imagely since quite a while.

Maybe this help and you could give a try :
You can find an example of a singlepic template in the plugin itself :
nextgen-gallery/products/photocrati_nextgen/modules/ngglegacy/view/singlepic.php
And you can go in the settings : Gallery Parameters -> NextGen Basic SinglePic and choose your template.

“Since this issue is already part of our priorities and it’s in our developer’s hands, I am going to mark this thread as resolved to close it.”

8 months it was a priority…
Thread resolved they say !

Easy way to get rid of a problem which is still not solved.

Hi,

Thanks for the suggestion.
By default it was set to 7 days. (i dont remember having changed this value).
I set it to 14 days, and the error is gone.
I did not try to go back to 7 days.
May be the initial (default) value was not taken in account correctly ?

Regards

Hello,

Same error here too :

[30-Apr-2018 09:24:28 UTC] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘)’ at line 1 for query DELETE FROM wp_xxxxiqblock_logging WHERE datetime < DATE_SUB(NOW(), INTERVAL DAY); made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/iq-block-country/iq-block-country.php’), iqblockcountry_clean_db

WordPress 4.9.5
MySQL Database Version: 5.5.59-0+deb7u1-log
MySQL Client Version: 5.5.59
PHP Version: 7.2.3

Thanks for taking care.
Regards.

Thanks for your reply.

Finaly I took the risk and upgrade to WP 4.9.4, using PHP 7.2.3 with NextGen 2.2.54, and I don’t have a similar problem.
I succeeded in creating galleries and loading images.
I have no explanation why in using MAMP and localhost I have the problem.
Nothing regarding this in a debug log file.

Going back to PHP 5.6 fixes the problem for me.
You may see it on one fo my site : here

I am still using the 2.1.62 NextGen (I kept this version, as I have done few hacks inside few files) and automatic upgrading break this.
This, just to tell that I have the same problem as others with the new build of PHP 7.0.26. So I am not sure that an older version of NextGen is going to help.
Tries with PHP 7.1 and 7.2 did not help either so I went back in using PHP 5.6 for the moment.

@photocrati – Cais

Thanks for your answer, but there is something I don’t understand.

@photocrati – Cais

Thanks for your answer, but there is something I don’t understand.

You said : “The dynamic folder is not a cache item.”

When I manually clear the image cache via :
Gallery -> Other options -> Miscellaneous -> Clear image cache,
then the images in the “Dynamic” folders are erased.

Another way to clear the content of these dynamic folders content is to make a call (in functions.php of my theme ??
$cache = C_Cache::get_instance();
$cache->flush_galleries();
I did that to try and it works.

But when I just view a post (without having modified anything) then the Dynamic folder refill with new calculated images…
date_image_name.jpg.nggidXXXXX-ngg0dyn-……..etc…..
with all the prefix set in your : package.module.dynamic_thumbnails.php
Nothing to do with “after they have been uploaded”

If I look to source code of the generated page, it’s these images which are loaded.
If images have a smaller size (width & height) in the post then these “dynamic” resized images loose a small amount of weight, but WORSE, if images keep the same size then the weight increase. And all of these files loose all the meta data written in the original file itself.

Example : here

Why resize an image with the same width ?
For instance why resize an image asked for a width 588 in the post, using the parameter w=588 in the singlepic shortcode if the original image in the gallery folder has exactly this width ? The same thing happens if no width is indicated in the shortcode.

Is it something due to NextGen or WordPress default way ?
Is there a way to avoid what seems useless resize ?

Thanks for answers.

https://www.ads-software.com/plugins/nextgen-gallery/

Hello,

@scttcrry I would recommand you read this : here

Even if rather old, It’s still helped me (with recent version of nextgen 2.0.66.29) to move recently from a localhost to final server.

You should search topics around the shortcode [tagcloud].

“Can you please mail me a photo?”

Email sent !

Several tries later, I am not quite sure that’s my problem come from the way GPS datas are arranged, or has something to do with the lack of GPS Date Stamp and GPS Date/Time…

Hi Frederic,

Until now I had no better results.
Either V.0.52 or V0.61.
I think I have an explanation, see below…

As in the settings, I could see the example map, but no result in post, and as I am sure all this is working for you, I thought it could be a configuration problem.

Then I had the idea to make a try with your example images, even if I was sure that my images had GPS datas.
So I imported your example images in a Gallery, and post, and then the map and the vignettes showed nicely.
So this surely meaned that there were differences in the exif datas.
Using Phil Harvey’s exiftools I compare :

Here is one of your image exifs datas as it is shown by exiftools :

Resolution Unit : None
Y Cb Cr Positioning : Centered
GPS Version ID : 2.2.0.0
GPS Time Stamp : 20:36:14
GPS Satellites : 0
GPS Map Datum : WGS-84
GPS Date Stamp : 2012:05:11
XMP Toolkit : Image::ExifTool 8.26
……some more datas…..
Color Components : 3
Y Cb Cr Sub Sampling : YCbCr4:2:0 (2 2)
GPS Date/Time : 2012:05:11 20:36:14Z
GPS Latitude : 44 deg 29′ 34.40″ N
GPS Latitude Ref : North
GPS Longitude : 63 deg 54′ 59.40″ W
GPS Longitude Ref : West
GPS Position : 44 deg 29′ 34.40″ N, 63 deg 54′ 59.40″ W

Here is one my images (made with a Canon camera) exits datas as it is shown by exiftools :

Exposure Mode : Manual
White Balance : Manual
Scene Capture Type : Standard
Lens Model : EF24-105mm f/4L IS USM
GPS Version ID : 2.2.0.0
GPS Latitude Ref : North
GPS Longitude Ref : West
GPS Map Datum : WGS-84
Compression : JPEG (old-style)
……some more datas…..
Aperture : 8.0
Date/Time Created : 2011:06:17 19:59:35+02:00
Digital Creation Date/Time : 2011:06:17 19:59:35+02:00
GPS Latitude : 65 deg 48′ 28.87″ N
GPS Longitude : 16 deg 23′ 13.78″ W
GPS Position : 65 deg 48′ 28.87″ N, 16 deg 23′ 13.78″ W
Image Size : 940×627
Scale Factor To 35 mm Equivalent: 5.8
Shutter Speed : 0.4

I usually use PhotoLinker to reverse geotag my images, before importing them to Lightroom, then exporting them for the web with all the metadatas.
Now that Lightroom 4 handles GPS datas, I might skip PhotoLinker.
But anyway there is a difference between the way GPS exifs are coded within your images and mines.
Especially the lack of GPS Date Stamp and GPS Date/Time in my image and the order.

I made a try with an image made with another camera (Panasonic), and your map shows OK. The GPS datas came from a gpx file used with PhotoLinker to tag the images.
The exif tools shows :

Lens Model : LUMIX G VARIO 14-140/F4.0-5.8
GPS Version ID : 2.2.0.0
GPS Latitude Ref : North
GPS Longitude Ref : West
GPS Altitude Ref : Above Sea Level
GPS Time Stamp : 16:42:01
GPS Map Datum : WGS-84
GPS Date Stamp : 2011:06:16
Compression : JPEG (old-style)
……some more datas…..
Aperture : 5.0
Date/Time Created : 2011:06:16 16:42:28+02:00
Digital Creation Date/Time : 2011:06:16 16:42:28+02:00
GPS Altitude : 17.9 m Above Sea Level
GPS Date/Time : 2011:06:16 16:42:01Z
GPS Latitude : 65 deg 31′ 32.22″ N
GPS Longitude : 13 deg 48′ 20.04″ W
GPS Position : 65 deg 31′ 32.22″ N, 13 deg 48′ 20.04″ W
Image Size : 940×587

So I do think my problem was coming from this.
Datas are not arranged in the same way or order.
I should have a look in the data base to try to understand, or modify your test :
line 28 in functions.php :
if (!isset ($exif[‘GPSLongitude’][0])) {return false;}
which maybe is toot strict.

If you have ideas from your side…they will be welcome.

Sorry to have been so long, but I am almost sure, I won’t be the only one to face this.
Hard time with these exifs which are not completely normalized…

@Frest.de

Thanks for you efforts and coming updates.

Just start a new project with V.0.52.
Sorry to tell I have the same issues within a post.
I don’t get any error messages at the settings page, I expect its because there is no preview map in this version.

Here is what I get with the post :

Notice: Undefined variable: map_output in /…/wp-content/plugins/nextgen-gallery-geo/plugin.php on line 25

Then for each image included in the gallery it repeats :

Notice: Use of undefined constant latitude – assumed ‘latitude’ in /…/wp-content/plugins/nextgen-gallery-geo/functions.php on line 65

Notice: Use of undefined constant longitude – assumed ‘longitude’ in /…/wp-content/plugins/nextgen-gallery-geo/functions.php on line 65

Notice: Undefined variable: pin_desc in /…/wp-content/plugins/nextgen-gallery-geo/functions.php on line 78

Notice: Use of undefined constant longitude_format – assumed ‘longitude_format’ in /…/wp-content/plugins/nextgen-gallery-geo/functions.php on line 86

Notice: Use of undefined constant longitude_format – assumed ‘longitude_format’ in /…/wp-content/plugins/nextgen-gallery-geo/functions.php on line 86

Notice: Use of undefined constant latitude_format – assumed ‘latitude_format’ in /…/wp-content/plugins/nextgen-gallery-geo/functions.php on line 86

I hope this will help you to track…

Hi,

@aviceda,
I found the trunk version here and installed.

I got there following this

BUT !
@frest.de,

I still get errors, when going in the settings of the plugin (preview map) :
Trying to get property of non-object in /…/wp-includes/post-template.php on line 30
This addresses to a file which is the wordpress core !
And then a full list or errors…regarding the plugin files.
And after the error list, then the example map shows !!!

In a post including [nggg], I get a full pages of errors
Notice: Undefined variable: map_output in /../wp-content/plugins/nextgen-gallery-geo/plugin.php on line 25
Notice: Undefined property: nggImage::$worldmap in /…/wp-content/plugins/nextgen-gallery-geo/functions.php on line 65
Notice: Use of undefined constant latitude – assumed ‘latitude’ in /…/wp-content/plugins/nextgen-gallery-geo/functions.php on line 67
Notice: Use of undefined constant longitude – assumed ‘longitude’ in /…/wp-content/plugins/nextgen-gallery-geo/functions.php on line 67
Notice: Undefined variable: pin_desc in /…/wp-content/plugins/nextgen-gallery-geo/functions.php on line 80
Notice: Use of undefined constant longitude_format – assumed ‘longitude_format’ in /…/wp-content/plugins/nextgen-gallery-geo/functions.php on line 88
Notice: Use of undefined constant longitude_format – assumed ‘longitude_format’ in /…/wp-content/plugins/nextgen-gallery-geo/functions.php on line 88

…etc…

I am not a PHP code specialist, but maybe there is certainly a simple syntax mistake in a file which generates theses problems.

I have detected something : at the end of the file functions.php, there is no end: ” ?> “. I tried to add one, but that does not solve the problem…

Any ideas ?