Imagely
Forum Replies Created
-
@fum,
Sorry, I didn’t notice the path before.
/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen\modules definitely doesn’t need to be moved over to wp-content/ngg/.
The purpose of wp-content/ngg/modules is to allow NGG users use their own custom coded templates so that’s why most of the folders are empty – this is expected.
If your old site doesn’t contain a wp-content/ngg/modules/photocrati-nextgen_basic_thumbnails/templates/carousel-view.php custom template for you to move over to the new site at the exact path ( creating it if needed ), feel free to just choose the default carousel-view.php from “NextGen Gallery -> Gallery Settings -> Basic Thumbnails -> Select View” then press “Save Options” and check again to see if that’ll solve it.
- This reply was modified 2 years, 10 months ago by Imagely.
Hi @carlomue,
We are sorry but the plugin version used on your site seems to be extremely old so there are no guarantees that the shortcodes you are using will continue to function as we’ve changed 3 or 4 times their structure and we don’t think the legacy initial version of them is supported anymore so while the main structure may remain as is, it is most likely that you’ll have to manually re-insert the gallery modules/shortcode after migrating to the latest version.
The above being said, we strongly recommend performing a full site and database backup before updating to 3.37.
Hi @stevenew2019,
This looks like a false-positive in the ModSecurity module on your server. Usually, images’ titles containing single quotes can trigger it. You can either ensure that none of your images from the gallery contain single quotes or whitelist the rule.
The rule causing it is rule number 77229500 or 229500, you need to ask your hosting company to remove that rule or create an exception, that is an old rule that dates back to NextGen version 2.x years ago and the issue was fixed back then.
Please let us know if this will help
Hi @fum,
You can copy them but that’s not specifically necessary unless you have created other custom views/templates.
Hi @fum,
The wp-content/ngg/modules/ directory is used to add custom templates ( now named views ) to NextGen Gallery.
You may want to check the source site to see if you had a custom template at the indicated path then create the same path on your new site and copy it there.
HI @mcaskill,
Thanks for your input. We’ll go ahead and register it for our developers’ review.
Hi @mnydigital,
This looks like a false-positive in the ModSecurity module on your server. Usually, images’ titles containing single quotes can trigger it. You can either ensure that none of your images from the gallery contain single quotes or whitelist the rule.
The rule causing it is rule number 77229500 or 229500, you need to ask your hosting company to remove that rule or create an exception, that is an old rule that dates back to NextGen version 2.x years ago and the issue was fixed back then.
Please let us know if this will help
Hi @tvlohne,
Most likely that’s caching related. Sometimes that comes from the hosting side itself. I’d try adding the same album to a different page to see if that’ll show the updated version of it.
Also, you can try adding /?1 at the end of your page’s URL to force it reload the resources.
Hi @mikkelcrunch,
We are sorry but it doesn’t look like we’d have any updates for this feature request. We have a list of over 500 feature requests over the years that our small dev team has to review. Regarding the forum threads – we are actually closing all of them after getting back with a concluding reply.
Worth mentioning that the biggest priority during the last 2 years was removing pope framework which required us a lot of code refactoring and that didn’t allowed us move forward with the new feature implementations as much as we wanted. At this moment – we are thoroughly testing it and we plan to release it sometimes soon if testing goes well. This huge update is going to be beneficial performance-wise for all NextGen Gallery users.
Thanks for your understanding,
Imagely TeamHi @chcw,
Let’s first of all try adding the following constant to your site’s wp-config.php
define('ALTERNATE_WP_CRON', true);If that doesn’t help, you can disable NGG’s transients entirely adding:
define('NGG_CRON_ENABLED', false);Hi @endpoints,
We hope that you wouldn’t mind contacting our support team directly at https://www.imagely.com/report-bug/ so we could have a direct look at the problem.
Thanks
Hi @ispreview,
Thanks for asking us. We are aware of these deprecations and these are one of the reasons why we look forward to completely exclude pope framework from NextGen Gallery really soon ( this was a huge project for us but the good news is that we are now close to a release ). It should also bring performance improvements for every NextGen Gallery user.
Hi @vegaswill,
There’s no such a setting but you can try to add the custom JS rule from below using a plugin like Simple Custom CSS and JS to add a scroll to top on the pagination click event:
jQuery(document).on("ajaxComplete",function(){jQuery(".page-numbers").click(function(){setTimeout(()=>{document.getElementById(document.querySelector(".ngg-galleryoverview").id).scrollIntoView()},1e3)})});Hi @banijadev,
Thanks for contacting us. Checking their logs https://wphive.com/plugins/nextgen-gallery/ it appears that they only point to a generic notice that comes from WP core since 5.8 https://ww.wp.xz.cn/support/topic/error-in-widgets-with-new-wordpress-version-5-8-wp_enqueue_script-and-wp/
We always test our plugins to comply with the latest PHP and WP versions and the majority of our team use PHP 8.2 for their sites without any PHP version related problems.