photocrati
Forum Replies Created
-
@mrvideogame – A lot would depend on the restoration done by your web host as the backup they were making may not have contained your complete site and/or database. If that is the case there is not much we can offer aside from suggesting you may need to start over with re-uploading images and re-inserting displays.
If the images are still on your site you may be able to create the gallery names again and then import from folder the images on the server although you may still need to recreate and re-isnert the displays you were using.
Thanks for the extra details.
– Cais.
@tony-morton – You may need to use the plugin a few times (this is rare but can be required) or there may be something creating a conflict on your site.
This may also have something to do with a “role manager” plugin being used on your site and the NextGEN Gallery Roles and Capabilities options being compromised by its usage (NextGEN Gallery can only use the default WordPress roles and will have unexpected results if those are modified and/or not used).
Have you tried deactivating all of your plugins, clearing your browser cache (and site caches if you are using a caching plugin), then reactivating the NextGEN plugin?
If this fixes the problem then it was likely one of the deactivated plugins that was causing an issue. Now, retrace your steps activating each plugin and re-checking to see if the problem returns. If it does then that last activated plugin was probably the one. Keep reactivating and in most cases it is also best to keep checking after each plugin, sometimes there may be more than one plugin on a site that will create an issue. If you do find one (or more) plugins causing this problem we would greatly appreciate your feedback on them so the developers may address them as soon as they can.
Also to note, in rare cases it may be the theme itself that is causing a conflict so while you have just the NextGEN plugin activated you might consider temporarily switching to one of the default WordPress Twenty series themes and see if this corrects the issue as well.
If the problem still persists after all of this we would still want to know, even more so, as we will still want to sort out the issue and may need additional details.
Thanks!
– Cais.
@andyt8 – Thanks for pointing our the “back” button reference, I did not notice that earlier. What appears to be happening is clicking on the image is triggering two events. The first event is the Fancybox (which appears to be working correctly) and the second event which is ignoring the Fancybox and just treating the image as is (which displays the image as the default HTML
<img>tag would).In most cases, this points to an option / setting / feature set of the theme (most common) or another active plugin that specifically deals with images. I would recommend focusing on those types of items to see if you can sort out which specifically is causing the second triggered event when clicking on an image.
Thanks!
– Cais.
@neilbert – Thanks for the update! Best of luck finding what is causing the problems on your site.
– Cais.
@mrvideogame – Do you recall what happened before you noticed your galleries and images where missing?
Thanks!
– Cais.
@omarperez999 – There are three hooks available to adjust the Manage Galleries list results, you would be looking at the following one to increase the number of galleries that appear on one page by default:
add_filter( 'ngg_manage_galleries_items_per_page', 'your-callback-function' );Thanks!
– Cais.
@thibay – Depending on the specifics of the conflict this may be resolved in the next release of NextGEN Gallery if it has to do with how WPML inserts a language URL segment.
We hope to have this release published soon.
Thanks!
– Cais.
@arthurandashes – The messages you are seeing are likely due to a security setting set by either a “security” plugin/service or from something within the server environment.
I would recommend looking at those possibilities and confirming the aggressiveness of the options you are using are set correctly for what you want to do with the website.
Thanks!
– Cais.
@lhtek – Great News! Having happy customers is very important!
– Cais.
@elrond532000 – Please contact our support team directly with any questions or concerns for NextGEN Pro displays or the NextGEN Pro Lightbox via your member’s area at https://imagely.com/support/
Thanks!
– Cais.
@thibay – Have you tried deactivating all of your plugins, clearing your browser cache (and site caches if you are using a caching plugin), then reactivating the NextGEN plugin?
If this fixes the problem then it was likely one of the deactivated plugins that was causing an issue. Now, retrace your steps activating each plugin and re-checking to see if the problem returns. If it does then that last activated plugin was probably the one. Keep reactivating and in most cases it is also best to keep checking after each plugin, sometimes there may be more than one plugin on a site that will create an issue. If you do find one (or more) plugins causing this problem we would greatly appreciate your feedback on them so the developers may address them as soon as they can.
Also to note, in rare cases it may be the theme itself that is causing a conflict so while you have just the NextGEN plugin activated you might consider temporarily switching to one of the default WordPress Twenty series themes and see if this corrects the issue as well.
If the problem still persists after all of this we would still want to know, even more so, as we will still want to sort out the issue and may need additional details.
Thanks!
– Cais.
@lulu29 – Have you tried deactivating all of your plugins, clearing your browser cache (and site caches if you are using a caching plugin), then reactivating the NextGEN plugin?
If this fixes the problem then it was likely one of the deactivated plugins that was causing an issue. Now, retrace your steps activating each plugin and re-checking to see if the problem returns. If it does then that last activated plugin was probably the one. Keep reactivating and in most cases it is also best to keep checking after each plugin, sometimes there may be more than one plugin on a site that will create an issue. If you do find one (or more) plugins causing this problem we would greatly appreciate your feedback on them so the developers may address them as soon as they can.
Also to note, in rare cases it may be the theme itself that is causing a conflict so while you have just the NextGEN plugin activated you might consider temporarily switching to one of the default WordPress Twenty series themes and see if this corrects the issue as well.
If the problem still persists after all of this we would still want to know, even more so, as we will still want to sort out the issue and may need additional details.
Thanks!
– Cais.
@andyt8 – As you are seeing this work elsewhere in a similar circumstance are you able to compare the two site more closely to see what differences there may be between the two?
I would suggest looking at the server environments as you are indicating you have checked your current active plugins and theme to see if the conflict is there.
Thanks!
– Cais.
@neilbert – Is there something unusual about the tag names you are trying to use? These should work just like a tag for a post and would have similar requirements.
Otherwise, although not too likely, it could be a conflict with another active plugin or your current theme. Have you tried deactivating all of your plugins, clearing your browser cache (and site caches if you are using a caching plugin), then reactivating the NextGEN plugin?
If this fixes the problem then it was likely one of the deactivated plugins that was causing an issue. Now, retrace your steps activating each plugin and re-checking to see if the problem returns. If it does then that last activated plugin was probably the one. Keep reactivating and in most cases it is also best to keep checking after each plugin, sometimes there may be more than one plugin on a site that will create an issue. If you do find one (or more) plugins causing this problem we would greatly appreciate your feedback on them so the developers may address them as soon as they can.
Also to note, in rare cases it may be the theme itself that is causing a conflict so while you have just the NextGEN plugin activated you might consider temporarily switching to one of the default WordPress Twenty series themes and see if this corrects the issue as well.
If the problem still persists after all of this we would still want to know, even more so, as we will still want to sort out the issue and may need additional details.
Thanks!
– Cais.
@paul33 – Unfortunately, due to the forum guidelines, support for plugins not hosted in the WordPress plugin directory is not allowed.
– Cais.