After upgrade to v3.0 of Moodle a error message 'get_device_type is removed, please update your code to use core_useragent instead' appears when enter creating new courses and changes profiles. All modules are updated. The associated help utility does not tell anything meaningful in how to deal with this.
Is there anybody who knows what to do in order to solve this problem??
Hello,
I'm hosting a Moodle site at Godaddy.com. I believe that, for e-mail purposes, everything is installed as default. However, I'm getting the following error every time Moddle needs to send an e-mail.
The Godaddy support sent me the following configuration, and I put that on Moodle.
Does anyone knows what can I do to solve this problem?
Thanks!
The error is:
2016-03-23 13:40:07 Connection: opening to localhost:25, t=10, opt=array (
)
2016-03-23 13:40:07 Connection: opened
2016-03-23 13:40:07 SMTP -> get_lines(): $data was ""
2016-03-23 13:40:07 SMTP -> get_lines(): $str is "220-a2plcpnl0377.prod.iad2.secureserver.net ESMTP Exim 4.85_1 #1 Wed, 23 Mar 2016 06:40:07 -0700"
2016-03-23 13:40:07 SMTP -> get_lines(): $data is "220-a2plcpnl0377.prod.iad2.secureserver.net ESMTP Exim 4.85_1 #1 Wed, 23 Mar 2016 06:40:07 -0700"
2016-03-23 13:40:07 SMTP -> get_lines(): $data was "220-a2plcpnl0377.prod.iad2.secureserver.net ESMTP Exim 4.85_1 #1 Wed, 23 Mar 2016 06:40:07 -0700"2016-03-23 13:40:07 SMTP -> get_lines(): $str is "220-We do not authorize the use of this system to transport unsolicited, "
2016-03-23 13:40:07 SMTP -> get_lines(): $data is "220-a2plcpnl0377.prod.iad2.secureserver.net ESMTP Exim 4.85_1 #1 Wed, 23 Mar 2016 06:40:07 -0700
220-We do not authorize the use of this system to transport unsolicited,"
2016-03-23 13:40:07 SMTP -> get_lines(): $data was "220-a2plcpnl0377.prod.iad2.secureserver.net ESMTP Exim 4.85_1 #1 Wed, 23 Mar 2016 06:40:07 -0700
220-We do not authorize the use of this system to transport unsolicited,"2016-03-23 13:40:07 SMTP -> get_lines(): $str is "220 and/or bulk e-mail."
2016-03-23 13:40:07 SMTP -> get_lines(): $data is "220-a2plcpnl0377.prod.iad2.secureserver.net ESMTP Exim 4.85_1 #1 Wed, 23 Mar 2016 06:40:07 -0700
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail."
2016-03-23 13:40:07 SERVER -> CLIENT: 220-a2plcpnl0377.prod.iad2.secureserver.net ESMTP Exim 4.85_1 #1 Wed, 23 Mar 2016 06:40:07 -0700
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
2016-03-23 13:40:07 CLIENT -> SERVER: EHLO moodle.tavares.eng.br
2016-03-23 13:40:07 SMTP -> get_lines(): $data was ""Hi Usman, thanks for your reply. I shall have another look at our php.ini file. It occurred to me that this actually isn't related to file type but indeed file size as the different types I was testing differed significantly in size with the backup file being the biggest. I'll start a new thread (as this is Antelope / Barracuda) once I have more information.
Hello,
I have a standard linux shared hosting with CPanel. Is it informations enough? (I couldn't find anything more than that)
Thanks!
You have a plugin that is not compatible with Moodle 3.0. Check your *optional* plugins are all up to date.
I just ran into this problem. It turned out that the /cache/stores/file/lib.php was incomplete. I FTPed just that file and it now works.
Thanks so much for your help!
I have multiple backups, so no worries there.
I've resolved the problem by changing the $plugin->version in the /mod/quiz/version.php file to the version that the upgrade script complained about (2014080700).
Upgrade successful!
I still can't figure out why the upgrade script said my version would be a downgrade. I tried removing the mod, and replacing it with a newer 2.7 version as you suggested which resulted in the same complaint. Oh well, nothing seems to be broken yet!
HI,
Yes they are available in database. In fact i moved the updated database from new server to old server and checked, those images are still appearing. No issues.
Is there any gd library required like imagemagick? or is there any other settings am i missing when migrating.
Hi
I'm using Moodle 3.0.3+ (Build: 20160317)
I've installed eguru and archaius themes. They are not showing up in Site Administration - Appearance-Themes, also no Notifications.
I've cleared cache in theme Selector and purged caches in Development.
Any help appreciated.
Thanks
I have same problem...! after migrating website to new dedicated server, no old images working (header, old profile picture, etc) and get notification: Cannot read file. Either the file does not exist or there is a permission problem. More information about this error.
This my website
anyone can help me? thank's
How did you install them?
Go to Site administration > Notifications to make sure the install routine has been executed.
Go to Site administration > Plugins > Plugins overview. Do they show up in the list of plugins? If not, they are either not installed at all or the file permissions are wrong (the web server can't read the files)
Hi Howard
Thanks for your reply.
The themes are not showing under plugins and there are no notifications.
What should the file permission be? The existing theme of 'Clean' is 767, so it doesn't seem to be this issue.
Any further suggestions appreciated.
Thanks
I used the one-click install.
Using user and password does not change anything...
Thanks!
Oh... did you try to access that README.txt file?
That's an important check
You should also run the Replace tool (/admin/tool/replace/index.php) to change all occurrences of 'https' in your Moodle database to 'http'.
removed all themes and added themes from v3.0.3+. Then added applied themes one by one, and then everything worked fine.
Thank you for useful support.
Hmmm. It might be a problem with the one-click install. Have you done anything on the cPanel side of things about email, yet?
Would you know how to install moodle from scratch?
I have moodle running on my GoDaddy hosted server, and email is working. But I installed moodle manually myself. Sometimes these "easy" one-click installs do strange things.
I figured out the solution to my first question: I forgot to set the prefix while running the Database Migration tool, that's why the migrated database was not accepted - the prefixes on config.php did not match the migrated database. I've now successfully migrated a near empty devlopment Moodle site's database from postgresql to mysql with the migrate.php script.
However, I've run into a different problem with migrating our production Moodle site's database that's much bigger. Now, the migrate.php script fails at the same place everytime trying to migrate the production database from postgresql to mysql. The error in PHP is
[25-Mar-2016 13:13:30 America/Los_Angeles] Potential coding error - active database transaction detected when disposing database:
* line 126 of \lib\dtl\database_importer.php: call to moodle_database->start_delegated_transaction()
* line 79 of \lib\dtl\database_mover.php: call to database_importer->begin_database_import()
* line 145 of \lib\dtl\database_exporter.php: call to database_mover->begin_database_export()
* line 85 of \admin\tool\dbtransfer\locallib.php: call to database_exporter->export_database()
* line 187 of \admin\tool\dbtransfer\cli\migrate.php: call to tool_dbtransfer_transfer_database()
The migration is smooth all the way up to the 'user' table, and fails there everytime. On the mysql database, preceding tables are all there. The 'user' table has about 450 entries on the postgresql production database, and on the incomplete/failed mysql destination database there are about 390 entries. In the Command Line where I run migrate.php, the error displayed is
Copying table timezone
Done
Copying table user
!!! Error writing to database !!!
I've also tried Maintenace Mode and also Stopping the site completely in IIS.
Any insight is appreciated, thank you.
Is the place you've FTP'd them to for the same server as you are accessing? Not a silly question as has happened in the past.
The Network Administrator does not know what they are talking about as the web server can be told to serve Moodle in a URL sub folder with 'Alias': https://httpd.apache.org/docs/2.4/urlmapping.html#outside - thus DNS to the machine then configure the web server (an OS change - not Moodle) with Alias then change Moodle config.php as Usman instructs.