Benjamin

That looks like there hasn’t been a request made to the server yet, try looking after clicking the “Upload X buttons” and the image fails?

We’ve found a separate (possibly) bug where it’s possible to click the upload button before a gallery has been selected; can you confirm that you have created or selected a gallery before attempting to upload new images?

If you are comfortable with some basic code editing I’ve committed a pretty simple change that fixes our uploader using a generic error message and makes it report what the server responds with. You can find that change on this github.com commit to get more detailed error reporting.

I’m not thinking of much that could help. Is this in the classic editor, the “gutenberg” / block editor, a custom post type, or in a page layout manager plugin?

Thanks tchekouze!

I haven’t experienced this problem myself while using WordPress pulled from git, but WP 5.7 isn’t quite yet to the alpha stage and they are making several changes to JS/jQuery with 5.6 and 5.7.

Do you still experience this with the latest WordPress nightly / pull?

Hi esmaeili!

Could you try the following (assuming you use Chrome) when trying to upload:
– Right click anywhere on the page and select “Inspect”
– Select the “Network” tab, then the “XHR” sub-tab below it
– Click the “Upload X files” button
– Click one of those new requests and then click on its “Response” tab

And then provide the results here? I expect there’s an error on the server side that isn’t being reported by our new uploader, if I can just find out what the server is replying with I can fix the problem.

Thanks!

That can be removed with:

add_filter('show_nextgen_version', function() { return ''; });

Hi rhondadrew! Sorry for the delayed response.

To accomplish that you would need to create your own album template. You can see our documentation on that here

Currently I feel a bit reluctant to clear the ngg cache for fear of having down-time again, but if it can help improve ngg we can talk about this.

I’ve thought about this some more, I should add: NextGEN’s image cache is just the “dynamic” images — say if you override the default thumbnail size for a Basic Thumbnail display then we create a second set of thumbnail images and store them in the cache.

NextGEN Pro’s Tile, Masonry, and Mosaic displays however don’t use the ‘full’ sized image and generate specially sized versions in order for those images to fit into their display and to conserve some bandwidth. If the generated / resized file does not exist the browser is given a special URL to the image (it starts with /nextgen-image/) that triggers the server to do the resize and serve the results to the browser. This can make the first time loading one of those displays pretty slow.

The feature to wipe NextGEN’s image cache is partially for people to reclaim disk space if necessary and partially because of a handful of bugs through NextGEN’s history; for most people it actually shouldn’t be used unless necessary. I’ve made a note to add a warning / confirmation to the “Clear image cache” button, that’s definitely on us for not having done so before and not explaining what it does before launching.

If you’re having to break up a single large gallery into multiple galleries.. this isn’t the friendliest answer but you could upload / create your large gallery and insert it into a private page and preview it — once the server has had the time to generate all of the new resized versions it will then have static copies that are much faster to serve and the page can be made public.

I hope that helps a little!