PRE-Update questions from 2.2.5 to 3.1.1

Hi webbeetle. Give this a read and see if it helps:

1. Theme update first, then the plugin.

2. The sharebar is not longer included in the theme. If you’re not using the sharebar or theme shortcodes then you don’t need the plugin.

3. Theme image sizes have remained the same.

add_image_size( 'thumb-small', 160, 160, true );
add_image_size( 'thumb-standard', 320, 320, true );
add_image_size( 'thumb-medium', 520, 245, true );
add_image_size( 'thumb-large', 720, 340, true );

4.

I copied style.css into the \child directory

If that means you copied the entire theme style.css file into your child theme, that’s not recommended. The child theme style.css file should only contain styles you want add or change. If you have custom css in your child theme style.css file you should move it all to the beginning of the file (under the heading section) and then remove everything else. Also, you no longer need the @import line; the parent theme automatically loads both the parent and child theme stylesheets. As a side note the parent theme stylesheet is now located in /assets/front/css/main.css. There is also a minified copy named main.min.css. The theme has an option to load the minified copy. See Customize > Global settings > Performance and SEO > Use a minified stylesheet.

5. Yes, the widget names have remained unchanged for now. However, if you have any of these in your child theme, see my Additional Notes below.

6. Don’t know if anyone has tested that or not. Since it’s a commercial plugin you might check on the plugin support page: https://wp-rocket.me/support/

7. The header image is still an option; see Customize > Header > Header Design.

8. Goggle fonts are not included with the theme; you’ll still need your plugin.

I guess it might be better to run my site for a couple of days with only the latest WP version before I do the next major theme update.

I think that would be a good approach; easier to resolve issues if you’re only dealing with one piece at at time.

Additional Notes.
There are two significant changes with the new version:
1. All the theme options have moved to the Customizer.
2. Many of the theme functions and files have been renamed and moved. For example, in your child theme single.php file you’ll see this:

<?php if ( ot_get_option( 'post-nav' ) == 'content') { get_template_part('inc/post-nav'); } ?>

The option name and the template location have changed:

<?php if ( 'content' == hu_get_option( 'post-nav' ) ) { get_template_part('parts/post-nav'); } ?>

If you don’t update those then you’ll find parts of your pages that don’t work. You could go through your child theme files and update all the different calls manually. However, a better approach would be to make a note of the modifications you made in each file, copy the new version of the file to your child theme and overwrite the old version, then reapply your changes. This would also apply to any theme functions you copied from the old theme into your child theme functions.php file. The old functions.php file has been split into different files that now reside in /functions.

Since you have several files in your child theme the time and effort to update to the new version will be some amount of work. But it’s really the only way you can assure yourself that your child theme files are current.

Here are a couple of references if you haven’t already seen them:
https://docs.presscustomizr.com/article/236-first-steps-with-the-hueman-wordpress-theme
https://docs.presscustomizr.com/collection/224-hueman-theme
https://presscustomizr.com/category/hueman-releases/

Hope that helps. Let us know if you have any other questions.

Thanks for the EXTENSIVE reply!
Very much appreciated.

I checked my style.css later yesterday: it’s not a complete copy although I copied some sections which I didn’t change later on. So it only needs a little cleaning up.

Most of my php changes don’t go very deep so I hope (the best) that not much will be affected by the changed path names you mention. I seem to recall that I have an inactive plugin [Child Theme Check] which compares version changes – that should make it easier.

Thanks for the links – some I didn’t know about. I’ll let you know early next week how it went…

First the good news: most of the update went okay.

But there are plenty of small niggles, like the thing with missing ‘Related Posts’ – luckily I found the reference in recently resolved tickets…

A couple of things which keep bothering me:

1. my pages seem to never stop loading! I didn’t use to have this issue before so I don’t believe it’s plugin related…

2. my social following links on top of sidebar now break in line, they sit BELOW the FOLLOW text. If I change the style, either delete the UPPERCASE or the float:right they sit in the same line… Weird!
https://dare2go.com/hotlink/hueman-social.jpg

I need to do more testing for other issues. Hopefully there will be few.

Another thing which had changed: my Jetpack mosaic galleries were suddenly in a container with a class data-original-width="500"

I found a solution on WP support https://www.ads-software.com/support/topic/where-does-tiled-gallery-get-width-size-from and added the suggested lines to function.php in my child theme:
data-original-width="800"
Where did that one come from?

