Pro 5.1.5 Upgrade to Pro 6 Beta 2 - 4 Issues

[urchindesign]

I’ve upgraded a super basic site from Pro 5.1.5 to Pro 6 Beta 2.

The site is basically just a blog, as a companion to a custom built Job Portal, using the default settings and Pro default templates.

These are the settings in Pro 5.1.5

And this is what it looks like in Pro 6 Beta 2 (I think changing the default theme template set up is affecting existing set ups.) So it is removing the “Site Layout / Content Layout” which was “Content / Sidebar” and changing it to “Full Width”.

By the way clicking “Cornerstone -> Theme Options” in the WP dashboard still opens and blank screen with no preview and no visible theme options. You sill need to go to the panel and choose theme options from the icons. No point to having a menu option that says “Theme Options” if it doesn’t open the theme options.

The Second Issue is with the header which also looks different.

Pro 5.1.5

After upgrade to Pro 6 Beta 2

[kory]

@urchindesign, thanks for writing in and sorry for these issues.

1. For the “Content Layout” in Theme Options, this old default of “Content / Sidebar” was updated in the last Beta to the “Fullwidth” option due to the fact that the vast majority of users wish to start from this general layout instead. We updated the default option in Theme Options and as long as your Theme Options were saved at least once in the past, this should not have changed on upgrade. I’m assuming you had at least saved the Theme Options once on your old build, correct?
2. We also updated the default page template to be the “No Container | Header, Footer” setup as this is widely preferred by users. I couldn’t tell by part of your comment if you were alluding to this being an issue as well. Could you please confirm this for me?
3. For your header issue, it appears that perhaps your breakpoints didn’t keep as you updated your site? I tested this myself by building out a header on the previous version of Pro, applying breakpoints to multiple containers within a Bar to hide / show my “Desktop” and “Mobile” navigations when necessary, and when I updated to Beta 2 after all of that, my breakpoints remained. It seems I am unable to recreate this exact issue…did you have any custom CSS in this header? If you go to those Elements, are their breakpoints not present anymore? A little more context would be helpful in deducing what might be going on.

Thanks!

[urchindesign]

Yes, my point is that with the changes you’ve made in the beta, “your points 1 & 2”, seem to be causing issues with upgrading sites that did use the previous default options.

I would have definitely saved the “theme options” as there are settings in it that are not the default settings when starting a site so my presumption is there is an issue with the upgrade.

In terms of point 3. This was the same upgraded site. If I hovered over the element it showed it had breakpoints applied but I couldn’t horizontal scroll to the customize section. I ended up deleting the element and creating a new one. I’m happy to transfer the Pro 5.1.5 version of the site to another subdomain and see if the upgrade has then same issues again. Then I can give you access if you like.

Just let me know.

[urchindesign]

I can confirm that I restored this site to a new sub domain and ran the upgrade from Pro 5.1.5 to Pro 6 Beta 2 and have experienced the same issues.

I’ve added login details to the secure notes for you.

[kory]

@urchindesign, we have put in a migration script that should mitigate the issues you experienced in #1 with the Theme Option changing. Can you confirm for #2 that a page template actually changed (i.e. under the Outline Settings on a page going from “default” to something else, et cetera)? If so, can you point me to a page that was another template and is now a new template? Again, not the Theme Option change, but the page template changing. I have tested this and am not seeming to run into any issues with my test install locally. For #3, I can confirm that you seem to have your hide during breakpoints options applied to your off canvas toggle, but they aren’t output on the frontend. Your other Elements seem to be working appropriately, though. I tested a migration locally with an off canvas Element and my hide during breakpoints classes are moving over as I would expect, so not sure what’s going on here yet.

[urchindesign]

Sorry this site has zero pages. It is literally just a blog.

Perhaps a mistake on my part in my description of what is happening.

It is just the archive pages and single post pages that have lost the side bar.

I have run the upgrade on the site twice with the same results. You can get the Updraft back up of the site before I ran the update to Pro 6 in Updraft Plus if you want to test the upgrades yourself.

[kory]

@urchindesign, no worries. Then #1 should be solved by the fix I mentioned above. This won’t be available until Beta 3 though, so once that is out we can test it. As of right now, the breakpoint classes not being applied to that one off canvas Element are the main thing I’m looking into here. Thanks!

[urchindesign]

I can confirm that the upgrade from Pro5.1.5 to Pro 6 Beta 3 worked on this site in terms of #1.

I can also confirm that the mobile break points are still a problem on the off canvas.

[kory]

@urchindesign, glad to hear #1 was fixed. I will have to look more deeply into what is going on with your situation, as I haven’t seen any other users reporting missing breakpoints and I cannot replicate this on my own with any Elements (including Off Canvas). This is noted and will be looked into.

[urchindesign]

I can confirm upgrading this site from Pro 5.1.5 to Pro 6 Beta 4 still has the same issue.

This is probably the simplest site I have ever built which is a bit of a concern. It is literally a header, footer and the blog using the default blog from the stack. I’ve done nothing special with the site and it was literally a quick companion blog to a custom site we built for a recruitment company.

I’m happy for you to take a backup of the site or I can even make a backup and give it to you if it will help.

[kory]

@urchindesign, when you say the same issue, you’re referring to the breakpoints not migrating only on your Off Canvas Element, correct? Also, when did you build this site originally? Was it quite a while ago?

I ask all of this only because I have tested numerous upgrades locally using all sorts of variations of these Elements (along with all sorts of other Elements in our Library) and I cannot replicate an issue of breakpoints not migrating upon upgrade. However, I do know that a while back we fixed some things with regards to how the breakpoints were being stored, so this might simply be a regression where you’re going to need to go in and re-apply your breakpoints and save, and moving forward it should always be fine as you continue to upgrade. To do this, just go into your Element and uncheck everything and re-select the breakpoints you wish for it to hide on again.

Let me know if that works, thanks.

[urchindesign]

It is an older site, but not that old. Can’t be 100% certain when we made it. It is one of our long term custom / system build clients who we’ve had for about 8 years, possibly more.

[kory]

@urchindesign, you say it’s not that old, but the client has been with you for 8 years…had you built the site on X initially and upgraded to Pro at some point? Either way, the fact that breakpoints are migrating everywhere else, and I can’t seem to replicate this even when migrating sites locally seems to indicate to me this might be something that just got “off” somehow at some point in working with the site. I haven’t heard of this issue from anyone else in the beta at this time it seems, so I’m not saying it isn’t happening, but it does seem to be unique to this build in particular. If you uncheck the breakpoints and reapply them as I mentioned, I assume everything works correctly for you?

[urchindesign]

Honestly I’m not sure when it was built. We’ve had the client about 8 years but my guess is sometime in the last 3.

Time flies though so not sure. I’ll double check the date of the first article when I’m back in the office on Monday

[kory]

No worries, and also try resetting the breakpoints as mentioned above, because that may simply be the fix in this case.