Hueman theme v3.1.0 release note 44


Improved overall speed performances

  • fixed : the child theme stylesheet loaded before the main one. Back to normal now.
  • Performance improvements compare to v3.0*
    • with the use of minified external script and stylesheet
    • by loading only the necessary resources
    • by grouping the stylesheets into one instead of 3 previously

 

Child theme users

v3.1.0 is safe for child themes : this release has no impact on the templates paths and the functions inside the template.

Note : the child theme stylesheet is now loaded again after the parent one, allowing you to override easily the main css rules.

The previsous version (v3.0.12) released a few hours ago had introduced a new way to load the main stylesheet of the theme. This has create an issue that could disable some custom rules that you’ve added to your child theme style.css.

This is now fixed in v3.1.0. You can add your custom css rules in this file and they will override the default ones.

 

Why not using the style.css file of Hueman for the css ?

The main reason for that is performance. Reducing the size and the number of external files (like css, javascript and images) helps improving the overall loading performances of a website.

 

Compacting CSS code can save many bytes of data and speed up downloading, parsing, and execution time.

Gtmetrix

 

This main style.css file provides details about the Theme (in the form of comments above) that is read by WordPress server side, but it can’t be minified. ย ( Minification is a technique to compress a css file and therefore improve speed (page load time) of your website.)

In the previous versions, the Hueman theme was loading 3 stylesheets not minified : style.css, responsive.css and font-awesome.css. Those files have now been concatenated into a singleย minified file : main.min.css, located in assets/front/css

 

Learn more about WordPress and website performance best practices here :

 

 

 

Changelog dated April 16th 2016

= 3.1.0 April 16th 2016 =

  • fixed : child theme stylesheet : style.css is loaded again as a dependency of the parent Hueman theme style, to make it easier to override the main stylesheet rules
  • fixed : wrong path to the default font Titillium in main stylesheet
  • fixed : php notice undefined var _faq_url in /wp-content/themes/hueman/functions/class-admin-page.php

 


44 thoughts on “Hueman theme v3.1.0 release note

  • Reply
    Sourabh

    Hi,

    Just wanted to confirm is our theme is compatible for auto load next article or post?

    Kindly let me know with your feedback

    Thanks
    Sourabh

  • Reply
    jessica gomber

    Hi Nicolas. I am super new to wordpress and I am using the child theme. I just did an update that was released. Do I need to do anything special to update the child theme? Or does it do it automatically? Thanks.

    • Reply
      Menaka S

      Hi Jessica,
      The very purpose of using a child theme is to ensure that your customization of the theme does not get overwritten with updates. Youhave done a good thing there by using a child theme. So, don’t worry. Sit back and enjoy. ๐Ÿ™‚

  • Reply
    RDelpoplo

    On mobile version the page navigation, when gets big (example, 20 pages), prevents the resize of the page to fit the screen.

  • Reply
    Touchstone

    Good morning.
    After update 3.1.0 the homepage doesn’t load correctly in mobile (iPhone), is showing the information like a text page. I don’t use responsive layout. With previous versions the info was showed correctly, now on desktop is ok but on iPhone no. Another issue i found is that now when you don’t use responsive layout, the page doesn’t appear fitted to screen as before. Now it appears the top left corner full screen forcing to pinch to zoom each time you go to home page or any post. Could you please confirm if there is a setting that have to be configured to show the pages as was in earlier versions? Thanks in advance.
    PD. Attached 3 pictures: 1.- Showing how is rendering the page in mobile phone with last update. 2.- Showing how is rendering the page after version 3 3.- Showing how was rendering in earlier versions (showing full page. This is the layout i want to recover

    • Reply
      presscustomizr

      Hi !
      thanks for getting in touch.
      Would you mind reporting those issues on the Hueman forum ?
      This is where our team collect and addresses the problem.
      Please also include the pictures (you can use an online screeshot sharing service to do it like https://snag.gy/ )

  • Reply
    Michele Sanchioni

    Hi Nicolas, what do you recommend between W3 Total Cache, WP-Super Cache, Autoptimize? Thank’s for your job!

  • Reply
    presscustomizr

    Hello,
    using a child theme is a very good practice to customize the theme. I’m not sure to understand what is exactly the problem. If it’s about css, you can add your custom rules in your child theme’s stylesheet (style.css) and they will override the parent’s theme ones.

    • Reply
      RDelpoplo

      Every update deletes the translation.
      I’ve copied hu_load() in functions.php modifying this line:

      load_theme_textdomain( ‘hueman’, get_stylesheet_directory().’/languages’ );

  • Reply
    presscustomizr

    OK. I know how frustrating it can be to frustrating it can be to see regressions after an update.
    However, the stylesheet concatenation and minification was a necessary step to improve the performances of the theme.
    This won’t be changed anyway from now on.
    Thanks for your feedback.

  • Reply
    RDelpoplo

    Sorry but from 3.0.12 the updates broke my child theme because I use a different sidebar width. Before the update there was a separate responsive.css loaded after style.css. Now i’ve to fully redefinite a lot of rules. ๐Ÿ™
    This update mitigated the problem and the child theme support is better than before as I don’t have to redefine hu_styles() ๐Ÿ™‚

  • Reply
    Guilherme Chagas

    Thank you very much for your effort.. Your theme is amazing and I’m very pleased..

    Yesterday I tested my blog speed and I got 78/100 with today’s update I got 89/100 which is a huge improvement.

    The only thing that I miss that would make my life a lot easier is the option to change the header background without disabling the logo and site tag…

    Keep going mate… Much appreciated

    • Reply
      presscustomizr

      Great. thanks for this performance feedback ๐Ÿ™‚

      There are other improvements to optimize the loading of the images. This should also have a postive impact on your speed performance.
      I’ll keep you posted.

    • Reply
      presscustomizr

      In v3.1+ you don’t need to import the parent style.css file anymore since it doesn’t contain any cs rules anymore.
      Thanks

      • Reply
        Wolfneo - Logganeo

        Hello
        I use a translator to write in English, you do not understand, I don’t speak Hueman V3.1 but your child theme found on another page of your site, which is not encoded as suggested by the WordPress codex.
        http://presscustomizr.com/hueman/

        There is your child theme for Hueman, we find code import in style.css so that should be a code in functions.php instead.

        On all my sites, I created a child theme, in accordance with the instructions of the WordPress codex.
        Thank You

Leave a Comment

Your email address will not be published. Required fields are marked *

Please check the following point before adding your comment

  1. - Did you check that you have the latest version the theme installed ?
  2. - Did you read the documentation ?
  3. - If you think it could be useful, please check your system informations : Navigate to Appearance > About Customizr and go to the bottom of the page.
  4. - Did you check if your issue was already resolved ? Before posting a new topic, you'll want to make a quick research with our Google powered search tool below.

You may also use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">