Upgrading to Pro broke our website!

[simpleorder]

I was told by Apex support that if i upgraded to pro our website would be fine and that everything until then would be treated as legacy and not changed and any new pages would be with the new Pro features.

But when i upgrade it completely messed everything up.

Thank god we had a backup service in place and quickly setup a restore.

I’ve installed pro in our staging and you can see how its messed up. i’ve also included in the secure note access to our staging so maybe you can help us diagnosis the issue.

Thanks!

[mldarshana]

Hi There,

Thanks for writing in! Are you using CloudFlare CDN? If so, head over to your Cloud Flare account, then Speed tab and then make sure to disable CSS & Javascript autominification options and clear your CloudFlare cache.

Also disable any caching mechanisms running on your server and test it again.

Thanks!

[simpleorder]

@mldarshana how will i know if i am using CloudFlare CDN?

[friech]

Hi There,

I did check the site and no it’s not on CloudFlare. I saw that you have a lot of customization on your child theme. Those customizations where left behind when you switch to PRO, you need to install a PRO child theme and move/copy those modifications on the PRO child theme.

Your site is coming from X version 4.6.1, a lot of changes happened from that version. There will be settings that you need to re-configure on the Theme Options. And you may need to modify some of your customizations on child theme to adhere to the latest version.

Leaping a long update especially if you heavily modified the theme won’t be smooth, this is a case for all themes.

Thanks,

[simpleorder]

@friech posted via a different account asking what would happen if we upgraded to Pro even with custom coded pages and i was told clearly that they would be treated as legacy pages and only new pages would be considered

Will upgrading a website built on ThemeX to Pro mess it up?

Can you please give some more detailed help on how we can start upgrading our website to Pro since we strongly wish to do this but the promise that it will not mess out our website seems not to be true.

Thanks!

[rad]

Hi there,

There is a confusion about the question, it’s a question about upgrading from X to Pro which is okay. But what you did is upgraded it from very old version to the latest which is going to break. Even if you didn’t upgrade to Pro, and you upgrade your X 4.0 to latest then the same thing will happen, it’s going to break to due feature gaps.

Hence with the question that if the pages will stay after upgrade to Pro, it will. But if you upgrade from very old versions to latest (to latest Pro or X), you’ll need to do a lot of fixes. And it’s similar to site maintenance and redesign. You will need a developer or webmaster to transition your site to the latest one. First, try upgrading it to the latest X (not Pro) to see what’s happening

Thanks!

[simpleorder]

Hey @Rad

So i successfully updated my ThemeX to the latest version and everything working fine.

But after i then updated the Theme to Pro everything broke down again.

You can see it in the link i’ve attached:

[Joao]

Hi There,

The provided credentials no longer works, please check.

Thanks!

[simpleorder]

Fixed @Joao

[rad]

Hi there,

Would you mind clarifying what’s broken? Because I switched X and Pro over and over and it’s all the same, no menu, there is a shortcode and same content. I’m not sure about So i successfully updated my ThemeX to the latest version and everything working fine. what’s working fine either. A comparison will be helpful, and some screenshots.

And please note that if you switch a theme with different name, regardless of theme and even a child theme, Wordpress will reset your menu and widgets, so your only option is to re-add or re-assign them. It’s not about legacy page or features, but it’s Wordpress’ doing.

Thanks!

[simpleorder]

@Rad i posted the link to our staging site to clearly show you that while we upgraded to ThemeX fully and then transitioned to Pro many things broke. Our home pages, yes our menus but also more than that too. It seems like much of our custom coded parts of the website broke even though they were supposed to treated as legacy.

I’ll attach links to pages which are even mostly built via Cornerstone and they’re broken too.

Your help is very appreciated!

[ruenel]

Hello There,

Thank you for the clarifications. This happens because you are using a child theme together with your customizations. As soon as you switch to Pro, all those changes in the child theme were no longer applied. To resolve this, I went ahead and edited your child theme’s style.css. I replace this line Template: x with Template: pro. I go to Appearance > Themes and activated the X Child theme. The child theme is now a child theme of Pro theme which applies all your modifications as seen in previous site using X theme.

Hope this explains it briefly.

[simpleorder]

Wow @RueNel

Though i haven’t QA’ed the whole site to see if its 100% working it seems to have fixed everything.

Thank you!

Maybe this should be included in documentation/support to alert people when upgrading from ThemeX to Pro.

[alexander]

You’re welcome! We do provide separate child themes for X and Pro with that distinction.

[simpleorder]

It still seems like part of our website has broken down. Perhaps a css style sheet needs to me moved too? Example:

[rad]

Hi there,

It’s pulling non-existing files, like this wp-content/themes/pro-child/assets/css/custom-styles.css. Do you have any enqueue or static code that adds asset file from pro-child? You should change it to x-child since it’s your active child.

Thanks!