The Contact Button in the navigation bar on my new website keeps disappearing when I refresh the page…
Can anyone help me fix that?
David
The Contact Button in the navigation bar on my new website keeps disappearing when I refresh the page…
Can anyone help me fix that?
David
the button is there still but seems to become invisible…my mouse pointer changes as I run over the blanks space…..weird
Something strange is going on there, I’m wondering if it’s the custom banner causing issues Does the menu work without the banner on the page?
Can you share your project via Elements Cloud so we can take a closer look for you?
Hi Dan,
I don’t think it is the custom banner (btw, thanks again for your input in helping me create that), as I have removed the banner entirely on the History page and the Contact button still disappears if the page is refreshed.
Have a look at the project I have just uploaded and let me know what you find…
elementsapp://downloadDocument/Iy1sxZAF93qN
Hmmm, I’m having trouble re-creating the issue in the local project.
Can you re-create the issue locally in that project? If so, what are the exact steps?
I have just built the site again from scratch here…
and the button behaviour is still weird.
What’s going on?
Very strange. I hope you can suggest a solution.
Btw, you noticed that my menu was not set as a Global and that’s because I am the guy having problems on my Mac where the Globals become corrupted and bring in loads of broken components. I’m hoping you can fix that soon and I can start using Globals again.
it disappears for me as well, when I open your link and refresh
it also does this
Yes… seems to have a mind of it’s own!
The logo on the left changes to a blue dot and black dot acting strange like the button when in mobile
So it seems I have managed to fix this!
I replaced the Contact button with a new one and that has done the job. Not sure what was wrong with the old button but this new one doesn’t disappear when I navigate to the other pages.
Maybe @dan can have a look at the old button and see if there was something janky about the code behind that which was causing the issue?