Bug/Issue with "Global Footer jumps to top" right below the Header
Hi Brizy Team
I'd like to report a bug which I encounter on following Brizy Cloud site: www.samo.press
Out of nowhere it happens that the global Footer gets moved right beneath the Header even though I didn't do that. Now I had to change it back to the footer eg. bottom for multiple pages multiple times, but after some time it happens again even though I saved the adjustments - obviously.
I can't tell you when exactly this happens. But after some investigation I realised a pattern (I think). It seems like that global Footer tends to "jump" back up to the top (below the Header) on Pages, but not on Posts and Categories or any custom single/archive assets after I adjusted the Footer back to normal.
- Page(s)
https://www.samo.press/en-wordpress-themes
https://www.samo.press/en-wordpress-plugins - Custom Single/Archive
https://www.samo.press/en-page-builder-wp-plugins
https://www.samo.press/en-brizy-plugin
Seems like a weird bug, however I'm not sure! May I ask you if you are aware of that "global Footer jumps to top" issue? Is there a workaround?
Looking forward to hear from you.
Francis
-
Hi Francis,
Thank you for all these details. I informed our developers about this problem and they will investigate it. When we will receive some details about this problem, we will immediately inform you too! I'm sorry for this inconvenience!
Best regards,
Sandra0 -
Hi,
Our developers found that the header and footer were removed from the homepage but on the pages, you reported, we couldn't reproduce the problem. Could you please check this or help us to reproduce it?
Thanks!
Best regards,
Sandra1 -
I can report that I have the same problem and it recurs frequently. Is there any resolution?
0 -
Hello!
Can you please add your website URL, so we can check it?
Add some screenshots too, please.
Kind regards,
Mihail
0 -
Sure, it is reoccurs every week when a post is added.
1 -
Hi
I meanwhile have implemented a workaround (Code Snippet) as the Brizy Team couldn't yet figure out how to solve it internally. My workaround is by no means perfect and only serves as a temporary workaround solution. In my opinion the actual issue can only get properly fixed by the Brizy Team as it seems to be a Brizy Core related Bug. 🤔
Workaround
You may find my workaround (Code Snippet) here: https://bit.ly/3ANjDS0
- Visit the URL to the Code Snippet
- Copy the HTML Code Snippet to your Clipboard
- Visit your Brizy Cloud Site and navigate to "Code Injection"
- Paste the HTML Code Snippet from your Clipboard to "Code Injection > Footer" & save it
- Open any page in the Backend & save it (I guess to clear the Cache or it's another Bug... 🤷♂️)
- Open any page in the Frontend where the issue previously appeared to see the workaround in action
Hope the Code Snippet will help everyone who has the same problem with Brizy Cloud and can't wait to have the Brizy Team fix it properly on their side. Of course, once they've solved it on their side, you can simply remove my workaround code snippet. ✔
Cheers,
FrancisPS
@BrizyTeam 🙈 When submitting my Bug Report I wasn't expecting to submit this publicly! Can you maybe have (at least) a checkbox where we have the choice to publicly share our Support Ticket or in this case Bug Report?! I mean it's OK for this Ticket, but I'd really appreciate to know if I'm writing a personal support ticket or a public forum ticket. Hope you know what I mean and can improve on that? 🙏
0 -
Hello Francis,
Thank you very much for your message!
Regarding what you said, we appreciate the fact that you shared this workaround with us. We hope it will be useful to other users as well. Now about making the ticket publicly - the tickets first of all arrive to us and we are the one who make it publicly. At the request of the user we may delete some information or create a private ticket. Next time, if you would like some things to not be posted, tell us!
Hope this made things clear! Have a nice day and best regards,
Doina
0
Please sign in to leave a comment.
Comments
7 comments