Forum Replies Created

Viewing 15 replies - 1 through 15 (of 20 total)
  • This is fully fixed now and here is a summary of the issue:
    It looks like that the theme developer set content width 625px even the wider screens were available to get the content up to 825px wide and this didn’t allow to add wider images in content then 625px.

    Adding this code in a child theme functions.php file which overwrites default theme content width limitation:

    if ( ! isset( $content_width ) ) {
    	$content_width = 825;

    More info in official WordPress documentation here:

    • This reply was modified 10 months, 4 weeks ago by gintsg.


    Actually, I think that I dug the issue where there is no issue.
    It’s how WP works and it doesn’t allow to choose wider images as the content is.



    Thanks @sterndata

    I just tested the same code on another WP instal on the same server and it works.

    The issue is only with one WP. that website has a big history, but the issue is even I switch off all plugins and using Twenteen Seventeen default theme. But for the Twenteen Seventeen, the limit now is 525px max. For that theme, I can’t get higher pictures then 525px. It looks like that for some reason the website is respecting content width and use that as for the max number for images. Totally strange.

    I moved that website recently to test server as a need to do updates, but it was migrated on fresh WordPress install and I copied only files into wp-content folder and database.

    The same issue is on the live server website.

    Any hint where can look for something that still could affect website if all plugins are deactivated and are using default theme? Any tips how can troubleshooting this, as I need to find the issue source. Maybe something in a database could affect this?




    And here is an update how it looks like if I embedding the image in a post:
    <img class="alignnone size-custom-medium-full-width wp-image-34638" src="" alt="" width="625" height="287">

    As you can see, the image is cropped and the right version of the image is chosen, but width=”625″ height=”287 is max 625px for all images.

    If I choose any image version under 625px width it works properly.

    And the same changing default Twenteen Seventeen theme:
    <img class="alignnone size-custom-medium-full-width wp-image-34638" src="" alt="" width="625" height="287" srcset=" 830w, 300w, 768w, 625w, 410w, 1180w" sizes="(max-width: 625px) 100vw, 625px">

    But here: sizes=”(max-width: 625px) 100vw, 625px always is max 625px.

    • This reply was modified 11 months ago by gintsg.
    • This reply was modified 11 months ago by gintsg.


    Thanks @sterndata

    Yes, I regenerated thumbnails with this plugin:

    The tests were made even with bigger images over 3000px wide and still nothing.

    The screenshot is from the image with 1920x770px size.

    And the same issue is with freshly uploaded images as well, not only with old ones after regenerating thumbnails.

    And another interesting thing, that I can choose original Full Size, but nothing between Full size and 625px wide.



    This is amazing! Thank you for your support!



    Thank you! It would be great if can do something like that. If you could share the code snippet idea or just let me know when it’s possible to use the hook and I will figure it out.

    Thanks a lot for your support, it’s really worth to move hosting to LiteSpeed server. cheers.



    Report number: SONQKSJG

    At the moment I switched off all Caching in this plugin and do caching with another WP caching plugin, but with LiteSpeed do all minimisation etc. and results are very good.

    I just wanted to ask, could it impact HTML rendering speed if the LiteSpeed server is not used and LSCache Module is disabled, but is used another server setup, i.e. standard Apache?

    • This reply was modified 1 year ago by gintsg.
    • This reply was modified 1 year ago by gintsg.

    Thank you very much for this update! This is great!


    Same here. Would like to see this option.

    Same here. This is important to be editable and should be an option to disable it.

    Thank you! The issue report is created here:

    @mazedulislamkhan I didn’t find any options in NextGen gallery where to set robots metas. So far my experience is that I did this just with Yoast SEO plugin.

    I did some additional test with all other Yoast SEO settings and fields for the tag page. Additional problem is, that the Custom Canonical link tag field not working as well. So, for specific NextGen gallery tag pages not rendered any data which you can define under Yoast SEO / Settings:
    – Allow search engines to show this Picture tag in search results?
    – Canonical URL
    And global settings under Search Appearance – Yoast SEO / Picture tag (ngg_tag) for:
    – Show Picture tag in search results?

    If I change Page Title, Meta Description etc. Then data from these fields are rendered properly. Only Canonical URL and Meta Robots tag not rendered. But the page is removed from the sitemap.xml page. You can see the updated page here:

    Both of these fields settings is not rendered on the tag page.

    • This reply was modified 1 year, 3 months ago by gintsg.

    Thank you! Here it is:
    ### WordPress ###

    Version: 4.9.4
    Language: en_NZ
    Permalink structure: /%year%/%monthnum%/%day%/%postname%/
    Is this site using HTTPS?: No
    Can anyone register on this site?: No
    Default comment status: open
    Is this a multisite?: No
    User Count: 1
    Communication with is reachable
    Create loopback requests: The loopback request to your site completed successfully.

    ### Active theme ###

    Name: Twenty Seventeen
    Version: 1.4
    Author: the WordPress team
    Author website:
    Parent theme: Not a child theme
    Supported theme features: automatic-feed-links, title-tag, post-thumbnails, menus, html5, post-formats, custom-logo, customize-selective-refresh-widgets, editor-style, starter-content, custom-header, widgets

    ### Other themes (2) ###

    Twenty Fifteen (twentyfifteen): Version 1.9 by the WordPress team
    Twenty Sixteen (twentysixteen): Version 1.4 by the WordPress team

    ### Must Use Plugins (1) ###

    Health Check Disable Plugins: Version 1.3

    ### Active Plugins (3) ###

    Health Check: Version 1.0.1 by The community
    NextGEN Gallery: Version 2.2.54 by Imagely
    Yoast SEO: Version 7.1 by Team Yoast

    ### Inactive Plugins (2) ###

    Akismet Anti-Spam: Version 4.0.3 by Automattic
    Hello Dolly: Version 1.6 by Matt Mullenweg

    ### Media handling ###

    Active editor: WP_Image_Editor_Imagick
    Imagick Module Version: 1673
    ImageMagick Version: ImageMagick 6.8.9-9 Q16 x86_64 2017-07-31
    Imagick Resource Limits:
    area: 8 GB
    disk: -1
    file: 768
    map: 8 GB
    memory: 4 GB
    thread: 1
    GD Version: 2.1.1
    Ghostscript Version: Unable to determine if Ghostscript is installed

    ### Server ###

    Server architecture: Linux 4.4.0-116-generic x86_64
    PHP Version: 7.0.28-0ubuntu0.16.04.1 (Supports 64bit values)
    PHP SAPI: fpm-fcgi
    PHP max input variables: 1000
    PHP time limit: 30
    PHP memory limit: 256M
    Max input time: 60
    Upload max filesize: 128M
    PHP post max size: 128M
    cURL Version: 7.47.0 OpenSSL/1.0.2g
    SUHOSIN installed: No
    Is the Imagick library available: Yes

    ### Database ###

    Extension: mysqli
    Server version: 5.7.21-0ubuntu0.16.04.1
    Client version: mysqlnd 5.0.12-dev – 20150407 – $Id: b5c5906d452ec590732a93b051f3827e02749b83 $
    Database prefix: wp_

    ### WordPress constants ###

    ABSPATH: /var/www/html/wptest/
    WP_HOME: Undefined
    WP_SITEURL: Undefined
    WP_DEBUG: Disabled
    WP_DEBUG_LOG: Disabled
    SCRIPT_DEBUG: Disabled
    WP_CACHE: Disabled
    COMPRESS_CSS: Undefined
    WP_LOCAL_DEV: Undefined

    ### Filesystem permissions ###

    The main WordPress directory: Writable
    The wp-content directory: Writable
    The uploads directory: Writable
    The plugins directory: Writable
    The themes directory: Writable
    The Must Use Plugins directory: Writable

    So, I just installed completely new WordPress and installed only two plugins Yoast SEO and NextGEN Gallery. Everything is the latest version.

    1. Make sure the issue doesn’t persist when Yoast SEO is disabled.
    If the Yoast SEO is disabled there don’t have any robots tags as well. But it’s because Yoast SEO is disabled which should do the task.

    2. Check for conflicts.
    I installed the Health Check. The check doesn’t make sense because I have installed only two additional plugins and WordPress default theme. The only two plugins what I can disable for Health Check are Yoast SEO and NextGEN Gallery.

    3. Check for JavaScript errors with your console.
    There don’t have any JS errors.

    At the moment NextGENN Support team didn’t answer my message on their support board. No answer yet.

    Here is my test page:
    WordPress 4.9.4
    Twenty Seventeen 1.4
    Yoast SEO 7.1.0
    NextGEN Gallery 2.2.54

    Added test gallery in NextGEN Gallery with one tag: test-tag.
    The only settings what I changed in Yoast SEO are: “Picture tag (ngg_tag)” -> “Show Picture tag in search results?” set to NO

    For security, I added X-Robots tag from server side sitewide. But this shouldn’t impact the issues.

    Should I upload this on GitHub or this description will get sent to developers?


Viewing 15 replies - 1 through 15 (of 20 total)