Support » Plugin: footnotes » Class ‘collapsed’ conflict

  • Resolved markyz89



    I had to disable the footnotes plugin today due to a conflict with our mobile nav menu on the class named ‘collapsed’. The rule to display none is coming from the footnotes plugin, which we disabled yesterday.

    Any chance you could make your style rules a bit more specific with something like #footnotes .collapsed to avoid such clashes? Collapsed is a fairly common thing for developers to include as a classname.

    Fortunately the collapsed class in our menu doesn’t seem to do anything (I didn’t build this site) so it appears that this will be pretty easy to solve, but I imagine it could cause bigger problems for other websites.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Rumperuu


    Hi @markyz89,

    Thanks for getting in touch. This is a known issue, and a fix is included in the upcoming 2.7.1 release, which is currently in testing and is expected to be out by the end of the week. You can download a pre-release version from here if you would like — select the ‘Development Version’ option in the drop-down.

    We are also in the midst of a wider review and refactor of the Plugin codebase as a whole (including stylesheets), so hopefully these sorts of issues will soon be a thing of the past!

    Plugin Contributor pewgeuges



    I apologize for this mistake, that I released one month ago. It caused an even worse issue reported 8 days ago, then found and fixed 6 days ago as reported. When I dropped in six months ago to propose a bunch of bug fixes, I was allowed to fix even more bugs, add missing settings and features, and release the fixes timely in the wake. But in the process I caused other bugs and issues, all fixed AFAIK with timely released bugfix versions. Sadly when releasing urgent 2.7.0, this one was 21 hours late.

    Thanks for your good advice!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Class ‘collapsed’ conflict’ is closed to new replies.