[SOLVED] Joomla 3.4.8 warning - enquiry

So this morning I get a couple of enquiries from users having issues, one cant view stuff he should be able to ( given his subscription) and another is constantly failing password update. Maybe no relation to 3.4.7 update - impossible to tell with all the variables of device, OS, browser. Waiting for more info from these users.

However, Joomla 3.4.8 just came in - something about "session" bugfixes for the 3.4.7 patch.
I applied it to my DEV server, and found it completely wrecks SOMETHING.
Logged in to DEV with a test user for Paid subscription, and they have no access to the material they should be able to see. It was working fine for them on DEV in 3.4.7

Needless to say I am going to hold off on applying 3.4.8 to our LIVE server.

Any ideas whats up with that???

No issues here beyond session being trashed on update. You should've been logged out after installing 3.4.8 then subsequent login will be fine. I do not recommend holding off on updating. If you've any issues throughout your site with 3.4.8 then please report them to Joomla or post directly on Joomlas forums. Your issue could have nothing to do with Joomla though and just be an issue with your CBSubs configuration.

What sort of CBsubs config issue could suddenly cause that? (I have not made any CBsubs config changes).

I just brought in a recent backup of LIVE server and applied it to our DEV. The backup was a 3.4.6 and upgrading to 3.4.8 creates no issues.

However, the previous test of 3.4.7 to 3.4.8 on our DEV did indeed totally ruin access for Paid users (and it was working fine on DEV after the 3.4.7 was applied there - just as it works fine now, on our live server currently running 3.4.7)

Definitively, really killed it - no amount of logging in or out or clearing caches made any difference.

I suppose you had tested your environment upgrading 3.4.7 to 3.4.8?? Or did you happen to do 3.4.6 to 3.4.8, like I just did successfully here on our DEV server now?

Still pretty nervous about this - with thousands of live paying users, the last thing I need is broken CBSubs access permissions. I'm going to try again on our DEV with a 3.4.7 cloned from the current live server - just to be on the safe side!

What sort of CBsubs config issue could suddenly cause that? (I have not made any CBsubs config changes).

Suddenly, none. You'd of had to of manually configured CBSubs to block the entire CB component.

I suppose you had tested your environment upgrading 3.4.7 to 3.4.8?? Or did you happen to do 3.4.6 to 3.4.8, like I just did successfully here on our DEV server now?

3.4.7 to 3.4.8 is tested internally as working fine.

I recommend upgrading a clone and if the clone has issues you'll be able to safely debug what's going on as something else is happening in your install. CB has no control over the session data and is entirely handled by Joomla. Especially in backend. Worse case for backend is CBSubs protects a backend view, but that won't affect login or anything of the sort.

Well, after bringing in a fresh 3.4.7 clone to our DEV server, the 3.4.8 patch took this time with no ill effects. NO IDEA why 3.4.7->3.4.8 mangled things the first time.

I do read there is a lot of glitchiness/controversy over these last couple of patches ( see issues.joomla.org/tracker/joomla-cms/8823 ) so it looks like I had better call a maintenance window and log all users out before doing the 3.4.8 upgrade on our live server.

It would be nice if Joomla would ADVISE about these sort of details before just throwing out a "go ahead and upgrade" notice! (But that's a topic for the JOOMLA forum...)

Thanks again for your advice!