Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thread Starter newwithtags

    (@newwithtags)

    Hello, JN,

    Thank you for taking the time to explain the issue which is causing the error.
    I understand, and it is also not a problem for me at this point.
    Once again, congratulations and thank you for a super-efficient plugin.

    Kind regards,
    Cristina.

    There is an extra comma in your code. Try this:

    add_action( 'after_setup_theme', 'my_child_theme_image_size', 11 );
    function my_child_theme_image_size() {
            add_theme_support( 'neve-blog' );
    	remove_image_size( 'neve-blog' ); 
    	add_image_size( 'neve-blog', 338, 225 );
    }

    step 1- place the code in your child theme’s functions.php
    step 2 – clear your cache
    step 3 – regenerate thumbnails.
    If your changes are not visible right away, try visiting your site in a private window.

    Just to be clear, this will change the size of the featured image inside the post. Your featured images have a 338 px width now when viewing the post page, so the above code would generate the same results.

    The code above will not change the image thumbnail sizes which are called on the front page, so it will not help to improve your pagespeed score.
    To serve scaled images on the frontpage and other pages, you can:
    – go to regenerate thumbnails plugin settings and add a new image size with the dimensions you require (the size needed on the homepage) and a relevant name; (I think this is also possible with smush)
    – regenerate thumbnails for the newly created image size; (I think this is also possible with smush)
    – edit your homepage / other pages, select the blocks you use to show posts; in the block options panel, on the right, select featured image options and choose your newly created size.

    There might be an easier way, but not that I know of.

    Also, from what I can see, you (should) serve scaled and optimized images via smush cdn on your site so you might ask them for a solution to properly sizing your images.

    You can try to add_theme_support:

    add_action( 'after_setup_theme', 'my_child_theme_image_size', 11 );
    function my_child_theme_image_size() {
            add_theme_support( 'neve-blog' );
    	remove_image_size( 'neve-blog' ); 
    	add_image_size( 'neve-blog', 1060, 530, true );
    }

    Obviously, you will need to change the 1060, 530 to your required size. The “true” after the size means the images will be cropped. If you want the images scaled, not cropped, simply remove the “, true” bit.

    I had trouble getting it to work following the Theme Isle tutorial as well, until I came across this topic: https://ww.wp.xz.cn/support/topic/featured-image-is-being-cropped/

    Thread Starter newwithtags

    (@newwithtags)

    Hei, @gdandrija,

    Thank you kindly for looking into this and notifying your developers. I will mark this as resolved here and I will follow the progress on github; thank you for the link.

    Have a lovely evening,
    Cristina.

    Thread Starter newwithtags

    (@newwithtags)

    Hei @gdandrija

    Thank you for your answer.
    The plugin we use is AMP and the theme is Neve.
    I have tried your suggestion and disabled all plugins, switched to a default theme (twenty twenty) and I enabled Coblocks and AMP. The result is the same, with the desktop version being a carousel, as expected, while the amp version shows as a list of posts. Screenshots with the default theme regular page amp page

    Regards,
    Cristina

    this rating is irrelevant. :-/

    Actually, reading again, I realised you want your featured images uncropped, so you will want to remove the “true” setting, as shown here: Crop Mode

    So, if it’s still an issue, you could try this in your child functions:

    add_action( 'after_setup_theme', 'my_child_theme_image_size', 11 );
    function my_child_theme_image_size() {
            add_theme_support( 'neve-blog' );
    	remove_image_size( 'neve-blog' ); 
    	add_image_size( 'neve-blog', 1060, 530 );
    }

    You can try to add_theme_support:

    add_action( 'after_setup_theme', 'my_child_theme_image_size', 11 );
    function my_child_theme_image_size() {
            add_theme_support( 'neve-blog' );
    	remove_image_size( 'neve-blog' ); 
    	add_image_size( 'neve-blog', 1060, 530, true );
    }

    I had trouble getting it to work following the Theme Isle tutorial as well until I came across this topic: https://ww.wp.xz.cn/support/topic/featured-image-is-being-cropped/

    @mrftun I’m happy my comment helped solved the pagespeed warning, but I regret it did not help increase the dowload speed. I’m not sure what you mean by “download speed” – do you mean your pagespeed score?
    Just like @notbatman09, who started this thread, I use the Asset Cleanup plugin on several sites to help increase page speed score and decrease page downloading times. It’s useful for on-page offloads, for those plugins you use only on certain pages, but would still load on all pages. The 2 preload options (google and local fonts) work well and it came in extra handy in a specific case, when manually preloading google fonts in the header failed to produce results.
    You could try using this plugin to increase your google pagespeed score. Do so with caution, up-to-date backups and using the “test mode”, so you can see the effects of your changes before publishing them on your site.

    Hey, @piotrk87, I don’t know if you still have this issue but you could try a relative path and/or specifying the crossorigin attribute. For example:
    <link rel="preload" as="font" href="/wp-content/themes/Newspaper/images/icons/newspaper.woff?19" type="font/woff2" crossorigin="anonymous">

    Adding add_theme_support( ‘post-thumbnails’ ); somehow worked finally!

    Same here. I could not get it to work following the tutorial, not until I read this and followed your suggestion to insert add_theme_support. I even tried turning off all plugins, caching, etc.
    Thank you, @unaizakhalid, for sharing this bit of info. 😊

    I don’t know what else is wrong with your preload, but I noticed you are using ”, instead of ”
    <link rel=”preload” href=”https://brightrockmedia.com/wp-content/themes/hitmag/fonts/fontawesome-webfont.woff2?v=4.7.0” as=”font” type="font/woff2" crossorigin>
    should be
    <link rel="preload" href="https://brightrockmedia.com/wp-content/themes/hitmag/fonts/fontawesome-webfont.woff2?v=4.7.0" as="font" type="font/woff2" crossorigin>

    Hello, @putchi

    To speed up the process of being indexed by search engines, you can manually submit your site to be indexed.

    To submit your url to Bing’s webmaster help & how-to: “Bing recommends webmasters using the Submit URLs to get their web content indexed as soon as they published or updated it online.”
    See how to do this in this article: https://www.bing.com/webmaster/help/submit-urls-to-bing-62f2860a
    Or you could submit the XML sitemap.

    There are plenty of articles of online which guide you through the process of submitting your website to be indexed by search engines, such as https://www.semrush.com/blog/submit-to-search-engines/ or https://ahrefs.com/blog/submit-website-to-search-engines/

    According to Jetpack, “In order to verify your site for webmaster tools, you normally need to add a “meta tag” to your page, or a new DNS entry. This isn’t always straightforward, so Jetpack’s Site Verification module is here to help.” See more here https://jetpack.com/support/site-verification-tools/

    I have tried searching for your site, it appears ok on google, showing a proper meta description, but on Bing, I cannot find it at all.

    I hope this helps.

    Best regards,
    C.

    Thread Starter newwithtags

    (@newwithtags)

    It’s solved. I’ve found the old plugin responsible for the schedule post problem. 🙂

    Thread Starter newwithtags

    (@newwithtags)

    Hello, Augustin & all,

    Sorry for not checking back. Thank you, the update worked smooth and now we are happily customising our new theme.
    The posts did not revert to drafts, as I imagined.
    There is one problem I cannot fix – as I was saying, the “schedule post” function has been modified to publish future posts. It served an old plugin which is disabled.
    Now we’d like to use the schedule post option which is super handy, but the update and switching the theme did not solve it.

    It seems like the modified functions.php is in the old theme folder, so why should this affect the new theme’s behaviour?

Viewing 14 replies - 1 through 14 (of 14 total)