Quantcast
Channel: Installing and upgrading help
Viewing all 46925 articles
Browse latest View live

Re: update version of moodle

$
0
0
by Howard Miller.  

It shouldn't be a massive disaster upgrading Moodle. You don't want to be running some ancient version of Moodle without support. Version 3.2 has been completely unsupported for over 3 years.

Re: update version of moodle

$
0
0
by Carlos Cadabeira.  

The point is that apparently the version would be fine, but it does not work.

thank by the ansvver.


Re: update version of moodle

$
0
0
by Carlos Cadabeira.  

You know that the hosting updated me the version of php and now the moodle does not work for me WITH ALL the courses that I have there.

I was running an old moodle 3.2.9.

The point is that when you want to take it to 3.6 it gives me an error.

It gives me a message that confuses me: "Version 7.0.0 is mandatory and you are running 7.4.20

PHP 7.3 is not supported.

You have idea what I can do.

Thanks

Re: update version of moodle

$
0
0
by Howard Miller.  

If you study Visvanath's table you can see that you have to upgrade to the newest version of Moodle 3.8 as your first step. This is the only version that will work with PHP 7.4 AND will upgrade from Moodle 3.2. Once you have that working you can upgrade to long term support 3.9 or even to the latest 3.11 as you wish.

Moodle 3.6 does *not* support PHP 7.4 (as you found)

It could be worse, if you had still been using Moodle 3.1 or earlier you would have had no upgrade path. This is why it's quite important to keep your Moodle version reasonably up to date. 

Re: PHP apache handler and clamAV upload issue, PHP fast-cgi slowness

$
0
0
by tore erotavlas.  

Hi,
I upgraded to php-7.4 via PPA and my problem with clamAV is gone. Moreover, even performance seems better.

Course reports error Exception - Call to a member function out() on null

$
0
0
by Shailesh Todkari.  

Hi
I have upgraded moodle 3.10 to 3.11 with standard procedure every think working fine except course reports like activity, course completion, logs, live logs. When I am trying to access this showing error 

Exception - Call to a member function out() on null
Debug info:
Error code: generalexceptionmessage
Stack trace:

  • line 48 of \lib\classes\report_helper.php: Error thrown
  • line 98 of \report\outline\index.php: call to core\report_helper::print_report_selector()

I had also tried different solutions from forum like purge cache, empty cache and local cache from moodle data but not working.

Thanks in advance.


Debugging after DB Upgrade with MariaDB 10.5.10

$
0
0
by Christe McMenomy.  

I failed to warn my system administrator about MariaDB 10.5.10, and he upgraded the database last Saturday.  We've had a bunch of issues since then, but before I have him downgrade the database, I want to know if anyone else has had similar problems perhaps caused by something else that we will also need to address.

Current system: Linux 5.10.27-gentoo. PHP 7.4.19. MariaDB 10.5.10 (sigh), Apache2.

Issue #1: Student is unable to upload file into assignment, receives "Error connecting to the server" message. On a later attempt (two hours, log out, log back in), upload works without a problem.

Issue #2: Student A attempts a quiz module and receives an invalid course module ID error message repeatedly; student A is unable to submit quiz.  Student B attempts quiz as test while Moodle is in debug mod, and gets this screen:


Student C attempts quiz 8 hours later and completes quiz without any issues.

Now, I could see how a consistent DB error would cause every student to  have a problem, but why can one student attempt the quiz and succeed, after another fails repeatedly? This intermittent behavior has me wondering whether something beside the 10.5.10 MariaDB version is wrong with the environment.  I'd had to roll back without fixing the problem.


Re: update version of moodle

$
0
0
by Visvanath Ratnaweera.  

Yep, the OP is lucky. It could have been otherwise.

Re: update version of moodle

$
0
0
by Carlos Cadabeira.  

OK

the version 3.8  say me the next:


Thank you

I vvill probe vvhit the version 3.5

Re: update version of moodle

$
0
0
by Carlos Cadabeira.  

I do not understand

Re: Upgrade 3.10 to 3.11 why are there changes to commit?

$
0
0
by Michael Knichel.  

Sorry for the delay, I was home and this is all on my work computer.
So I have 3.10.4 not 3.10.4+, why does that matter when I try to upgrade?
When I opened the directory with my development editor (git enabled) it shows that those files have uncommitted changes. I swear I have never edited ANY moodle files (other than config.php). Maybe a plugin I added did that?
Being fairly new to GIT, what do I do to correct this?

When I upgraded from 3.9 to 3.10 I did the same thing on both my dev and prod servers. My prod server is 3.10.4+ for some reason...

Thanks again for all of your help.

MK

Installation's update

$
0
0
by Roberto Catanuto.  

Moodle 3.9.3

Hi I've to update my school's installation from 3.9.3 to 3.9.7.

I read in https://docs.moodle.org/311/en/Git_for_Administrators#Moodle_branch_names that all is needed is:

$ cd /path/to/your/moodle/

$ git pull

