Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the googlemeet_records table is being written with duplicated registers but with different googlemeetid #33

Open
Arvaloez opened this issue Aug 23, 2023 · 1 comment

Comments

@Arvaloez
Copy link

Hello Rone,
As the title says, When the sync process finishes, the records report shows all the records of that room but also records from other rooms. I was checking the problem and I found that the googlemeet_records table has duplicated records but with different googlemeetid. In the attached image, there is a capture of that table with two duplicated records but with different googlemeetid (the second column).

Screenshot 2023-08-23 at 8 30 49 AM

@ronefel
Copy link
Owner

ronefel commented Oct 30, 2023

Hello Alexandre, sorry for the delay in responding to you, I have other projects and I am not able to give the necessary attention to this project.

This problem occurs when backing up and restoring the course or copying the activity, is that what you did?

The ideal is to create a new room with a different code than Google Meet, so as not to pull recordings from the other course.

And indeed, as you instructed, the $name parameter must be the value of $googlemeet->originalname.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants