Plugin Contributor
Imagely
(@imagely)
Hi @staze,
I hope that you wouldn’t mind trying to manually reinstall NextGen by deactivating/removing it then install it anew from ww.wp.xz.cn repository.
Hope this helps,
Mihai
-
This reply was modified 7 years, 6 months ago by
Imagely.
Plugin Contributor
Imagely
(@imagely)
Hi @staze!
You might have already tried this, but I would like to know if is an existing conflict or cache problem.
Cache.
– Please clear or purge any cache you have installed, does the problem persist?
Conflict
1.- Temporarily deactivate all your plugins except NextGen Gallery.
2.- Is the problem solved? Then, it was caused by one of your plugins. Please check one by one and find the one causing the problem.
3.- If the problem is not solved with the deactivation of the plugins, try changing to a standard WordPress theme, it could be a conflict with your current theme.
Please, keep us posted.
We are happy to help.
– Gaby
Thread Starter
staze
(@staze)
As in other ticket, spun up entirely new site. Added two slideshows via widgets. Got the same “404” for the wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_basic_gallery/static/slideshow/nextgen_basic_slideshow.min.css
Looking in that directory, that file doesn’t exist. But ngg_basic_slideshow.min.css does.
Symlink fixes, but some code is referencing the wrong thing. Or that file just needs renamed (or lazily duplicated)
I’m having the same issue with nextgen_basic_gallery/static/slideshow/nextgen_basic_slideshow.min.css being 404 for the slideshow on this page. Error in chrome dev console.
https://www.alaskahelimush.com/your-glacier-flight-to-dog-world/
Hi
I am also receiving this error
Failed to load resource: the server responded with a status of 404 ()
404 not found for nextgen_basic_slideshow. ver 3.1.4
Site is https://www.blackbear.website/
Ann
(@akg-free)
EDIT: We thought we’ve solved it, sadly… nope.
We have the same issue. All caches cleared.
Maybe helpful?
The file was called “nextgen_basic_slideshow.min.css” up to version 2.2.54 – a long time ago. 😉
-
This reply was modified 7 years, 5 months ago by
Ann.
-
This reply was modified 7 years, 5 months ago by Ann.
Thread Starter
staze
(@staze)
Just updated to 3.1.5, issue still occurs.
Hi @staze
We want to help you troubleshoot this issue you see with “nextgen_basic_slideshow.min.css” file. Unfortunately, ww.wp.xz.cn doesn’t allow us to address pro support questions here in the free forum.
We can only address NextGEN Gallery [Free] questions only.
Please submit a support request through your member account here: http://www.imagely.com/account.
Because we need separated ticket numbers for each problem, you need to create a new one for this bug report. Many thanks!
– Gaby, Customer Support Imagely
Thread Starter
staze
(@staze)
This is NGG free that I’m needing support on. As I mentioned in my ticket with pro support, I only emailed to kick this back into the light. The issue still exists. with the free NGG.
Hi @gabyimagely
Apologies, we need to take a more in-depth look at this particular issue.
Would that be ok? It’s not just because you are Pro user; we need to set some time apart, ask our developers and find why is happening.
We may need to deactivate plugins and switch the theme while troubleshooting temporarily. Would you feel OK with that? If so, please send us a bug report here: http://www.imagely.com/report-bug, refer back to this forum thread and let them know Gaby referred you.
– Gaby, Customer Support.
Hi everyone,
Thanks for the report and for the associated comments. I have checked our records and it looks like it has been already reported before and I have personally submitted it for our developers’ review.
It looks like the Slideshow tries to load a renamed resource that doesn’t exists. We are looking forward to see it fixed in one of the next plugin’s updates.
Sorry for the inconveniences,
Mihai
Thread Starter
staze
(@staze)
Hi @mihaiimagely,
Still seeing this issue with 3.2.2. Could you give us all a bit of an update on where this falls on the priority list? Seems like it should be an easy fix…
Hi @staze,
We are sorry for the delays. This issue is still unreleased even though it might be already fixed by the developers as a separate branch but just not included in the release yet. I hope to see it released in the next update.
