Report a bug with Header builder - by Marta Iraola

This topic has 34 replies, 3 voices, and was last updated 5 years, 8 months ago ago by Olga Barlow

  • Avatar: Marta Iraola
    Marta Iraola
    Participant
    March 26, 2020 at 18:06

    Hello Olga,

    1 – Totally understood! I did see that this feature is in beta, so I guess it is normal to see bugs… Thank you for taking the time to investigate and solve them!

    2 – In my case, the warning appears each time I try to close the tab of the header builder. Even if I don’t change anything and try to close it, the message appears. And if I have done some change and saved it correctly, the message appears too. I use Chrome browser if it helps. This is not my screenshot but the message is identical: https://i.stack.imgur.com/x5blG.png

    When it appears I simply close it and the tab too, then I check the page where that header appears and I see that the change was correctly done so I don’t know why it appears.

    Thank you!

    Avatar: Olga Barlow
    Olga Barlow
    Participant
    March 30, 2020 at 10:14

    Hello,

    Save the headers and publish changes https://gyazo.com/439ebec7fba85983a23d5263964239ad then you won’t get any messages. Some changes could be saved automatically because we use Ajax but some – not, so to be safe it would better save header and publish changes.

    Regards

    Avatar: Marta Iraola
    Marta Iraola
    Participant
    March 31, 2020 at 17:10

    Olga,

    OK! I didn’t know you had to click Publish too. I thought that you just had to click on “Save”.

    I tried it now and it doesn’t show any message.

    Thank you for all your help! I think we finally can close the ticket haha

    Have a nice day.

    Kind regards,

    Marta

    Avatar: Olga Barlow
    Olga Barlow
    Participant
    March 31, 2020 at 19:33

    Hello,

    You are welcome!

    Regards

  • 1 2
    Viewing 34 results - 31 through 34 (of 34 total)

The issue related to '‘Report a bug with Header builder’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.