Beta 1 - Header assignments not ported to the new conditions?

Beta
#1

I’m playing around with a site originally built on the previous release, and a header I had assigned to specific pages still displays fine on those pages… but when I go into the Header view, it shows all the headers as Unassigned.

image

And if I go into the conditions within that header, there aren’t any assigned.

image

Are you guys planning on porting the previous assignments to the new conditions? Or just continuing to support them until a user goes in and explicitly sets new conditions?

Overall, I think a lot of people upgrading to V4 are going to be pretty confused about the new way of assigning headers (unless there’s a an alert or guide telling them what to do).

1 Like
#2

Actually, I guess something’s not working right here. (Or you guys are still working on this?)

In my above scenario, I had that How To header applied to a How To CPT (made with Pods). Visiting the site, I still see the How To header on any of those How To pages I built.

Now, I just went in to the Header and set the conditions to only display on the Front Page. Which it now does.

image

However, it still appears on the How To pages as well. And I can see now way of removing that old assignment.

#3

Hey Devin, I’m really sorry about that. I can see what’s going on. I can’t get it fixed for the patch going out today but will definitely get that addressed.

There is technically a new assignment system overlaid with the old one and it was meant to work seamlessly. I must have broken that somewhere along the way.

To get it fixed on your site for now, you can do is delete cornerstone_header_assignments from your wp_options table and that will make the site forget all the assignments from previous versions of Pro. Otherwise, wait until the next patch (not the one coming today) and just save the header again.

#4

No worries, I’m in no rush. It’s just a test instance I was messing with. Thanks!

#5

Sounds good!

#6

Update: Fixed for next patch.

1 Like