Big Bug in Elements

Hi Karsten,

Any chance you can create a staging site and share the admin login with us?

Hi Ying,

I have added credentials so you can check this issue.

We would need the login URL as well.

added

Login URl is added

That doesn't look like the test site.

Can you provide the login to a staging site with all plugins disabled?

Thanks.

Please check access to staging. Plugins are deactivated. Issue still exists.

Thank you

Can you try setting a value here and remove the exclusion for now?
https://www.screencast.com/t/S5Luaqj6ni

Hey Leo, I don't know what you mean, and also the screenshot does not help me to understand.

I gave you access to the staging, so please do the necessary changes in order to fix this issue.

Thank you

Hi there,

so that element has somehow 'lost' its exclusion rules except the first one. It may be because the install could not handl the large number of exclusion rules and they got corrupted.
All i could do was to delete the empty exclusion rules, and set the the Location to Posts > All Posts.

I assume you want that to remove that Page Hero if there is another page hero present.

What i have done as a suggestion:

1. The Page Hero Einfach:
1.1 I have set the Display Rules Location to Posts > All Posts
1.2 I have removed ALL the exclusions
1.2 I have set the Page Hero > Priority to 25 ( This will make it load after any other page hero )
1.3 The GB Container Block i have given an Advacned > Additional CSS Class of: fallback-page-hero

2. I went to an Example post that has a specific hero eg.

https://yourwebsite.de/aktienfinder/

Where i can see both Page Heros.

2.1 I added this CSS in Customizer > Additional CSS:

.gb-container + .fallback-page-hero {
	display: none;
}

This will automatically hide the Page Hero Einfach if there is another Page Hero above it.

This means you don't need to set Display Rule > Exclusions on the Page Hero Einfach. as the CSS will do it for you. Is that a working solution?

Hello David,

thank you very much for this working solution, which helps to fix this issue.

But I think in the long run we need another solution, because display:none; is not really optimal code for this kind of bug.

Are you planing to fix this issue in one of the next theme updates?

This would really be great.

Please let me know what you think. Thank you.

Best,

Karsten

These kind of issues are very complicated to debug, as we have only ever seen a handful of these issues and we have been unable to replicate them. It could be specific to the server set up or related to a mix of plugins. We are however reviewing the Display Rules system which hopefully should eliminate issues when listing large amounts of display locations/exclusions on a single element.

What i do in these instances is to create a Custom Taxonomy for my Posts and Pages, and that the purpose of that taxonomy is purely to set Element Display Rules.

See here for a PHP Snippet on how to do that:

https://generatepress.com/forums/topic/reducing-the-number-of-element-headers/#post-1942770

This way you can create an Element Control Taxonomy Term eg. Remove Default Hero and then you can edit your main Page Hero, and set its Exclusions to Post Category -> Remove Default Hero
Then whenever you create a Post that has a unique hero you can assign that taxonomy term