Apologies for the slow response, we are having a busy spell in support.
Please allow me a little time to read through the details of the issue and familiarise myself with your site, and I'll get back to you in a little while.
OK, I'm aware this is a production server. Do you have a staging server available that I could do some debugging and testing on (which may involve adding utility plugins, de-activating and re-activating plugins, etc.)?
If not, given that several days have passed, can you at least confirm that you now have an up-to-date backup of your production server. I don't want to log in and do anything until I know that you are covered.
Yes current issue is on production. We tested on staging but did not go this deep into testing there, focus was on stability and performance which turned out to be OK.
Ee decided to build the translations one by one on production using the hide languages function and using the "show hidden languages" feature for test users aka proof readers.
Techtalk
daily scheduled backup production server
staging on separate server with own resources. you can play around whatever you need there. We use github to secure consistent coding and security.
Update: yesterday I received response from learndash about the issue. I think that could be helpful too. I think your colleague forwarded you the response already
The consensus appears to be that the workaround suggested by Learndash is a promising one:
>You can change the default behavior through a workaround that uses the Groups feature. This will involve adding all translated versions of a Course to a Group and granting users access to that Group. A user who is granted access to a Group will automatically gain access to all its associated Courses. Our support guides linked here have more details on the Groups feature: hidden link
The discussion is public—the forum contains a wealth of information for clients researching topics that have been raised before—but we have certain measures in place for privacy.
The original chat conversation is private: I can see it but other users cannot.
In the subsequent thread any links that are shared with us are automatically hidden from other users.
If we need some sensitive information from you—such as site credentials—I can set up a private reply for you to share those.
And when we complete the discussion, if you want I can go back and
I can do that now, for your next reply, but note that I have to choose a template for your reply (e.g. one to share website and FTP credentials), and you must provide values in the template otherwise the freeform text you write may not be private.
So let me use the template for sharing a Duplicator package of your site. You should be able to put some dummy URL in there, and then write your response.
