CB

Well, the only and very easy way to "fix" that is to leave a dummy column called "access" in that table until CB 2.1 ?

Think that would not be an issue. Thoughts ?

I don't think that's in line with our deprecation of the other old access columns. I'm in favor of just leaving it as is. It's a non-breaking notice that most won't even see if their debugging or error reporting is off (most likely scenario).

I was thinking to keep viewaccesslevel column in line with other tables, but to add a new dummy access column temporarily here.

Nothing major either way.

Thoughts?

Right, but I don't think it's necessary for the sake of a minor notice in a few plugins custom backends. It also only applies to upgrades and all will be fixed shortly after we go stable. Since it's non-breaking I think we're ok to just leave as is.

I'm not too keen on the idea of dummy DB columns. If we can get magic getter and setter working ok though that'd also solve it, but last time I tested those there were issues with it.

Ok, if this is backend only and notices only, and we fix this in groupjive, think we can live with it.

Leving this now Assigned to Kyle, so that he can close this when it is fixed in all CB plugins that access the access column.

All plugins using ->access now fixed to use ->viewaccesslevel. Note was only for display purposes in their custom backends.