Overall: wouldn’t it be helpful to have one sticky post listing such theme issues one has to expect after update? Would make finding solutions to these things much quicker…

First the good news: most of the update went okay.

That’s good to know.

my pages seem to never stop loading!

I didn’t have that issue. The site loaded complete in approx. 3 seconds.

my social following links on top of sidebar now break in line,

I’ll take a look at that.

Where did that one come from?

Not sure. Jetpack has issued at least a couple of updates since WP x4.5 was released.

wouldn’t it be helpful to have one sticky post listing

wp.org doesn’t permit sticky posts on theme support forums. Plugins, yes; themes, no.

my social following links on top of sidebar now break in line

That’s due to the number of links. In the default configuration there is room for 6 links and icons. You have 7 links defined so it pushes the list down. If you need 7 links you could use this css to adjust the display:

/* adjust padding for 7 social links */
.s1 .sidebar-top {
    padding: 15px 20px;
}

Thank you for your quick reply! I’m making slow progress: a couple of problems are solved, and a number of new issues which need attention:

The Social Follow links had somehow 500px added as an extra link with a tiny unformatted icon. Don’t ask me how or when it happened (I’m not even on 500px). Maybe 500px was added to the database and activated automatically?

I have removed it via the new WordPress Customizer (don’t get me started on that stupid tool! I hate it already with a passion. It is so slooow, because it has the live preview next to it, and you need multiple clicks to get anywhere. Give me back ALX’s widget page any time, that was so much easier… Not your fault! It’s just a general trend in web design which drives me crazy. For the sake of a “cleaner user interface” things get buried where only the expert user can find them! I used to reorganise our footers quite frequently, cut things from one and insert into another footer section – all on the one ‘widget’ page. Now I need to open each one individually, if I want to move multiple things around I have to paste all footer content into a notepad file and copy from there. Minimum 10 clicks more required [with the lengthy ‘saves’ to wait for], and in between the footers on the page look like a mess because every single one is updated individually. Grrr!). Now that 500px is gone the line doesn’t break any more between the FOLLOW and the icons. That’s one problem gone.

Issue 1:
BUT now the Social Follow links are in the wrong order! That’s not the order I want them in, Instagram is our second-most important SM account.
See screen captures: https://www.dare2go.com/hotlink/hueman-social-2.jpg
How can I fix that?

Issue 2:
on mobile view the button to open the ‘Menu’ (the Hamburger symbol which expands the menu) is now white. Since I changed Hueman drastically to a much lighter colour scheme one can hardly see the button.
I think in the old Hueman version this was controlled by the style class
.fa {color: #333;} <<< in my child style.css
See screen capture: https://dare2go.com/hotlink/menu-button-on-mobile.JPG

This .fa doesn’t seem to have any affect in the new version. On the limited screen size of mobile width I can’t find out with Firebug which style is applied to the icon (not enough width to read the code lines). Please help me out here!

Issue 3:
Somehow my ? line is not updating (I had this issue already in my previous version – basically since January this year). It shows correctly with 2016 in Customizer and still with 2015 on the page. I’ve cleared my cache multiple times, went through all the updates, and it’s still wrong. I don’t have a custom footer.php in my child theme, so it’s certainly not hard-coded into that…
Where is this hiding? How can I fix it?

Issue 4: deleted!
I just discovered that we still have the ‘old’ widgets page. Thank havens!

I thought I had fixed issue 2.
The style class is.nav-toggle, now set to color: #333;…
What does it do (in addition to giving me a dark menu button)?
It turns all Social Follow icons black!
More confusion…

Issue 1 and 3 also remain open – they really have me baffled!

Back to first issue report: never ending loading.
The home page stops correctly, I seem to have this issue more with individual posts (which keep loading)…

update: I believe I really (???) have issue 2 fixed!
And no more problem with black Social Follow icons…

The rest remains as big ?

Last update: really sorry, I made an idiot of myself!

I think I now solved all issues.

1. The order of the Social Follow icons wasn’t saved.

2. On the server was a footer.php in the child folder with hard-coded (c). Why that wasn’t on my local mirror remains a mystery to me.
So the issue 3 is also resolved!

My ‘Child Theme Check’ also complains

header.php: Parent theme is missing version keyword.

Please close this as [resolved]!

…and thanks for your patience!

Hi webbeetle,

Only you can mark this thread as resolved, because it’s created by you.

Thank you

Gosh, I must have been under a lot of stress the last couple of days.

I seriously looked y’day for the check box to close it – didn’t see