You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the "merge header" in GeneratePress and/or OceanWP theme, it's not possible to grab the edit section and edit the upper section ( because it is laying under the header ). One always needs to disable the merge header first, then edit, and then check the merge header again, which is very frustrating and time consuming.
Now, even that workaround does no longer fix this bug.
I started using Generate Press and OceanWP as they are recommended and are supposed to work seamlessly with Elementor. Please fix this bug and or provide a workaround that still works. Apart from this, love Elementor!!!
Thanks!
Annie
The text was updated successfully, but these errors were encountered:
Ofcourse it would be better is this was fixed within Elementor, so it can work seamlesly with these ( Elementor compatible ) themes, without the need of tweaks in the themes itself?
When using the "merge header" in GeneratePress and/or OceanWP theme, it's not possible to grab the edit section and edit the upper section ( because it is laying under the header ). One always needs to disable the merge header first, then edit, and then check the merge header again, which is very frustrating and time consuming.
This is a known issue please look here:
https://generatepress.com/forums/topic/transparent-header-for-all-pages/#post-366748)
and here:
https://generatepress.com/forums/topic/cant-reach-the-section-and-paragraph-buttons-on-an-elementor-section/
Until the recent Elementor update, this css workaround worked:
Now, even that workaround does no longer fix this bug.
I started using Generate Press and OceanWP as they are recommended and are supposed to work seamlessly with Elementor. Please fix this bug and or provide a workaround that still works. Apart from this, love Elementor!!!
Thanks!
Annie
The text was updated successfully, but these errors were encountered: