Hey there,
I’m not sure what you mean by the ID the CSS is scoped to means, can you please elaborate?
None of the CSS selectors have changed since the release of Version 3 which was released about 18 months ago.
Can you please provide steps to recreate your issue or clarify what you mean above so I can advise?
All the best
Peter
Thread Starter
iioeo
(@iioeo)
That is coming from my dev that put the menu in place. In April, when we noticed this issue before, he looked into and and said: “I put in a script that looks for the old ID and changes it to the new one their CSS is scoped to”. Is it possible we didn’t update the plugin when you released the change and once the plugin was updated on our end, it broke? I would have to look back to see when the plugin was originally added to the site.
Sorry for being so vague, but thanks for the help! I wish I knew more about the code, but I do design 🙂
Hey there,
I think I am struggling to understand what “CSS scoped to” means in this context which is why I am confused as to what the issue is.
It looks to me from looking at your code that something has changed the ID of my menu from responsive-menu to menu-main-1. If you change that back then everything will work for you.
I can only guess this is what your dev means by CSS scoping, and if so then yes he needs to change every instance of #responsive-menu in my CSS to #menu-main-1 or to update the ID in your code or in your CSS in the opposite direction.
Please let me know if this is what you mean.
Peter
Thread Starter
iioeo
(@iioeo)
Thank you- so it SHOULD be responsive-menu?
Hey there,
That is correct, responsive-menu is the correct ID for the menu.
Peter