Is it the same for installed plugins?, e.g. :

$ cd mod/plugin_1

$ git pull

then

$ cd ../

$ cd mod/plugin_2

$ git pull


The git clone command has already been issued in the last upgrade from 3.5 to 3.9.3

Thank you.




Please help me - idiom error

$
0
0
by Carlos Cadabeira.  

Please help me.

I don´t let me updapting 

Update the image

Re: Debugging after DB Upgrade with MariaDB 10.5.10

$
0
0
by Christe McMenomy.  

gRRR... I would HATE to roll back without actually fixing the problem during the same outage.

Re: Installation's update

$
0
0
by Ken Task.  

One can use git pull with addons *only if* ... *only if* ... the addon code was acquired via git repos for those addons.  Look for a hidden .git directory in those plugin directories.   If not there, plugin was not installed using git.

Other wise a git pull at code root of the moodle acquires *only* ... *only* ... core code.

To update the plugins either use Admin GUI interface for upgrading plugins via Moodle pluginsserver or manually acquire the zip files for the plugins and upgrade manually.

See: https://docs.moodle.org/311/en/Installing_plugins

'SoS', Ken


Re: update version of moodle

$
0
0
by Ken Task.  

That was nasty of hosting provider if they did that without any warnings! :| or did they warn?

Anyhooo ... at this point ... make sure you have a full backup .. downloaded off your server ... that's an archive (tar ball  or zip) of code directory, minimally moodledata/filedir/ (that will be the largest probably) and a dump of the DB for Moodle.

Do you have site backups?

How large are the files ... the tar ball/zip of code is?

The minimal moodledata/filedir/ tar ball/zip of that?

The sql dump of your DB?

'SoS', Ken

Re: Debugging after DB Upgrade with MariaDB 10.5.10

$
0
0
by Christe McMenomy.  

Also: the apache log is showing this error:

Default exception handler: An error occurred while processing your responses (Invalid course module ID). Click continue to return to the page you were on and try again. Debug: \nError code: errorprocessingresponses\n* line 2479 of /mod/quiz/attemptlib.php: moodle_exception thrown\n* line 89 of /mod/quiz/processattempt.php: call to quiz_attempt->process_attempt()\n, referer: https://www.scholarsonline.org/ScholarsOnline/moodle/mod/quiz/summary.php?attempt=58314&cmid=43677. There is a course module with this ID number and it identifies the correct course. Is there a way to map the quiz attempt back to the quiz and the correct course module id? I've been trying to puzzle out the connections but haven't quite figured out how these tables are related.

Re: Debugging after DB Upgrade with MariaDB 10.5.10

$
0
0
by Ken Task.  

In DB there is a table for QuiZAttempts.

mdl_quiz_attempts

Field name    Type    Allow nulls?    Key    Default value    Extras
id     bigint(10)     No     Primary     NULL     auto_increment
quiz     bigint(10)     No     Indexed     0    
userid     bigint(10)     No     Indexed     0    
attempt     mediumint(6)     No     None     0    
uniqueid     bigint(10)     No     None     0    
layout     longtext     No     None     NULL    
currentpage     bigint(10)     No     None     0    
preview     smallint(3)     No     None     0    
state     varchar(16)     No     Indexed     inprogress    
timestart     bigint(10)     No     None     0    
timefinish     bigint(10)     No     None     0    
timemodified     bigint(10)     No     None     0    
timemodifiedoffline     bigint(10)     No     None     0    
timecheckstate     bigint(10)     Yes     None     0    
sumgrades     decimal(10,5)     Yes     None     NULL

The state column ... if student finished the quiz has 'finished'.

Possible fix if you find the right entries.

'SoS', Ken

PHP Upgrade - Fatal error: $CFG->dataroot

$
0
0
by Shawn Peters.  

So were just prepping for some summer updated and I updated PHP from 7.2.32 to latest 7.4.20 release and not Moodle wont boot at all.  Get "Fatal error: $CFG->dataroot is not writable, admin has to fix directory permissions! Exiting." Error.

If I make the PHP v7.2.x files live again everything works perfectly.  What changed in the new PHP version to break this???

Also tried latest PHP v.7.3.28 with same issue.

Moodle is version 3.6.5  on Windows IIS.  Running on MySQL.

Yes the permission on 'moodledata' folder are correct and I even re-applied them just to make sure.  I'm really stumped.

PHP location is the C:\php\  I'm just moving the v7.2 or v7.4 files in/out of that folder to upgrade.   PHPinfo file loads perfectly, just Moodle wont.


Any ideas?  I've been banging my head for 2 days now and haven't gotten any further.


Thanks in advance,

Re: PHP Upgrade - Fatal error: $CFG->dataroot

$
0
0
by Shawn Peters.  

Still no idea what's going on, but put PHP v7.2.34 on the server and had no issues.
PHP v7.3.1 -- fails.... Fatal error: $CFG->dataroot

SO what the heck changed so much in PHP v7.3.x from v7.2
Viewing all 46925 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>