photocrati
Forum Replies Created
-
@opusuno – It appears we may be having the same discussion in a Bug Report, let’s carry on there if there is more to add as it appears this very old NextGEN Legacy shortcode structure is no longer working.
Thanks!
– Cais.
@vyskoczilova – Is this only happening with the WordPress 4.7.5-alpha version(s); or, are you also seeing this with WordPress 4.7.4 (the current stable release)?
Thanks!
– Cais.
@fritzbogott – You’re welcome!
– Cais.
@smej87 – Please contact our support team directly with any questions or concerns for NextGEN Pro displays via your member’s area at https://imagely.com/support/
Thanks!
– Cais.
@fritzbogott – Glad to help, although if this happens again look to caching and/or optimizing plugins/services active on your site; in some cases these may remove the source references and may require an adjustment to their settings.
Thanks!
– Cais.
@megamel – The following JavaScript snippet may be of use in disabling image click functionality:
// Disable <img> clickable $(document).ready(function(){ $('.post-body a img:not(.clickEnabled)').click(function(e) { if (e.which === 1) { e.preventDefault(); } }); });As to the small screen view issue I am not really seeing anything specific when viewing the URL you provided.
Thanks!
– Cais.
@ade11 – The plugin should be network activated for best results, which includes providing the additional options noted.
Thanks!
– Cais.
@vyskoczilova – Please contact our support team directly with any questions or concerns for NextGEN Pro (or NextGEN Gallery) via your member’s area at https://imagely.com/support/
Thanks!
– Cais.
@dharator – There are currently no methods in NextGEN Gallery et al. by Imagely to download an entire gallery/album/collection/etc.
Thanks!
– Cais.
- This reply was modified 9 years, 2 months ago by photocrati.
@slparker67 – You’re welcome!
– Cais.
@mditack – We’re not seeing this error ourselves in testing or production sites making it difficult to know where the issue is. 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? Although not too likely to be a conflict it is still good to rule out the possibility.
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.
@opusuno – The leading comma ( , ) may be causing some issues although if those tags exist then that shortcode should work as expected. We actually had to update our own page to use current tags as can be seen now.
Thanks!
– Cais.
@acadia – Thanks for sharing this here! We are looking at the implementation to see if it is easily implemented into our current codebase as a permanent addition.
– Cais.
@dberch – Are there any recent entries in the error_logs for the server that might help to point out the specific issue? Have you contacted the other author, and were they able to shed any light on this situation?
Thanks!
– Cais.
@integritive – No worries, we’re happy to see all is well on the site.
– Cais.