-
Notifications
You must be signed in to change notification settings - Fork 13
Limitations and Bugs
merrill-oakland edited this page Feb 6, 2016
·
7 revisions
- Backup and restore does not work.
- New WebEx users are created for users (assuming no email address collision) who create or host a meeting. On sites with a limited number of user slots, this may cause two accounts for one effective user.
- When a Moodle user is used to create or host a meeting, a new WebEx user is created for them, with the prefix setting prepended to the username. If the email address is already taken, the user will be redirected to a field to enter their WebEx password. A workaround for this is to change the users existing email address in WebEx from something like user1@example.com to user1+webex@example.com. Everything between the + and the @ is ignored by email systems.
- Only Meeting Center and Training Center are currently supported.
- When a recording name is updated in Moodle, the information is sent to WebEx, but the name will not reflect the change in the WebEx user interface. This is a bug in WebEx.
- If you host one meeting type (like Meeting Center), and then go to try and host a meeting of a different type (Training Center) you may get an error. Workaround: Go to the WebEx site and click "Log out". Then try again.
- User WebEx passwords are stored in the database. This is because WebEx doesn't provide a way or retrieving a token for authentication - we must send the password with each request.