Imagely
Forum Replies Created
-
Hi @anna-blume,
We have deprecated NGG’s Custom CSS field as it was duplicating the default WP’s one from “Appearance -> Customize -> Additional CSS”.
Adding/moving your custom CSS there should apply just fine for any NextGen galleries.Hi @hudlee,
Reading the first message, our guess is that you use Nginx web server and unlike Apache, it doesn’t make use of .htaaccess at all ( it can use
nginx.confinstead ).Please try editing:
nextgen-gallery/products/photocrati_nextgen/modules/ngglegacy/ngg-config.phpand change line 14 from it to indicate the server path in case that you placed WP-CONTENT outside the classic file structure.Hi @hudlee,
This is most likely a routing related issue. Please try adding the constant from below to your site’s wp-config.php to see if that’ll resolve anything:
define('NGG_GALLERY_ROOT_TYPE', 'content');Hi @hudlee,
Could you please let us know what hosting provider you use for your site?
Hi @gamicord,
Thanks for asking us. We can confirm that this is one of the most requested features that we have registered but having in mind that we are a very small team, we need to weight the cost/benefit of things we implement, there are 500+ feature requests on our board at the moment.
When we start a development cycle we try to choose the most impactful features that will benefit the largest base possible and start working on them or fully implement them depending on their complexity, for example getting rid of POPE framework from NextGen Gallery alone took us approximately one year and we are still not ready for a release yet ( but that’s going to be highly beneficial performance-wise for all the NextGen Gallery users ) also we need to apply emergency fixes for medium and large issues that appear on top of the regular plugin maintenance and updating for compliance with WordPress, PHP, MySQL, etc. This unfortunately does not leave as much room as we want to keep improving the plugins.
That’d be too resource consuming and the uploading process already implies lots of sub-processes so in the best scenario it’s going to be a duplicate images remover separate feature should our developers decide positively on this one sometime in the future.
Hi @centoasa,
Unfortunately, NextGen Gallery doesn’t come with such a mechanism and it’ll store as many copies of the image as you’d upload adjusting the filename.
We can only add it as a feature request to our list.
Thanks for your understanding
Hi @luxworx,
This looks like a database encoding constraint. Could you please check with your hosting provider to see if encoding is set to allow special Polish characters?
We were able to create a gallery with exactly same name “OBIAD DZIĘKCZYNNY” and to upload images to it in our end.
Hi @theodelaruelle,
Please reach to our support team directly at https://www.imagely.com/support/ should you have any questions for us now that you have a premium account with us.
We are not allowed to offer any sort of premium support here in the forum.
Thanks for your understanding
Hi @theodelaruelle,
Please reach to our support team directly at https://www.imagely.com/support/ should you have any questions now that you have a premium account with us.
We are not allowed to offer any sort of premium support here in the forum.
Thanks for your understanding
- This reply was modified 3 years, 8 months ago by Imagely.
Hi @ptienhung,
Unfortunately, NGG’s comments use a different taxonomy which makes them unreachable for the default “Comments” widget that comes by default with WordPress.
We suggest using a third party plugin that adds its own widget and includes taxonomies support such as Recent Comments Widget with Excerpts.
- This reply was modified 3 years, 8 months ago by Imagely.
Hi @dickraney,
That’s odd. The option should ensure that NextGen’s lightbox doesn’t load. If your site uses some caching or performance plugins, please try to clear the cache after selecting “None” for NextGen’s lightbox setting then hard refresh the page (Ctrl+Shift+R in Chrome) to see if that’ll solve it.
Hi @whiskydog,
We have removed any
create_function()function calls starting NGG 2.2.30 version back in 2017 to be compatible with PHP 7.2 or newer versions so respectively – it shouldn’t be NGG triggering this issue.First of all I’d perform a plugin conflict check by deactivating them one by one to see which one causes the error.
We are not allowed to provide any premium related support here in the forum but you can feel free to reach to us directly at https://www.imagely.com/contact/ and we’d be happy to answer your questions.
Hi @takesport,
Feel free to submit a request at https://www.imagely.com/report-bug/ for us to have a direct look at it.
Thanks