Hi there.

We are running 7.3.1-beta1 on quite a few of our websites and I was wondering if anyone knows if the latest update applies to the a version this old.

We would pretty much have to re-theme each site to upgrade it to the latest version, and since they are so different I am wondering if there is a way I can patch my version to make it secure.

Please if anyone can help in any way that would be awesome.

Thank you in advance

Comments

capfive created an issue. See original summary.

markhalliwell’s picture

markhalliwell
Primary language English
CreditAttribution: markhalliwell at Tag1 Consulting commented
Status: Active » Closed (works as designed)

Unfortunately, no there is not a special security patch for the 7.x-3.1-beta1 release. The reason that release is "so different", as you put it, is because it included a "feature" that completely changed the landscape for how the page and region theme hooks operated in the base theme.

Given that there is only 44 reported installs still using this release, I'm not very inclined to create a special security patch regarding this release. Instead, I'd recommend upgrading to the latest release/dev version and then apply the patch I just rerolled that adds this feature back: #2128129-30: Provide setting to change sidebar/content widths.

Ultimately, you really should upgrade your themes so you don't have to apply this patch anymore. That feature isn't going to be added to the 7.x-3.x branch.

So that issue will likely become stale, again, and someone will have to reroll it against the latest dev again (this will be the last time I do since I'd like to move on from that mistake).

Anyway, hope this helps.

capfive’s picture

capfive CreditAttribution: capfive commented

I really appreciate the fast response!

So what you are saying is I should be able to upgrade and roll that patch which will minimise the issues faced in a total re-theme?

markhalliwell’s picture

markhalliwell
Primary language English
CreditAttribution: markhalliwell at Tag1 Consulting commented

It will allow you to "upgrade + patch".

When you say "re-theme", I'm not sure it's that big of a task. It's more likely just a matter of re-organizing some templates (everything in "regions" back to "page") and any custom preprocessing logic to reflect the current release's support "layout".

There may be a few places you will have to rethink how some of the logic is done, but it wouldn't be a complete "re-theme".

Otherwise, you will have to "upgrade + patch" each time a release comes out and you run the risk of said patch becoming stale and no longer applying. So you (or someone else) will have to stay on top of that patch and make sure it stays current (if that's the route you decide to go).

capfive’s picture

capfive CreditAttribution: capfive commented

Mate, can't thank you enough!

This will save loads of time.

Awesome work!

markhalliwell’s picture

markhalliwell
Primary language English
CreditAttribution: markhalliwell at Tag1 Consulting commented

You're quite welcome. Just glad to help :D

capfive’s picture

capfive CreditAttribution: capfive commented
Title: Latest security update » Upgrading from 7.x-3.1-beta1 to 7.x-3.8

Well what an experience!

For anyone wondering what you need to do to successfully complete this task...

It is not easy. ALOT of functions are printed in the tpl's which don't exist anymore. Things like the primary and secondary menu have changed locations and are now in the page.tpl

My advice to others is that it can be done, but sometimes might not be worth it.

Best of luck to any who attempt and thanks again for the help Drupal community :)

If anyone needs a detailed breakdown please let me know