Closed elinara closed 5 years ago
Solved by #119
@athird, @msbachler, from #116 it seems that the issue is blocking some users. Shall we make quick test of merged changes and deploy the latest version to all instances?
@ivanoterouvigo, are your teachers using the production instance?
Yes, I began to work with them in production instance. But we are at the beginning. I would like to give them the oportunity of create content in hide mode. But teacher role didn't let them to work like this
OK. @athird, @msbachler, shall we schedule deployment to the pedagogy and then production instances?
@michzimny Yes, we should. We've made quite a few fixes recently; we should batch at least some of them together for a deployment. And also any other pressing ones we need to have sorted out before we deploy (that we could do very quickly). When do you think would be best? Do we, e.g., need to have a call to go through them and schedule the deployment?
If we could do this outside of working hours and book some additional time to solve things if anything occurs after deployment, then any day is fine. If not, then I need to check with pilot countries as some activities with teachers are ongoing.
I'm afraid I will not find enough time till the end of the month to participate in the technical side.
@athird, however, in case of blockers as #116, I think we need to fix them ASAP. Either by deployment or a manual fix.
@athird, @msbachler, this issue is blocking users. Could we schedule deployments of the fix?
I think it could be done at any time, if before 7th January. Otherwise, we need to agree on a proper time.
@michzimny I've manually set the right configurations on production and pedagogy; I didn't want to risk stability by redeploying possibly other new stuff at the same time. Same for #82 and #93.
The setting showonlycustomactivities must be disabled because otherwise the non administrative user can not create a new activity.