Upgrading from 7.x-3.0 to 7.x-3.8 breaks portions of my sub theme.
Changed files or folders in the bootstrap theme update were these:
includes/common.inc
templates/block/block.vars.php
templates/bootstrap/
templates/menu/
templates/system/
...and none of those were in my sub theme, thus I figured I did not need to change anything in my sub theme. So no files changed in sub theme.
Inspecting versus pre-upgrade I see actual html changes.
If any ideas, would appreciate. Did many cache flushes, etc.
Thanks,
Rick

Comments

Rick Hood created an issue. See original summary.

markhalliwell’s picture

Status: Active » Closed (works as designed)

You really can't just say something "breaks" without actually giving an adequate description or even steps to reproduce what is actually breaking.

---

That being said, if you're really upgrading from the 7.x-3.0 release, then that is honestly just expected. That's nearly 4 year old code.

As with any update, you really should read the release notes for the version(s) you are updating to. Just so you know what code is being touched (which in this case is everything). This includes reading all prior versions you're lumping into this single "update".

For instance, the 7.x-3.1 release contained changes that were simply unavoidable (due to several factors, but mostly stagnated releases) and is very well documented.

Most releases after that have been relatively less invasive and less painful.

---

As a side note: simply upgrading to 7.x-3.8 (which I'm assuming is because its a security release) isn't far enough IMO.

The current release (as of now) is 7.x-3.14.

I'd strongly recommend upgrading to the latest release and try to stay on top of it so you don't run into this exact issue again.