mweichert
Forum Replies Created
-
@thedevonartist we don’t have any records of that particular issue.
Please, if you have some time, we′d like to take a closer look. Would you mind sending us a bug report here: https://www.imagely.com/report-bug, refer back to this forum thread and let them know Mike referred you.
Many Thanks.
Mike
Thanks!
@sccjono I’ve fixed this and it will be included in our next release
@francoc30 This was fixed and released with NGG Pro 3.1.2 and NGG Plus 1.7.0.
Has everyone here having this issue dequeued jquery migrate?
@aj, are you still seeing images missing from https://www.heymanhustle.com/rr/?
Hi there!
It looks like a plugin is causing a conflict. NGG and a few of your other plugins rely on jQuery, which isn’t available on that page for some reason. The most likely reason though is a plugin conflict.
I’d suggest try disabling all of your plugins other than NGG, and then reactivating one-by-one to determine which one is breaking things.
Cheers,
MikeI’d suggest using the C_Displayed_Gallery_Renderer class.
$renderer = C_Displayed_Gallery_Renderer::get_instance(); echo $renderer->display_images(array( 'src' => 'galleries', 'ids' => array('3'), 'display' => 'basic_thumbnail' ));
- This reply was modified 6 years, 3 months ago by mweichert.
Hi there!
I’m trying to reproduce this one but not with much luck. Do you mind posting which theme you’re using please, as well as what hosting company you’re with.
Thanks!
MikeI think in this case you need to deactivate all plugins, activate NGG, verify that the editor works, and then activate other plugins one-by-one while checking the editor and determining which plugin causes the conflict.
Thanks.
Deactivate all plugins, and then activate NextGEN Gallery. If the visual editor breaks, then it means that there must be a conflict with the theme. If it’s not broken, then it must be a conflict with one of the other plugins – you’ll need to try different combinations to determine that.
Please post back with the results.
Thanks.
NGG is very popular and therefore used with a wide variety of third party plugins and themes. Some plugins and themes decide to use their own version of jQuery. That isn’t necessarily a problem if the author decides to do that correctly by enqueuing the same version of jQuery but would like to load jQuery from a CDN. But it does become a problem when a third-party plugin/theme overrides to enqueue a different version of jQuery that changes the API interface such as what happened with jQuery 1.9 over 1.8. When that happens, things break. If you look at the definition of wp_deregister_script(), you can see that WP had to do it’s best to stop users from specifying their own jQuery versions in WP-Admin. Although they allow it on the front-end, they discourage it.
It would be very difficult for us, if not practically impossible, to determine if a particular plugin or theme is overriding the bundled version of jQuery for good reason. In any case though, if a plugin/theme needs a custom jQuery version they should enqueue it as a different handle, such as ‘jquery-custom’, rather than override the ‘jquery’ handle WP provides.
—
The fix_query() method in NGG resets the ‘jquery’ handle back to what WordPress shipped with. That is, the ‘jquery’ handle should have no ‘src’ attribute but instead have ‘jquery-core’ as a dependency. The ‘jquery-core’ handle should have a src of ‘/wp-includes/js/jquery/jquery.js’.
Resetting the handle back to how WP intended seems to resolve most of the cases we find, though there will be cases where it doesn’t work. It’s a very difficult problem to resolve in a general way due to the wide matrix of possible plugins/themes that NGG could be installed alongside. If there’s a better way of handling this, we’re open to suggestions.
For the cases in which resetting the ‘jquery’ handle back to what WP shipped with doesn’t work, our support staff will do their best to help determine what the problem might be and relay any details back to the developers for a solution. Your assistance and co-operation is much appreciated. Our goal is to be widely-compatible as possible.
Thanks,
MikeHi Reddo,
What’s your site url? How did you insert font-awesome.css? Are you en-queuing it via wp_enqueue_script?
Thanks,
MikeTry adding this to wp-config.php:
define('WINABSPATH', str_replace('/', DIRECTORY_SEPARATOR, ABSPATH));
It should be added just before:
/* That’s all, stop editing! Happy blogging. */
Thanks,
MikeHi Kapara,
If you’re using the Attach to Post interface:
1) Open the Attach to Post interface by clicking on the gallery placeholder in the Post Content Editor window
2) Open the “Customize the display settings” tab. Select the template you want to use from the “Template” drop-down.
3) Click save.
If you’re using shortcodes, could you what you’re using here for us to see, please.
In any case, I’d love the opportunity to investigate your site further. If you don’t mind submitting a bug report here along with temporary WP credentials, I’d be happy to look into this issue for you. Please mention my name “Mike” in your report so that it gets my attention.
Thanks,
Mike@lagdonkey, NextGEN Gallery uses Pope for extensibility:
https://bitbucket.org/photocrati/pope-frameworkWe opt for using Pope’s adapters rather than hooks/filters so that in the future, if we’d like, we could take NextGEN Gallery to another platform, such as Joomla. Note, porting to other platforms is not on the roadmap, and not likely to be added any time soon.
Thanks,
Mike