Upgrade bug going from 5.1.5 to 6.0.6

[co50]

Hey folks, I figured by the 6th point release this bug would be fixed but it’s still there.

When we upgraded our site from 5.1.5 to 6.0.2, the main page loaded all the elements but the font was a generic Times New Roman looking font. So we reverted back.

We just upgraded again from 5.1.5 to 6.0.6 this time and the bug is still present but worse. Instead of all the elements loading with a generic font, now the font still changes but also entire bottom half of the homepage is missing.

Here was the site on 5.1.5:

Here is the site after upgrading to 6.0.6:

And worst of all, here is the site after restoring all files to 5.1.5 but leaving the database as is (this should not happen):

Hoping for a renewed commitment to code quality going forward…

[charlie]

The hotfix for 6.0.7 will probably fix the lower page issue. I haven’t seen font issues brought up since 6.0.3 which is when we had google font fix. In your theme options of V6 what does it say your current fonts are? Are you able to run a staging site for us to check out?

You have a commitment from me. Frankly we had a lot of code to release at once based on the old release strategy. Now that I’m here we’ll be updating more frequently, keeping things up to date, and utilizing Beta more throughout the year to increase stability. I appreciate the patience and we’re here for you during this upgrade process.

[co50]

Hi Charlie,

Wow - that was the most thoughtful response I’ve ever gotten from a Themeco rep. I looked at your responses to other people’s inquiries and saw much of the same. Wow, I hope you stick around. You’re a welcome change from the usual hurried responses I get from support.

I created a staging for this site and upgraded again to 6.0.7. The lower page now appears. But fonts are not right. The fonts in theme options all show “inherit” as the current font. They were set as "Meriweather (Google) in 5.1.5. Upon looking at font manager, the Google fonts that were configured are gone and now the fonts associated with Body and Headers is “Helvetica”.

EDIT: Upon further investigation, your 6.0.7 update is turning on Font Manager, which was not on before. Turning off Font manager resolves the issue and brings back the correct fonts.

[marc_a]

Hey @co50,

We’re glad that you’re able to fix your issue.

Cheers!

[co50]

I need to hop on this again. We upgraded an additional 5 sites that had this bug. Some had font manager on and some did not, but the fonts were screwed up by the upgrade in all of them. Had to change font settings and restore the fonts set for the site to look proper.

Additionally, and this is a big deal - did you guys know that once upgraded to 6.x you CANNOT go back to 5.1.5? Maybe you should put that somewhere. And again, it’s due to the font issue. If you attempt to install and activate 5.1.5 after upgrading to 6.x, it produces Wordpress critical errors referencing your font manager php files.

[ruenel]

Hello @co50,

Can you send us the PHP warning and error messages that were triggered by WordPress critical errors referencing the font manager PHP files? It could be coming from out dated PHP version. be advised that the Pro 6.x will now run with PHP 8.0. If you are using PHP version that is later than PHP 7.4, it will display PHP warnings and errors.

These are the suggested steps in updating the WordPress core, Themeco theme, or plugins in a WordPress site:
1.) Back up your site. This can be done in your hosting account (or using plugins to backup a site).
2.) Clone your site in a staging area. All updates must be done in the staging area.
3.) Update the WordPress core.
4.) Go to Pro (or X) > Validation > Theme Options Manager and download the XCS file.
5.) Update the Pro (or X) theme in Dashboard > Updates > Themes.
6.) Go back to Pro (or X) > Validation > Theme Options Manager and import the saved XCS file. This is to make sure that you will still have the same Theme Options settings.
7.) Update the plugins.
8.) Clear all your caching plugins and browser cache.
9.) Test the staging site if all the updates are working perfectly.
10.) If there are issues and conflicts that show up after the updates, troubleshoot.
11.) If everything works perfectly along with all the updates, push all these changes to the main site.

• The backup is important so that you can always go back to the previous version, especially if you have custom modifications in a child theme or modifications to a plugin.
• Working in the staging area ensures that the live site is still working and your users and customers can still view and purchase your products.

Best Regards.

[co50]

Your reply is very confusing.

We are on PHP 8.0. Pro 5.1.5 worked fine on 8.0. So an outdated PHP version is certainly not the issue. But then you said 6.x will now run with PHP 8.0…OK, but it’s a new version so why would you say “now run”…as if it didn’t before? But then you said using any version later than 7.4 (so 8.0? 8.1?) will display errors.

Can you reconcile which version of PHP 6.x works with and then get back to me?

Anyway, just letting you know for what it’s worth that you can’t downgrade back to 5.1.5 and your 6.0.7 still is messing with fonts. It’s happened on enough of our sites to know it’s an issue with your software.

[ruenel]

Hello @co50,

The Pro 6.x is PHP 8.0 compliant. It works with PHP 8.0. With Pro 5.1.5, using PHP 8.0 or newer will (or might as I will rephrase that again ) display PHP errors or warnings. In your WP site install running Pro 5.1.5 with PHP 8.0, no errors are displayed. You can only see those PHP warnings in your error logs. There were specific functions or some elements that errors and/or warnings to occur. If you are not using those functions/features, nothing is displayed even on the error log.

Pro 6.x is a major update. Downgrading from Pro 6.x to Pro 5.1.5 may have issues which are why the best way to revert to Pro 5.1.5 is by using the backup.

Best Regards.