4.2 compatibility?

Where are we with 4.2 compatibility? Is 1.7 compatible, despite the Visual Composer version?

Yup. You can always download the theme files and check the changelog, too, as it will normally state stuff like that, such as XSS security patch to coincide with all the industry fixes (new WP 4.2.2 update today!). 🙂

In which case 1.7 isn’t compatible, glad I checked.

Going to take a little while to roll all of our 1.7 tweaks into 1.7.1

Well….. to be clear, 1.7 works with 4.2
— 1.6 works with WP 4.2.2, so 1.7 “should” …

I would skip 1.7 and go right to 1.71B (current file on ThemeForest).

• This reply was modified 11 years by simchris.

We’re at 1.7 currently, under 4.1.4.

The changelog lists 4.2 compatibility as being part of 1.7.1, I’m going to look at merging our changes in over rushing the upgrade.

And of course you should already be running 4.2.2 due to all the XSS security patches done in 4.2, and 4.2.1 and the XSS in the icons in twenty-fifteen theme (which you can actually just delete vs upgrading to 4.2.2 if mood strikes… )

Anyway…. shutting up now 😉

Wasn’t that the point of 4.1.3 and 4.1.4?

Only the latest issue hasn’t had a point release for 4.1.x and our host (WPEngine) is doing something application-level for customers to safeguard for the time being.

Correction, 4.1.5 is now being pushed with the same fix as 4.2.2.