I have tried this scenario only once.
I see that content now has been finalized for 3.11.3 and already in testing phase. We can take this bug in for the next release which is ocs 3.11.4.
(In reply to RamaKasturi from comment #16)
> Hello Yaniv,
> I see that content now has been finalized for 3.11.3 and already in
> testing phase. We can take this bug in for the next release which is ocs
Makes little sense to me - perhaps I'm missing something. This is just a tracker - the relevant BZ has been fixed, verified and released. I'm not sure why this cannot be part of the regular testing of 3.11.3.
Perhaps I'm missing something.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.