Are you looking for a solution for the error message “error/moodle/generalexceptionmessage”? We can help you.
A few days ago, we had come across this error message and our Support Engineers fixed it efficiently.
Here at Bobcares, we often receive requests to fix Moodle errors as a part of our Server Management Services.
Today, let’s see the possible causes for this error and see how our Support Engineers fix this error.
Why does the exception error message show up?
We have seen this error appearing during moodle upgrade attempt, while attempting to add courses in moodle, creating a guest or admin user and many during many other occasions.
The most common causes for this error that we have seen is due to corrupt plugins, outdated moodle version, missing a few necessary PHP libraries and many more.
Among these, the most common one is the plugins that are mainly used in messaging.
Possible causes for error/moodle/generalexceptionmessage to appear
Now, let’s discuss the common causes due to which this error message appears.
1. Faulty plugins
Many of our customers enable plugins for messaging in moodle. Sometimes, these plugins won’t be compatible with the PHP version or the moodle version due to which it will throw an error message.
Hence, disabling this plugin will normally fix the error.
2. Missing PHP Libraries
We’ve seen customers experiencing this error if the necessary PHP libraries are not available on the server.
However, this can be easily found through the error message displayed in the moodle.
3. Outdated Moodle version
Sometimes, if the Moodle is not up-to-date then it will throw an error.
So it is always recommended to keep the moodle updated.
How we fix this error/moodle/generalexceptionmessage?
Our Support Engineers are well experienced in managing servers and are familiar with Moodle errors. Now, let’s see how our Support Engineers fix this error.
1. Faulty plugins
One of our customers approached us with the error message generalexceptionmessage in moodle. Here is the screenshot of the error message.
Our Support Engineers started troubleshooting this error by checking the version of Moodle.
As a result, we found that the moodle was of the latest version.
Then we went checking for any third plugins enabled for messaging if they are causing any problem.
For that, we followed the below steps:
1. Accessed the Site Administration.
2. Clicked on the Plugin and then Plugins overview option.
3. Then accessed the Additional plugins.
Here, we found that there was a third party plugin enabled. Disabling it fixed the error.
Through this, we could find that the plugin was causing the problem.
2. Missing PHP XML Library
We came across the same error message but on another occasion. One of our customers was trying to upgrade the moodle and ran into the below error message
# php moodle/admin/cli/upgrade.php
Default exception handler: Exception - Call to undefined function xml_parser_create() Debug:
Error code: generalexceptionmessage
* line 76 of /lib/xmlize.php: Error thrown
* line 307 of /lib/environmentlib.php: call to xmlize()
* line 355 of /lib/environmentlib.php: call to load_environment_xml()
* line 101 of /lib/environmentlib.php: call to get_latest_version_available()
* line 116 of /admin/cli/upgrade.php: call to check_moodle_environment()
!!! Exception - Call to undefined function xml_parser_create() !!!
!!
Error code: generalexceptionmessage !!
!! Stack trace: * line 76 of /lib/xmlize.php: Error thrown
* line 307 of /lib/environmentlib.php: call to xmlize()
* line 355 of /lib/environmentlib.php: call to load_environment_xml()
* line 101 of /lib/environmentlib.php: call to get_latest_version_available()
* line 116 of /admin/cli/upgrade.php: call to check_moodle_environment()
!!After looking at this error message our Support Engineers found that the PHP XML library was missing.
Finally, we fixed this error by installing the XML library by running the below command:
apt-get install php7.0-xml
service apache2 restartAfter this, the customer was able to upgrade the moodle.
[Need any assistance in fixing the moodle errors? – We’ll help you]
Conclusion
In short, the error/moodle/generalexceptionmessage appears due to many reasons which include faulty plugins, missing PHP libraries, outdated moodle and many more. Today, we saw how our Support Engineers fix this error.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
var google_conversion_label = «owonCMyG5nEQ0aD71QM»;
error/generalexceptionmessage upgrading to 3.11.4
- ◄ problem with Moodle 3.7.7 (Build: 20200713)
- Which table stores data of user accessing the site ? ►
Hi,
I tried for the second time to upgrade a copy of my moodle 3.11.1+ (Build: 20210716) installation to version 3.11.4 2021051704.02 and when I try to log in after copying the usual files and directories from my old version I get this error instead.
Has anyone else received this and found a solution?
Thanks and best regards.
Michael
«after copying the usual files and directories from my old version» … which are what? And since you ‘copied’ were ownerships/permissions on old files and directories you were copying retained?
Add debug lines to config.php and try it again. Debug lines found in Section 7 of config-dist.php file.
Also check web service error logs for some hints/clues.
‘SoS’, Ken
Average of ratings: Useful (1)
Thanks Ken, and sorry for having been imprecise.
With «usual files» I wanted to say that I also copy them, like config.php, .htaccess (file permissions remained 644), thememoove and some more. They havent’t changed in all my other upgrades so far.
In the servers error .log file shows only this:
AH01071: Got error ‘PHP message: PHP Warning: Use of undefined constant MINSECS — assumed ‘MINSECS’ (this will throw an Error in a future version of PHP) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/message/lib.php on line 62PHP message: PHP Warning: A non-numeric value encountered in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/message/lib.php on line 62PHP message: PHP Warning: Use of undefined constant MINSECS — assumed ‘MINSECS’ (this will throw an Error in a future version of PHP) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/message/lib.php on line 63PHP message: PHP Warning: A non-numeric value encountered in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/message/lib.php on line 63′
and that line is:
define(‘MESSAGE_DEFAULT_MAX_POLL_IN_SECONDS’, 2 * MINSECS);
After I enabled ALL lines in section 7 and copied the lines to config.sys, I still get only the same rows in the error.log
access.log shows (first with Chrome, second with Firefox)
185.77.84.44 — — [25/Nov/2021:17:43:00 +0100] «HEAD /moodle/admin/ HTTP/1.1» 500 — «-» «Microsoft Office Word 2014»
185.77.84.44 — — [25/Nov/2021:17:43:00 +0100] «GET /moodle/admin/ HTTP/1.1» 500 — «-» «Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36»
Where shall I see the added debug information ?
I attach my config.sys is:
I wish you a great day/evening
Michael
One does not copy the entire Section 7 from config-dist.php to config.php …
Just these lines without the // comments. Looks like:
@error_reporting(E_ALL | E_STRICT);
@ini_set(‘display_errors’, ‘1’);
$CFG->debug = (E_ALL | E_STRICT);
$CFG->debugdisplay = 1;
and they are added above this line:
require_once(__DIR__ . ‘/lib/setup.php’);
and note that all of those lines end with a ‘;’
Your first error log line says something about Microsoft Word!!!!???? Huh?
You didn’t edit config.php with Word, did ya?
What I get when going to your site either / or /moodle/ is a 403 error and the typical screen that is used for that error saying: ‘Forbidden … you don’t have permissions to access this resource’ … which is usually a sign of ownerships/permissions not allowing the web service user access.
‘SoS’, Ken
Average of ratings: Useful (1)
Dear Ken, I just cannot express how much I appreciate your help.
Of course, I use notepad++ to edit files and I was wondering about the mention of Word myself.
At first I tried the 4 lines but since I put them at the end…
Now that I moved them above I got the following message on the mozilla screen (both moziulla and chrome):
$a contents: Call to undefined function get_config()
Stack trace:
line 797 of /lib/setuplib.php: Error thrown
line 658 of /lib/setup.php: call to initialise_cfg()
line 39 of /config.php: call to require_once()
line 88 of /admin/index.php: call to require()
Perhaps I need to go through all single version upgrades from mine to the last version, or is it a bug ? Where shall that function be defined?
I tried to rem out the line require_once(__DIR__ . ‘/lib/setup.php’);
but this causes the following msg in the browser:
Notice: Undefined property: stdClass::$dirroot in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/admin/index.php on line 93
Fatal error: Uncaught Error: Class ‘core_component’ not found in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/admin/index.php:97 Stack trace: #0 {main} thrown in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/admin/index.php on line 97
Not sure what to do.
As for the problem you experienced trying to connect, it is due to the .htaccess file giving a narrow range of IP adresses. Furthermore, the provider has a feature called «live staging» what means that most people see the old working version while some IPs see the copy where I test. If you want to retry, you must give me the iIP address from which you are connecting.
Have a great week end,
Michael
PS: by the way, what does ‘SoS’ mean ?
The debug lines go above this one:
require_once(__DIR__ . ‘/lib/setup.php’);
note the comments in the file at the bottom.
At the top of your config.php file … should look like:
<?php // Moodle configuration file
unset($CFG);
global $CFG;
$CFG = new stdClass();
Am confused …
«go through all single version upgrades from mine to the last version«
thought you said going from a 3.11.x to a 3.11.4 … which is a minor point release of code. So, have to ask what was the version you started this upgrade with?
If lower than 3.11.x, then yes, you *might* have to depending upon the version. There are «dependencies» — going from lower to higher … PHP version, and php extensions, MySQL version, etc.
https://docs.moodle.org/dev/Releases
One way to check … once you get your previous site restored and working, go to Admin Menu -> Server -> Environment check. Update the component. Then select desired version of moodle in the drop down list and see what moodle says … yellow probably need to do … red must do.
SoS = ‘Spirit of Sharing’.
‘SoS’, Ken
When I spoke about the versions, I meant 3.11.2 to 3.11.3 but I found today that they are no more available. I tried the official version today instead of the last stable one but to no avail.
I still did your check and my system is fit even for version 4. I have two directories on the server so I can switch between the good and the bad on the fly.
I checked the config.php again with your hints. Perhaps I should not copy it back but merge it ?
However, the first 4 lines are exactly the ones you stated. I attached my file in one of the previous posts.
Yes, I did put the debug lines above «require_once(__DIR…..». That’s why I got the additional information.
Any idea about the function get_config() ? Where should it be defined? I did not undefine anything 😁
Michael
PS: what happens if I have forgotten to copy the directory of an installed plugin from the old installation to the new version before loging to admin ?
Moodle consist of code + a database that must match (tons of version.php files). So this ‘staging’ thing you’ve mentioned you can flip between on the fly must have staging code + a staging db. The moodledata directory is seldom touched on an upgrade but moodle caches a bunch. One of the recommendations one might see upon upgrading is to clear the cache directory in moodledata. Moodle will rebuild that cache.
Yes, you need to copy the config.php + any addon you’ve installed (like a theme) to the upgraded code directory. If an addon has a higher version available, usually, after the first run of cron, a notification should be sent or seen in Notifications of the site.
On checking plugins, if you did not copy from old to new, you’d see ‘missing from disk’ … meaning there is references and tables for the plugin in the DB, but the files are not there.
There is a mdl_config_plugins table … and if staging site/production site are using same DB and not a separate DB for each, would think your moodle is confused.
‘SoS’, Ken
Average of ratings: Useful (1)
No worries, Ken, the staging is well designed and proven by myself in several updates and it duplicates every part: db, code and even the datadirectory under private (even a different php version is selectable).
Ok, I will try to keep my records updated with any new plugin i might install in the future, but since you confirmed that I should receive an explicit message for missing directories, the risks are low.
However, I guess I’ll destroy it today and restart with a fresh copy – just to be sure – and let you know, of course.
Regards,
Michael
Hi Ken,
it’s really crazy!
Now I copied the files of version 3.11.4 again to the site and, even without any change, before copying .htaccess and config.php, when I point the browser to …/admin I already get the usual error:
Fatal error: Uncaught Error: Call to undefined function get_string() in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/install.php:636 Stack trace: #0 {main} thrown in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/install.php on line 636
Then I copied .htaccess and config.php and the only thing that changes is the layout of the error page and the return of the original «error/generalexceptionmessage.».
I tried to search for «undefined function get_string()» but I cannot find useful help. Seems as if this version has problems but if I am the only one…
As far as I can see, the function is defined in libmoodlelib.php only and this file is nearly the same in my old and the new version, which has only one mor function.
By the way, I use php 7.4
Michael
line 636 of install.php:
In this section of that file:
$sub = ob_get_clean();
install_print_header($config, get_string(‘language’),
get_string(‘chooselanguagehead’, ‘install’),
$sub, ‘alert-success’);
} else {
** install_print_header($config, get_string(‘language’),
get_string(‘chooselanguagehead’, ‘install’),
get_string(‘chooselanguagesub’, ‘install’));
So your issue appears to be around languages. Default for fresh install is en.
Clarification … the ‘missing from disk’ should/would show only for *addons* and only when site is up and running and you’ve gone to admin area to check plugin upgrades.
So your staging thing, clones production … and changes config.php to reflect a different url to access, a different DB (which has been cloned — how? raw file copy?), a different moodledata location (which has also been cloned). There is a ‘lang’ directory in moodledata.
In the cloned moodledata is there is a ‘cache’ directory? Might consider manually removing contents of that directory prior to attempting to upgrade the DB in ‘staging’.
If you ran Linux, I’d suggest using git … fewer moving parts and a minor point release upgrade is trivial and takes only a couple of git commands + one can finish the upgrade via CLI — literally takes just a few of minutes.
‘SoS’, Ken
Well I’ll try right now, but I remember, after copying back my config last time adding the debug lines, I got different lines where that function was not working. They were:
$a contents: Call to undefined function get_config()
Stack trace:
line 797 of /lib/setuplib.php: Error thrown
line 658 of /lib/setup.php: call to initialise_cfg()
line 39 of /config.php: call to require_once()
line 88 of /admin/index.php: call to require()
Not sure how staging exactly works and the documentation is only in italian. It is build (and called this way) because you can even try out changes, installations, upgrades a.s.o. and publish it back to production (while production is in hold).
Ok, I try your hint and get back here (hopefully not 😉)
Michael
Now I cancelled every single file from the private/moodledata/cache directory, leaving the underlying directory structure as is
Result: no change (still «error/generalexceptionmessage»
After adding the 4 debug lines to config.php I read several similar warnings like the following:
Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210
Warning: Use of undefined constant MINSECS — assumed ‘MINSECS’ (this will throw an Error in a future version of PHP) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/message/lib.php on line 62
Warning: A non-numeric value encountered in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/message/lib.php on line 62
Warning: Use of undefined constant MINSECS — assumed ‘MINSECS’ (this will throw an Error in a future version of PHP) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/message/lib.php on line 63
Warning: A non-numeric value encountered in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/message/lib.php on line 63
Error
error/generalexceptionmessage
Debug info:
Error code: generalexceptionmessage
$a contents: Call to undefined function get_config()
Stack trace:
line 797 of /lib/setuplib.php: Error thrown
line 658 of /lib/setup.php: call to initialise_cfg()
line 37 of /config.php: call to require_once()
line 88 of /admin/index.php: call to require()
The last 2 warnings are regarding the following 2 lines:
define(‘MESSAGE_DEFAULT_MAX_POLL_IN_SECONDS’, 2 * MINSECS);
define(‘MESSAGE_DEFAULT_TIMEOUT_POLL_IN_SECONDS’, 5 * MINSECS);
Can they have to do with it?
The next that I tried was to unrem other debug lines: no added information achieved.
Now I try something more extreeme: to merge the new version into the old one by overriding older files and after that I shall uninstall all third party plugins before upgrading. — or at least the oldest ones.
The table config_plugins has 2136 rows; 472 distinct plugins. Are they all not moodle core ??? We installed not even half a dozen…
Regards,
Michael
PS. What you wrote about the staging is true. I also found sql files used with the whole database content to be rebuilt.
Making progress … believe it or not! 
The following error I think causes the others that follow and might be the root cause of the issue — even if it says ‘Warning’:
Warning: is_readable(): open_basedir restriction in effect.
File(/db/renamedclasses.php) is not within the allowed path(s):
(/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom)
in
/var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php
on line 1210
You could try the following in the .htaccess file since you say you have an .htaccess file to restrict client access to staging:
php_flag open_basedir offNote: ... not that it matters ... I've never had to do that! ????
'SoS', Ken
Average of ratings: Useful (1)
Hope so
I am still waiting on an answer from the provider but, in case, send me the command you want me to execute on the server and I will send it to them.
My .htaccess is now: very similar to this:
order deny,allow
deny from all
allow from 217.57….
php_flag open_basedir off
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{ENV:HTTPS} off
RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301,NE]
</IfModule>
#QUESTO AGGIUNGE ACCESSO TRAMITE JMIL TUTELA RELEASE
SetEnvIfNoCase Referer «tutelarelease.siaspa.com» good_referer
#QUESTO SERVE PERCHE CONTINUI A FUNZIONARE UNA VOLTA LOGGATO
SetEnvIfNoCase Referer «elearningtl.siaspa.com» good_referer
Allow from env=good_referer
And the debug output has become:
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at postmaster@elearningtl.siaspa.com to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
In the error log I find:
elearningtl.siaspa.com [Thu Dec 02 18:22:56 2021] [error] [pid 6597] mod_proxy_fcgi.c(888): [client 185.77.84.44:0] AH01071: Got error ‘PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/lib/classes/component.php on line 1210’
elearningtl.siaspa.com [Thu Dec 02 18:25:01 2021] [alert] [pid 6121] config.c(2046): [client 185.77.84.44:0] /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/.htaccess: Invalid command ‘php_flag’, perhaps misspelled or defined by a module not included in the server configuration
elearningtl.siaspa.com [Thu Dec 02 18:25:20 2021] [alert] [pid 6217] config.c(2046): [client 185.77.84.44:0] /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/.htaccess: Invalid command ‘php_flag’, perhaps misspelled or defined by a module not included in the server configuration
elearningtl.siaspa.com [Thu Dec 02 18:25:28 2021] [alert] [pid 6217] config.c(2046): [client 185.77.84.44:0] /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/.htaccess: Invalid command ‘php_flag’, perhaps misspelled or defined by a module not included in the server configuration
elearningtl.siaspa.com [Thu Dec 02 18:27:50 2021] [alert] [pid 6121] config.c(2046): [client 185.77.84.44:0] /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/.htaccess: Invalid command ‘php_flag’, perhaps misspelled or defined by a module not included in the server configuration
elearningtl.siaspa.com [Thu Dec 02 18:28:26 2021] [error] [pid 6598] mod_proxy_fcgi.c(888): [client 185.77.84.44:0] AH01071: Got error ‘PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210’
elearningtl.siaspa.com [Thu Dec 02 18:28:28 2021] [error] [pid 6598] mod_proxy_fcgi.c(888): [client 185.77.84.44:0] AH01071: Got error ‘PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/db/renamedclasses.php) is not within the allowed path(s): (/var/www/vhosts/elearningtl.siaspa.com/:/tmp/:/var/lib/php/session/:/dev/urandom) in /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moodle/lib/classes/component.php on line 1210’
elearningtl.siaspa.com [Thu Dec 02 18:28:54 2021] [alert] [pid 6122] config.c(2046): [client 185.77.84.44:0] /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/.htaccess: Invalid command ‘php_flag’, perhaps misspelled or defined by a module not included in the server configuration
elearningtl.siaspa.com [Thu Dec 02 18:28:55 2021] [alert] [pid 6124] config.c(2046): [client 185.77.84.44:0] /var/www/vhosts/elearningtl.siaspa.com/httpdocs/moo_test/.htaccess: Invalid command ‘php_flag’, perhaps misspelled or defined by a module not included in the server configuration
Contact provider about:
open_basedir restriction in effect (path to a moodle script) not within the allowed path(s). logs then show what paths your server knows about and is allowing.
and the other:
Invalid command ‘php_flag’, perhaps misspelled or defined by a module not included in the server configuration
The php_flag in your .htaccess file.
Found this with a quick Google search: «php flags in .htaccess»
https://support.tigertech.net/php-value
‘SoS’, Ken
Average of ratings: Useful (1)
Hi, the provider says «a warning is a warning blah blah» and since our php server is shared, we cannot add anything to the php.ini.
What he suggests is to try to upgrade himself so I will propably ask him to do so in staging next week.
Happy weekend.
Michael
‘shared’ and control of a moodle updates/upgrades by customer has always been a problem. «He» must think ‘he’ knows a way around the issues on ‘shared’ … but not disclosing that to customer who doesn’t have high enough access level … then it’s good ‘he’ is doing this on ‘staging’.
Is this going to cost you more … time/frustration/downtime/$ … each time you need to update or upgrade in the future? It is well known that of the top 2 reasons sites are compromised etc is ‘failure to fix/patch’. While Moodle security is generally pretty good (few have been hacked), there is always that chance it could be.
Take a gander @ https://docs.moodle.org/dev/Releases and especially 3.11.x
https://docs.moodle.org/dev/Releases#Moodle_3.11
The version you are upgrading to did have one «emergency minor release’ … in Windows terms ‘out of band’ (think that’s the term used). What’s ‘minor’ to some is ‘major’ to others — been my observation.
So …. all in all … I can no longer advise. Sorry ’bout that!
Best of luck!
‘SoS’, Ken
Average of ratings: Useful (1)
Do not merge two different code versions!! It will not help and you will have no idea what issue is arising from which part.
Average of ratings: Useful (1)
+20 to Emma’s advice on *not merging*!
Question: do you have command line access to your server?
Does server have git installed?
‘SoS’, Ken
Don’t think so, need to ask the provider.
I have file access through filezilla and DB through browser.
If necessary could try to install a local copy with XAMPP
Leaving…have a pleasant working day and evening
Michael
Eureka! The provider succeeded.
What did he do different? I still have to try to repeat it but meanwhile I succeeded in updating that copy to «my» moodle.
What he did after uploading of the 3.11.4+ version was:
- copy some of my directories into it, without overwriting (thus adding my plugins not comprised in the core):
mod
themes
blocks
(he did not copy anything into auth and login yet) - I think he copied my config.php but with the one line I added remmed. The line is: $CFG->logoutredir = «https://tutela… and makes moodle turn to the only site from where users log on automatically after logging off. This is done thanks to a plugin (directory loginlogoutredir copied under auth
- He also did not copy .htaccess yet.
However, both points 2.and 3.are working now. Perhaps I need to start without modifying auth and login leaving changes for after the upgrade.
Stay tuned
Well, I was not THAT silly.
I always copied the directories I know I had added. Instead of copying the whole mod directory (saying no when it came to overwrite files), in the past I just copied selected directories. The moodle docs don’t say which method to use to copy them back to new.
If I forget one, I will get the message that a directory is missing — no problem.
The problem was supposedly that I might have copied
either a modified files without the necessary directory
or I copied a directory without the lines that uses it.
But until I retry I cannot tell.
Happy weekend
Michael
Am still not certain … but maybe this will help … this time.
Core mod directories/files of a 3.11.4+ (Build: 20211210) as of today:
README.txt
assign
assignment
book
chat
choice
data
feedback
folder
forum
glossary
h5pactivity
imscp
index.html
label
lesson
lti
page
quiz
resource
scorm
survey
upgrade.txt
url
wiki
workshop
core blocks files/folders
accessreview
activity_modules
activity_results
admin_bookmarks
badges
blog_menu
blog_recent
blog_tags
calendar_month
calendar_upcoming
classes
comments
completionstatus
course_list
course_summary
edit_form.php
feedback
globalsearch
glossary_random
html
index.html
login
lp
mentees
mnet_hosts
moodleblock.class.php
myoverview
myprofile
navigation
news_items
online_users
private_files
quiz_results
recent_activity
recentlyaccessedcourses
recentlyaccesseditems
rss_client
search_forums
section_links
selfcompletion
settings
site_main_menu
social_activities
starredcourses
tag_flickr
tag_youtube
tags
tests
timeline
upgrade.txt
core themes
boost
classic
font.php
image.php
index.php
javascript.php
jquery.php
styles.php
styles_debug.php
switchdevice.php
upgrade.txt
yui_combo.php
yui_image.php
Any folder or file you have in your code mod/blocks/themes/ directories NOT in listings above *is an addon*.
‘SoS’, Ken
Average of ratings: Useful (1)
- ◄ problem with Moodle 3.7.7 (Build: 20200713)
- Which table stores data of user accessing the site ? ►
Are you looking for a solution for the error message “error/moodle/generalexceptionmessage”? We can help you.
A few days ago, we had come across this error message and our Support Engineers fixed it efficiently.
Here at Bobcares, we often receive requests to fix Moodle errors as a part of our Server Management Services.
Today, let’s see the possible causes for this error and see how our Support Engineers fix this error.
Why does the exception error message show up?
We have seen this error appearing during moodle upgrade attempt, while attempting to add courses in moodle, creating a guest or admin user and many during many other occasions.
The most common causes for this error that we have seen is due to corrupt plugins, outdated moodle version, missing a few necessary PHP libraries and many more.
Among these, the most common one is the plugins that are mainly used in messaging.
Possible causes for error/moodle/generalexceptionmessage to appear
Now, let’s discuss the common causes due to which this error message appears.
1. Faulty plugins
Many of our customers enable plugins for messaging in moodle. Sometimes, these plugins won’t be compatible with the PHP version or the moodle version due to which it will throw an error message.
Hence, disabling this plugin will normally fix the error.
2. Missing PHP Libraries
We’ve seen customers experiencing this error if the necessary PHP libraries are not available on the server.
However, this can be easily found through the error message displayed in the moodle.
3. Outdated Moodle version
Sometimes, if the Moodle is not up-to-date then it will throw an error.
So it is always recommended to keep the moodle updated.
How we fix this error/moodle/generalexceptionmessage?
Our Support Engineers are well experienced in managing servers and are familiar with Moodle errors. Now, let’s see how our Support Engineers fix this error.
1. Faulty plugins
One of our customers approached us with the error message generalexceptionmessage in moodle. Here is the screenshot of the error message.
Our Support Engineers started troubleshooting this error by checking the version of Moodle.
As a result, we found that the moodle was of the latest version.
Then we went checking for any third plugins enabled for messaging if they are causing any problem.
For that, we followed the below steps:
1. Accessed the Site Administration.
2. Clicked on the Plugin and then Plugins overview option.
3. Then accessed the Additional plugins.
Here, we found that there was a third party plugin enabled. Disabling it fixed the error.
Through this, we could find that the plugin was causing the problem.
2. Missing PHP XML Library
We came across the same error message but on another occasion. One of our customers was trying to upgrade the moodle and ran into the below error message
# php moodle/admin/cli/upgrade.php
Default exception handler: Exception - Call to undefined function xml_parser_create() Debug:
Error code: generalexceptionmessage
* line 76 of /lib/xmlize.php: Error thrown
* line 307 of /lib/environmentlib.php: call to xmlize()
* line 355 of /lib/environmentlib.php: call to load_environment_xml()
* line 101 of /lib/environmentlib.php: call to get_latest_version_available()
* line 116 of /admin/cli/upgrade.php: call to check_moodle_environment()
!!! Exception - Call to undefined function xml_parser_create() !!!
!!
Error code: generalexceptionmessage !!
!! Stack trace: * line 76 of /lib/xmlize.php: Error thrown
* line 307 of /lib/environmentlib.php: call to xmlize()
* line 355 of /lib/environmentlib.php: call to load_environment_xml()
* line 101 of /lib/environmentlib.php: call to get_latest_version_available()
* line 116 of /admin/cli/upgrade.php: call to check_moodle_environment()
!!After looking at this error message our Support Engineers found that the PHP XML library was missing.
Finally, we fixed this error by installing the XML library by running the below command:
apt-get install php7.0-xml
service apache2 restartAfter this, the customer was able to upgrade the moodle.
[Need any assistance in fixing the moodle errors? – We’ll help you]
Conclusion
In short, the error/moodle/generalexceptionmessage appears due to many reasons which include faulty plugins, missing PHP libraries, outdated moodle and many more. Today, we saw how our Support Engineers fix this error.
The post Why does error/moodle/generalexceptionmessage appear? appeared first on Bobcares.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
- Pick a username
- Email Address
- Password
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
#php #moodle
Вопрос:
Я пытаюсь запустить moodle на локальном хосте, появляется ошибка — что я делаю не так и как я могу это исправить ? код config.php -переименовал его в свой локальный хост, установил соединение
<?php // Moodle configuration file
unset($CFG);
global $CFG;
$CFG = new stdClass();
$CFG->dbtype = 'mysql';
$CFG->dblibrary = 'native';
$CFG->dbhost = 'localhost';
$CFG->dbname = 'moodledb';
$CFG->dbuser = 'root';
$CFG->dbpass = '';
$CFG->prefix = 'mdl_';
$CFG->dboptions = array (
'dbpersist' => 0,
'dbport' => 3306,
'dbsocket' => '',
'dbcollation' => 'utf8mb4_unicode_ci',
);
$CFG->wwwroot = 'C:/Server/data/htdocs/moodle/moodle';
$CFG->dataroot = 'C:/Server/data/htdocs/moodle/moodledata';
$CFG->admin = 'admin';
$CFG->directorypermissions = 0777;
require_once(__DIR__ . '/lib/setup.php');
// There is no php closing tag in this file,
// it is intentional because it prevents trailing whitespace problems!
ошибка/generalexceptionmessage
Код, который был на сервере в конфигурации:
<?php // Moodle configuration file
unset($CFG);
global $CFG;
$CFG = new stdClass();
$CFG->dbtype = 'mariadb';
$CFG->dblibrary = 'native';
$CFG->dbhost = 'localhost';
$CFG->dbname = 'moodledb';
$CFG->dbuser = 'moodleedu';
$CFG->dbpass = 'moodleedpas';
$CFG->prefix = 'mdl_';
$CFG->dboptions = array (
'dbpersist' => 0,
'dbport' => 3306,
'dbsocket' => '',
'dbcollation' => 'utf8mb4_unicode_ci',
);
$CFG->wwwroot = 'https://moodle.com';
$CFG->dataroot = '/var/www/moodledata';
$CFG->admin = 'admin';
$CFG->directorypermissions = 0777;
require_once(__DIR__ . '/lib/setup.php');
// There is no php closing tag in this file,
// it is intentional because it prevents trailing whitespace problems!
Кроме того, возникает вопрос, где я могу более конкретно посмотреть список ошибок в moodle — где он записывает данные?
Комментарии:
1. «wwwroot» — это URL-адрес в конфигурации сервера, но локальный путь в локальной конфигурации… может быть?
2. @LarsStegelitz изменено: $CFG->wwwroot = ‘> локальный хост:3000/moodle/moodle ‘;. Ошибка все еще оставалась