Website Gallery Plugin Repair or Replacement
Budget: $250 – $750 AUD
PLEASE READ the entire post before responding. Auto responses will be unlikely to be successful.
https://www.stampmall.com.au
This is a Long Post, and the question was asked to Chat GPT and their answer is also shown below.
I would like to know from the users here what path to follow. My gallery is large, over 200,000 image and 400 galleries, plus over 100 Tag categories.
I run a Word Press website Current Version 7.0 that uses NextGen gallery V4.2.1 and NextGen Pro V4.2.0, (now called Imagely). It does not work well now it has been upgraded to version 4.
The Front end Public View displays as expected, but all the faults are in the back end Administration side. Some faults, but not all; are unable to move images as Gallery dropdown does not show, Unable to sort images effectively in Admin Gallery view as only the first page of images is included in the sort selection. No image search feature in backend as there was previously. PLUS MANY OTHERS….
Their solution was to reinstall the Legacy version of Next Gen Gallery and work with that, however, now that is having issues displaying some galleries in the Admin back end. Their help has looked, (and was polite and as helpful as they could be) but essentially, say the features that worked previously in the V3… of Next Gen gallery are not included in the V4 upgrade. This essentially makes it a downgrade.
I am looking for solutions. Do I get a developer to work on it, given that the basic Next Gen Plugin V4. seems to be at fault ? Do I migrate to a new Gallery plugin, such as Foo Gallery, which I have tried and found to be to basic and does not support Tags ? It is important that I have Tags working and a very good search engine. I have tried Foo gallery and it is a good replacement with import for next gen, however it does not support tags which is really important, although it does have an import feature from Next Gen. I also tried Modula which also does not support Tags.
What are my options ???
HERE is what Chat GPT has to say
What you are describing is not really a “broken website” problem — it is a platform architecture problem caused by the move from legacy NextGEN Gallery / Imagely v3 to v4.
From your description, the important point is this:
your frontend still works
your backend workflow is broken
critical DAM-style features disappeared:
tagging workflow
image search
bulk organisation
proper sorting across pages
moving images between galleries
admin usability
That means the plugin is no longer functioning as a true image management system for your use case.
And based on what you described from Imagely support:
“those features are no longer included”
…this is unlikely to be fixed properly by waiting for updates.
So your real decision is:Option 1 — Stay on Imagely and hire a developer
OR Option 2 — Migrate away from Imagely entirely My recommendation
Given your requirements:
heavy image library
tags are essential
backend search is essential
likely thousands of images
long-term maintainability matters
I would NOT invest heavily in custom development on top of NextGEN v4.
Why?
Because your issue is not a bug.
It is a design direction change in the plugin.
A developer can patch symptoms:
dropdown fixes
pagination fixes
admin JS fixes
…but they cannot easily restore:
the old workflow model
the legacy admin architecture
missing search/tagging behaviour
removed UX features
You could easily spend thousands and still remain trapped in a plugin ecosystem that is moving away from your needs.The core issue: NextGEN became gallery-first instead of library-first
Older NextGEN behaved more like:
a Digital Asset Manager (DAM)
image database
searchable media catalog
Version 4 behaves more like:
a visual gallery builder
ecommerce/photo-sales platform
block-oriented frontend plugin
That is why power-user backend features regressed.The best long-term solution Move image organisation into WordPress itself
Instead of relying on a gallery plugin to manage:
tags
categories
metadata
searching
relationships
…you move all that into the native WordPress media system.
This is the important conceptual shift.
Then:
gallery plugins become “display layers”
not the master database
This avoids being trapped again later.The architecture I would seriously recommendMedia Library Assistant (MLA)
Media Library Assistant
This is probably the closest thing to the old “power user” NextGEN workflow.
It gives you:
image tags
categories
custom taxonomies
advanced search
filtering
bulk editing
EXIF/IPTC support
dynamic galleries
searchable media management
Most importantly:
it works with the native WordPress media library
This is huge.Then pair it with a frontend gallery plugin
You then choose a frontend renderer such as:Option A — Photonic
Photonic Gallery
Good for:
large image sets
filtering
albums
dynamic galleries
photographers
More technical but powerful.Option B — Justified Image Grid
Justified Image Grid
Extremely popular with photographers.
Excellent:
filtering
tagging
performance
visual layout
dynamic image loading
This combination:
MLA + Justified Image Grid
…is honestly one of the strongest replacements for old-school NextGEN workflows.Why FooGallery and Modula disappointed you
Because they are mostly:
presentation-focused gallery plugins
They are not:
image database systems
asset management systems
So:
tags are shallow
search is weak
organisation tools are limited
You already discovered this yourself.What I would NOT doDo not:
continue relying on Legacy mode long term
build more dependency on NextGEN shortcodes
custom-patch NextGEN heavily
spend months debugging Imagely admin issues
Legacy mode will eventually become:
incompatible
insecure
unstable
Especially with future WordPress releases.Practical migration path
This is the safest path I’d recommend:Phase 1 — Stabilise current site
Before touching anything:
full backup
database backup
image folder backup
staging site clone
Critical.Phase 2 — Export / preserve metadata
You must preserve:
tags
captions
alt text
descriptions
gallery relationships
This is the most important part.Phase 3 — Install MLA
Start organising images inside:
native WP Media Library
taxonomies
tags
Phase 4 — Install frontend gallery system
Likely:
Justified Image Grid
OR
Photonic
Phase 5 — Convert galleries gradually
Do not attempt:
“big bang migration”
Instead:
migrate gallery-by-gallery
test SEO
preserve URLs where possible
Should you hire a developer?
Yes — but for migration architecture, not for fixing NextGEN.
You want someone experienced in:
WordPress media systems
database migration
custom taxonomies
gallery migrations
shortcode conversion
NOT simply:
“WordPress plugin troubleshooting”
Very different skill set.The most important thing
Your real asset is NOT the gallery plugin.
It is:
your image library
metadata
tags
organisation structure
The goal is to free that data from a proprietary plugin ecosystem.
That is the strategic solution here.
https://www.stampmall.com.au
This is a Long Post, and the question was asked to Chat GPT and their answer is also shown below.
I would like to know from the users here what path to follow. My gallery is large, over 200,000 image and 400 galleries, plus over 100 Tag categories.
I run a Word Press website Current Version 7.0 that uses NextGen gallery V4.2.1 and NextGen Pro V4.2.0, (now called Imagely). It does not work well now it has been upgraded to version 4.
The Front end Public View displays as expected, but all the faults are in the back end Administration side. Some faults, but not all; are unable to move images as Gallery dropdown does not show, Unable to sort images effectively in Admin Gallery view as only the first page of images is included in the sort selection. No image search feature in backend as there was previously. PLUS MANY OTHERS….
Their solution was to reinstall the Legacy version of Next Gen Gallery and work with that, however, now that is having issues displaying some galleries in the Admin back end. Their help has looked, (and was polite and as helpful as they could be) but essentially, say the features that worked previously in the V3… of Next Gen gallery are not included in the V4 upgrade. This essentially makes it a downgrade.
I am looking for solutions. Do I get a developer to work on it, given that the basic Next Gen Plugin V4. seems to be at fault ? Do I migrate to a new Gallery plugin, such as Foo Gallery, which I have tried and found to be to basic and does not support Tags ? It is important that I have Tags working and a very good search engine. I have tried Foo gallery and it is a good replacement with import for next gen, however it does not support tags which is really important, although it does have an import feature from Next Gen. I also tried Modula which also does not support Tags.
What are my options ???
HERE is what Chat GPT has to say
What you are describing is not really a “broken website” problem — it is a platform architecture problem caused by the move from legacy NextGEN Gallery / Imagely v3 to v4.
From your description, the important point is this:
your frontend still works
your backend workflow is broken
critical DAM-style features disappeared:
tagging workflow
image search
bulk organisation
proper sorting across pages
moving images between galleries
admin usability
That means the plugin is no longer functioning as a true image management system for your use case.
And based on what you described from Imagely support:
“those features are no longer included”
…this is unlikely to be fixed properly by waiting for updates.
So your real decision is:Option 1 — Stay on Imagely and hire a developer
OR Option 2 — Migrate away from Imagely entirely My recommendation
Given your requirements:
heavy image library
tags are essential
backend search is essential
likely thousands of images
long-term maintainability matters
I would NOT invest heavily in custom development on top of NextGEN v4.
Why?
Because your issue is not a bug.
It is a design direction change in the plugin.
A developer can patch symptoms:
dropdown fixes
pagination fixes
admin JS fixes
…but they cannot easily restore:
the old workflow model
the legacy admin architecture
missing search/tagging behaviour
removed UX features
You could easily spend thousands and still remain trapped in a plugin ecosystem that is moving away from your needs.The core issue: NextGEN became gallery-first instead of library-first
Older NextGEN behaved more like:
a Digital Asset Manager (DAM)
image database
searchable media catalog
Version 4 behaves more like:
a visual gallery builder
ecommerce/photo-sales platform
block-oriented frontend plugin
That is why power-user backend features regressed.The best long-term solution Move image organisation into WordPress itself
Instead of relying on a gallery plugin to manage:
tags
categories
metadata
searching
relationships
…you move all that into the native WordPress media system.
This is the important conceptual shift.
Then:
gallery plugins become “display layers”
not the master database
This avoids being trapped again later.The architecture I would seriously recommendMedia Library Assistant (MLA)
Media Library Assistant
This is probably the closest thing to the old “power user” NextGEN workflow.
It gives you:
image tags
categories
custom taxonomies
advanced search
filtering
bulk editing
EXIF/IPTC support
dynamic galleries
searchable media management
Most importantly:
it works with the native WordPress media library
This is huge.Then pair it with a frontend gallery plugin
You then choose a frontend renderer such as:Option A — Photonic
Photonic Gallery
Good for:
large image sets
filtering
albums
dynamic galleries
photographers
More technical but powerful.Option B — Justified Image Grid
Justified Image Grid
Extremely popular with photographers.
Excellent:
filtering
tagging
performance
visual layout
dynamic image loading
This combination:
MLA + Justified Image Grid
…is honestly one of the strongest replacements for old-school NextGEN workflows.Why FooGallery and Modula disappointed you
Because they are mostly:
presentation-focused gallery plugins
They are not:
image database systems
asset management systems
So:
tags are shallow
search is weak
organisation tools are limited
You already discovered this yourself.What I would NOT doDo not:
continue relying on Legacy mode long term
build more dependency on NextGEN shortcodes
custom-patch NextGEN heavily
spend months debugging Imagely admin issues
Legacy mode will eventually become:
incompatible
insecure
unstable
Especially with future WordPress releases.Practical migration path
This is the safest path I’d recommend:Phase 1 — Stabilise current site
Before touching anything:
full backup
database backup
image folder backup
staging site clone
Critical.Phase 2 — Export / preserve metadata
You must preserve:
tags
captions
alt text
descriptions
gallery relationships
This is the most important part.Phase 3 — Install MLA
Start organising images inside:
native WP Media Library
taxonomies
tags
Phase 4 — Install frontend gallery system
Likely:
Justified Image Grid
OR
Photonic
Phase 5 — Convert galleries gradually
Do not attempt:
“big bang migration”
Instead:
migrate gallery-by-gallery
test SEO
preserve URLs where possible
Should you hire a developer?
Yes — but for migration architecture, not for fixing NextGEN.
You want someone experienced in:
WordPress media systems
database migration
custom taxonomies
gallery migrations
shortcode conversion
NOT simply:
“WordPress plugin troubleshooting”
Very different skill set.The most important thing
Your real asset is NOT the gallery plugin.
It is:
your image library
metadata
tags
organisation structure
The goal is to free that data from a proprietary plugin ecosystem.
That is the strategic solution here.