-
Notifications
You must be signed in to change notification settings - Fork 3
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
Error 800 when restoring a template to a course with ":" in its name #21
Comments
Hi! Thanks for reporting and glad you like it 👍 Best |
Sorry but I think it's actually a different issue. Is there a limit to the course name within your code? It's possible that when I removed the colon it went under the limit... I say that because it just happened now with another course that has no symbol in the name. The original shortname of this course had 57 chars. Can that be changed? |
Thanks for the additional information. We'll have a look and get back to you. Best |
Hi! We've discussed this internally and think the reason is probably something different. Would you be able to provide a .mbz backup file which does not work on your site for us to test? Thanks! |
Sure! I attached a zip that contains two .mbz files, both had issues and were fixed as I described before. Keep in mind that some of the content there is in Hebrew :) And again, this happened maybe 2-3 times out of 100-200 courses so far, and those courses had long names (in Hebrew) and one had the colon. Thanks! |
Hi,
We're using your plugin (free version) and it works great so far.
There's a bug we encountered lately where an error is shown if a template is restored in a course with a colon (:) in its name.
When I removed the colon from the course and and tried again, it worked.
The error says:
"Restore failed with status: 800
Error reading from database"
(paraphrasing a bit, our Moodle isn't in English)
Does it mess the plugin's code somehow?
Would other symbols cause similar issues? ("/", "'" etc)
We're on Moodle 3.9.
Is it something you could fix?
Thanks!
The text was updated successfully, but these errors were encountered: