Microsoft 365 Integration
Premium Certified Partner
Maintained by
Enovation Dev Team, Lai Wei, Patryk Mroczko
This plugin provides libraries and services that power other Microsoft 365 plugins.
Comments
Comments are no longer open for new posts. Existing comments remain available to read.
Fatal error: Can't use function return value in write context in /var/www/lms.alte-kanti-aarau.ch/moodle/local/msaccount/classes/client.php on line 62, if I like to open a module with texteditor.
If I set the permission on msaccount directory to 0000 the texteditor works well. I migth be, that at the first installation month ago something didn't go well.
What can I do?
- deinstalling: not all plugins have an uninstall link.
- updating to moodle 3.0.1
Is this a solution?
I was getting this error while trying to do this in php:
1
if empty($userSession = $this->Session->read('User')) { //do something; }
The solution to get over this is to define a variable before actually testing for its value, as such.
1
$userSession = $this->Session->read('User');
2
if empty($userSession) { // do something; }
As a rule of thumb, the php function empty cannot check the return value of a function or method. It can only check variables.
Thanks for your help.
Jürg
<< behavior observed>> when clicking the "Moodle" icon from Office 365 after the plug-in install, the login to Moodle wasn't successful, and the web-browser page kept oscillating back and forth.
<< Error meg. >> The reply address ‘http://poc-elearning. /auth/oidc/’ does not match the reply address ‘http://poc-elearning. /auth/oidc’ provided when requesting authorization code. There is a difference of “/” character in the two URLs.
<< Action Taken >> used fiddler to temper and inject the “/” in the url being send to Moodle by Office 365. Also in the App registration changed the URI to include the “/”.
<> same no change in behavior observed.
<> can anyone guide us to resolve this issue ?
Debug info:
Error code: errorucpinvalidaction
Stack trace: •line 54 of \auth\oidc\ucp.php: moodle_exception thrown
Ideas?
It seems that the program only sync users with teachers licenses. I had deleted all of my users from O365, then I ran cron. I got all of my teachers back, but my students not. Could you, or anyone help me?
Thank you for your reply!
I can't be absolutely sure if the error happened after the update, but I would say it about 90%.
We are still using our office 365 subscription as an experimental project in our school, so I only registered the teachers in September. That time Moodle got all of the users from O365 successfully (although I had problems with users that were deleted from O365 later on). This weekend I upgraded all of our plugins to the latest releases and than Moodle itself from 2.9.1+ to 2.9.2+ successfully. A few hours later I added all of my students as well (~ 100) to O365 with student licenses and I thought everything will be alright. Yesterday I found out that my new users were not synced so I ran cron manually and that is what I got.
Unfortunately I am only a power user and not a programmer and I still have very little experiment with O365.
"Execute scheduled task: Sync users with AAD.
... started 16:17:47. Current memory use 32.7MB.
Could not create user "xxxxx@thankaroly.hu" Reason: Hiba az adatbázis írása közben."
... and the list continues with the other users and the same error message...
"Hiba az adatbázis írása közben" means: "an error happened when writing into the database".
The strangest thing is that they CAN still log into the system, but only as brand new users and they have to supply all of their data (eg.: e-mail address) after the login page.
Any ideas?
The Moodle log states: "Login failed for the username xyz for the reason with id '3'".
I found that just means that someone tried to log in with a valid username but with a wrong password.
By the way we implemented Moodle 2.9.1+ (Build 20150730)
That is very odd! What exactly happens when you have this special character in the password? Does Moodle give you an error message or Azure/O365?
At our university we implemented the plugin (connection to Office 365) succesfully with just one small issue: authentication does not work correctly when the password contains a special character (@ for example) on the first and only on the first position! Do you have an explanation for this strange behavior?
Thanks Martin