Imagely
Forum Replies Created
-
Hi @catheg,
In one of the recent NextGen Gallery updates we’ve moved FontAwesome from web loading to locally loading ( to ensure the plugin complies with GDPR European standard ).
Since then, NextGen includes different versions of FA icons such as woff, tiff and svg and the optimization plugins tend to prefer loading FA as svg when the concatenation is enabled ( for the performance reasons ) and the theme or the other plugin may not work with FA icons as SVG but there’s not much that can be done from our side of things to prevent this behavior unless perhaps finding the necessary scripts and exclude then from the concatenation but we aren’t sure that’ll work.
Hi @catheg,
Seems that FontAwesome icons are loading as SVG.
Please try disabling CSS/JS concatenation and minify to see if that’ll change anything. If that doesn’t help, you can try deactivating FA from “NextGen Gallery -> Other Options -> Miscellaneous -> Do not enqueue FontAwesome: Yes”
Hi @sarahsas,
It’s a bit complicated to guess what is happening here but perhaps double check to see if the caching service/plugin you use has a specific setting that ‘d allow clearing the homepage cache.
Also, we wonder if you’d get the entire list of images displayed if adding /?1 at the end of your URL for example https://declutter123.com/#before-after/?1 that’d basically force any page load new its resources.
- This reply was modified 3 years, 3 months ago by Imagely.
Hi @hellsbrigade,
You have the images open in 2 lightboxes simultaneously. One of them is NextGen’s and another one that stays as a background is Magnific Popup lightbox that loads from OceanWP theme. Please check with your theme support to see if they offer a possibility to deactivate the theme’s lightbox.
Hi @jimk1416,
Could you please double check to make sure you use Post Name permalink setting in Dashboards -> Settings -> Permalinks?
This is an old version we’ve released in = V3.2.10 – 07.23.2019 =
Updating NextGen Gallery plugin is safe and necessary. Your already existing galleries will remain unchanged.
Hi @macsurf,
NextGen will automatically add this incremented number to the gallery folder’s name/slug in case that there’s already a gallery folder using the same name. You can check by FTP to see if you are using unique enough gallery names so it wouldn’t increment their slugs when you create new galleries.
We need to note that changing the gallery’s path will not change the already existing gallery folder but will simply create an empty gallery folder with a duplicate name thus that’s why it comes incremented. You’d need to manually transfer ( by FTP ) the image files from the old gallery folder to the new one.
Hi @summdom,
My bad, please disregard the initial message. This is Envira forum indeed.
Checking with Brad from Envira support team, it seems that they have registered an issue ticket for the dev team but issues like this one may take longer to be solved, tested then released as a part of a future plugin release.
Thanks for your understanding
- This reply was modified 3 years, 3 months ago by Imagely.
Hi @estherramos,
We don’t have any other similar reports either so that’s why we’d assume its something local happening due to either a server configuration or a conflict of some sort that we are not aware of. We suggest you enable define( ‘WP_DEBUG_LOG’, true ); to check if it’ll catch any errors and test for a plugin conflict by temporarily deactivating the site’s plugins excepting NextGen Gallery to see if that’ll change anything.
The module that’s adding the descriptions is nextgen-gallery\products\photocrati_nextgen\modules\nextgen_basic_album\templates\descriptions.php
Hi @danielhubes,
Could you please let us know what NGG version are you using for your site?
It may worth deleting NGG plugin’s folder by FTP and re-installing it to make sure that your installation isn’t corrupted and doesn’t use legacy code.Hi @estherramos,
I’m afraid we couldn’t replicate the issue on IOS 16.4.1 visiting the gallery page you’ve mentioned.
You may want to enable WP Debug and the logs to catch the errors in case that they aren’t consistently replicable. Perhaps that’s due to the server randomly running out of hardware resources ( RAM or CPU ). You may want to additionally consult the hosting provider to check the server loading logs.
WP Rocket also comes with “Images Lazy Loading” feature that’d conflict with NextGen’s AJAX pagination. Basically, you’ll need to ensure that you don’t have any plugin or service enabling lazy loading.