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

Re: CSS not working

$
0
0
by Visvanath Ratnaweera.  

Hi Ken

> Issue: CentOS 7 which has reached EOL.

True that CentOS has reached EOL. Still, it was long in use and very stable. It is impossible that CentOS 7 died with leaving such a grave bug unpatched. What OP has observed is that Apache Prefork MPM provided PHP path info, but not MPM nor Event MPM.

The problem must be in the myriad of configuration parameters in these modules or other "security" enhancements. Of course I am guessing, my RedHat times were in the stone age. No CentOS, no Fedora then.

Re: This plugin is already installed on the site

$
0
0
by John D.  

I guess because of the above, my site is in the maintaining mode (see https://moodle.org/mod/forum/discuss.php?d=460859#p1850733), and I'm unable to follow
https://docs.moodle.org/401/en/Installing_plugins#Uninstalling_a_plugin

I.e., there's no way for me to get to the
Administration> Site Administration > Plugins > Plugins overview

Besides, the Uninstall link was not there initially.

So I did the next step, "Use a file manager to remove/delete the actual plugin directory as instructed"

Now I see it in red, saying: Additional Missing from disk!
 
I give up fighting, as I think as of now, the easiest way to fix my problem is to restart everything from scratch.
 

Re: CSS not working

$
0
0
by Ken Task.  

We all know the devils are in the details.

OP said he know all that ... had all that configured ... and still not working, soooooo

I wonder ... that apache link I shared

https://httpd.apache.org/docs/2.4/mod/worker.html

did have a section on sample config and it is very detailed.

Yes, CentOS 7 was probably patched to the hilt ... but still EOL is EOL!   Am still wondering ... Why?

So think I'll go back to the present and near future and get on with my life!   Wishing the OP all the best!

'SoS', Ken

Re: Git upgrade of 3.9 LTS final gave me 4.1.7 LTS (not 4.1.11+) (SOLVED)

$
0
0
by Visvanath Ratnaweera.  

Hi Ken and Leon

Yes, missing 'git fetch' after somewhere December 2023 is the culprit. I thought of this possibility but was too late after I did a 'git pull'. 
 
Now dug up an older backup and it lists the missing commits. Matter SOLVED. Thanks for helping to solve the "mystery".
wink
 
$ git branch
  MOODLE_31_STABLE
  MOODLE_32_STABLE
  MOODLE_33_STABLE
  MOODLE_35_STABLE
  MOODLE_38_STABLE
* MOODLE_39_STABLE
  master
$ git pull
remote: Enumerating objects: 62044, done.
remote: Counting objects: 100% (24945/24945), done.
remote: Compressing objects: 100% (28/28), done.
remote: Total 62044 (delta 24921), reused 24934 (delta 24917), pack-reused 37099
Receiving objects: 100% (62044/62044), 22.39 MiB | 22.75 MiB/s, done.
Resolving deltas: 100% (46654/46654), completed with 5442 local objects.
From git://git.moodle.org/moodle
   86716dc1201..7f450dcea36  MOODLE_401_STABLE -> origin/MOODLE_401_STABLE
   86a0b876586..efce12bb63d  MOODLE_402_STABLE -> origin/MOODLE_402_STABLE
   fe8d759b175..431f27e7bfc  MOODLE_403_STABLE -> origin/MOODLE_403_STABLE
 * [new branch]              MOODLE_404_STABLE -> origin/MOODLE_404_STABLE
   a891866cbd1..8a6e8563fdc  main              -> origin/main
   a891866cbd1..8a6e8563fdc  master            -> origin/master
 * [new tag]                 v4.1.10           -> v4.1.10
 * [new tag]                 v4.1.11           -> v4.1.11
 * [new tag]                 v4.1.8            -> v4.1.8
 * [new tag]                 v4.1.9            -> v4.1.9
 * [new tag]                 v4.2.5            -> v4.2.5
 * [new tag]                 v4.2.6            -> v4.2.6
 * [new tag]                 v4.2.7            -> v4.2.7
 * [new tag]                 v4.2.8            -> v4.2.8
 * [new tag]                 v4.3.2            -> v4.3.2
 * [new tag]                 v4.3.3            -> v4.3.3
 * [new tag]                 v4.3.4            -> v4.3.4
 * [new tag]                 v4.3.5            -> v4.3.5
 * [new tag]                 v4.4.0            -> v4.4.0
 * [new tag]                 v4.4.0-beta       -> v4.4.0-beta
 * [new tag]                 v4.4.0-rc1        -> v4.4.0-rc1
 * [new tag]                 v4.4.0-rc2        -> v4.4.0-rc2
 * [new tag]                 v4.4.1            -> v4.4.1
Already up to date.

Re: Git upgrade of 3.9 LTS final gave me 4.1.7 LTS (not 4.1.11+) (SOLVED)

$
0
0
by Ken Task.  

Moodle is moving origin from 'master' to 'main'.

a git branch -a

Should show at the top as main not master.

To rename your local branch:

git branch -m master main

should reset that to main.

'SoS', Ken

Re: Upgrading from Moodle 4.0.4: Need Advice on Intermediate Steps

$
0
0
by Feki Pangestu Wijaya.  

Correct me if I am wrong, from what I understand from the table, if I update to version 4.3, I need to update from version 3.11.8 first. Additionally, if I want to update to 4.5 later, I would need to downgrade to 4.1.2 (latest LTS) first. Is that correct?

Re: Upgrading from Moodle 4.0.4: Need Advice on Intermediate Steps

$
0
0
by Feki Pangestu Wijaya.  

Yes, on my dev server, my Moodle 4.0.x is running on PHP 8.1 without issues so far. However, I understand that Moodle 4.0 is not officially compatible with PHP 8.1, and it’s only a matter of time until I encounter problems.

Thank you for pointing me to the "PHP max." column in the table and the upgrading documents. I will review these resources to ensure a smooth upgrade process.

Re: Upgrading from Moodle 4.0.4: Need Advice on Intermediate Steps

$
0
0
by Visvanath Ratnaweera.  

> if I update to version 4.3, I need to update from version 3.11.8 first.

I changed the wording of the column to "Earliest from". Hope it is clearer now. To jump straight to 4.3 you need a 3.11.8 or _higher_. See http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases.

The official release notes are linked from each version in the first column. You can double check.

> if I want to update to 4.5 later, I would need to downgrade to 4.1.2 (latest LTS) first

No! Same answer as above. Only releases 4.1.2 (LTS) and later can jump straight to 4.5 LTS.

Re: Upgrading from Moodle 4.0.4: Need Advice on Intermediate Steps

$
0
0
by Ken Task.  

Mr. V's chart is excellent info, but you have a tool on your server right now with which you need to familiarize yourself.   Now and during/after upgrades as a reminder.

Login as Site Admin, then to go Server Environment.

On the Environment Screen - update the component - link in upper right hand corner of that screen.

Then in the moodle version drop down list which shows your current version first, choose each moodle version higher that what you have.

The screen will refresh and show environment info.  

That will show your current versions of PHP + extensions as well as your current DB version.

Be sure to scroll to the bottom of that screen each time as there is sometimes additional information that must be addressed.

Greens means server environment checks out - all is good.

Yellows means you should investigate follow recommenations for optimizing your server environment.

REDS - you  MUST address before attempting upgrade to the version in the drop down list.

All of that is core ... what it doesn't check are addons - additional plugins - and theme compatiblity if you are using a third party theme for your site.

For theme suggest you force your site to use boost via config.php file by adding a line to config.php above the comments at the bottom:

$CFG->theme='boost';

That will force the site to use a stock theme that comes with every newer version.  After upgrading one of the things you need to do is check notifications to see if there is a link to update/upgrade plugins.

Strongly advise getting those updates to the plugins.

The addon plugins you have to check by going to

https://moodle.org/plugins/?q= 

and finding what you have currently installed to see if there exist a compatible version.

And a comment about that: if an addon doesn't have a version you need for the upgrade, my take on that ... plugin goes (un-install it) for that one plugin might be a blocker to upgrading.

And one more piece of advice ... don't get in a hurry ... be slow and methodical.   It's not important how fast, but it is extremely important to be correct!

'SoS', Ken

Botched Upgrade to Moodle 4.4 - problem with /course/format/renderer.php

$
0
0
by P L.  

Hi everyone,

My workplace has upgraded one of their Moodle platforms to 4.4 and since then, when trying to access any course, I encounter this error:


I am only an admin for this platform so I only have access to the web interface. Here is what I have done so far, based on similar topics:
- Enabled maintenance mode and debugging
- Had ICT edit config.php so as to force Boost theme, since another error would be thrown when trying to access the page 'theme selector'. I completely disinstalled the two custom themes we had
- Asked ICT to remove this 'course/format/topics/renderer.php' file which seemingly is not supposed to be included in Moodle 4.4 and was probably restored from backup, but they put it back for some reason
- Checked "Environment". Everything is OK, PHP version is 8.1+
- Checked all updates available, including for plugins. Everything is up to date

Our only additional plugins are mod_choicegroup 1.45, block_admin_presets 3.4, filter_multilang2 2.0.1, enrol_apply 3.9-a, local_boostnavigation v3.11-r1, local_mailtest 3.1.6, local_pages v.19, local_profilecohort v3.10-r2. But I suspect this is something not related to any themes or plugins. I cannot even access Server > PHP Info (line 14 of /admin/phpinfo.php: Error thrown) and probably many other parts I am not aware of. My guess is that our current version is not really completely up to date, but from web interface I have limited control.

Can anyone advise on the next steps I should take to solve this? I would be very grateful. I have no idea what to do and need this platform to work. 

Re: Botched Upgrade to Moodle 4.4 - problem with /course/format/renderer.php

$
0
0
by Luis de Vasconcelos.  

The message says that the error is triggered when Moodle tries to open the /course/format/renderer.php file. Does that file exist in your /moodle/course/format directory? If not, then there's something wrong with your Moodle installation. So, first get ICT to check that ALL the Moodle files were correctly uploaded to your Moodle directory on the server. While they're busy with that, they should check the folder permissions too.

Re: Git upgrade of 3.9 LTS final gave me 4.1.7 LTS (not 4.1.11+) [SOLVED]

Re: Botched Upgrade to Moodle 4.4 - problem with /course/format/renderer.php

$
0
0
by Leon Stringer.  

- Asked ICT to remove this 'course/format/topics/renderer.php' file which seemingly is not supposed to be included in Moodle 4.4 and was probably restored from backup, but they put it back for some reason

That's the cause of this error. It looks like you not only have this file but you have the Moodle 3.11 version. When upgrading Moodle it's crucial that removed files are not present. The file course/format/topics/renderer.php must be removed for Moodle 4.4 to function.

Re: Botched Upgrade to Moodle 4.4 - problem with /course/format/renderer.php

Re: Upgrading from Moodle 4.0.4: Need Advice on Intermediate Steps

$
0
0
by Visvanath Ratnaweera.  

Ken, thanks for reminding me that the Site administration > Server > Environment has a drop-down list.

Caution to the new comers: That information does not get updated once version is no more supported. So you won't find Moodle 4.5 LTS in the drop-down list in Moodle 3.10. I imagine, LTS to LTS is supported: You may ask 4.1 LTS about 4.5 LTS.

Ri: Re: Botched Upgrade to Moodle 4.4 - problem with /course/format/renderer.php

$
0
0
by P L.  

Thank you. I checked again how the Moodle 4.4 directory should be and there is no 'course/format/topics/renderer.php' file there. My guess, after reading the Upgrading tutorial linked by Visvanath Ratnaweera below, is that IT did not read the 'Move your old Moodle software program files to another location. Do NOT copy new files over the old files.' part, and we ended up with a mix of Moodle 3.11 and 4.4. I will ask IT to try repeating the whole upgrade.

Ri: Re: Botched Upgrade to Moodle 4.4 - problem with /course/format/renderer.php

$
0
0
by P L.  

Thank you; IT mentioned 4.2.8 as being the previous Moodle version, but another answer mentions we probably have the 3.11 version of this renderer.php file... I will ask for the whole upgrade to be attempted again.

Re: Ri: Re: Botched Upgrade to Moodle 4.4 - problem with /course/format/renderer.php

$
0
0
by Visvanath Ratnaweera.  

Coming from 4.2 or from 3.11 makes a difference between go or no-go. A straight jump to 4.4 is possible only from 4.1.2 or higher! (see the chart and the official release notes linked in the first column)
 
OK, the statement could also mean that you were on 4.2 but it still had this renderer.php from 3.11. Which means the upgrade to 4.2 has also been done by copying the 4.2 code over the previous (3.11?) code. Better start with a fresh download of 4.4 code or, even better, by cleaning the present 4.2 by replacing the messed up code with a fresh download.
 
BTW, do you know that Moodle also releases LTS versions every two years? 4.1 and 4.5 are LTS. See https://moodledev.io/general/releases.

Re: Upgrading from Moodle 4.0.4: Need Advice on Intermediate Steps

$
0
0
by Ken Task.  

Don't have an older version to check anymore.

If the drop down list doesn't cover higher versions that the site cannot upgrade to then there is another area that needs to do the same.

Notifications screen.

That should not show higher versions of moodle with a download button that the server cannot support.   The button should change to a link for server environment check to verfiy.

As long as I am 'mini-ranting' ... one more link provided on Notifications screen - a link to moodle docs on how to perform a site backup - which is the first step before attempting update or upgrades.

Now before someone suggest I post something in 'improvements' ... been there - done that - went no where! sad

'SoS', Ken

Re: Moodle 4.4 upgade - Edumy Theme

$
0
0
by Abhi Arora.  

@Duncan Thanks for letting me know. I'll contact the bank and try to get it sorted from their end. We are working with the official Moodle devs. and even they have no idea who these people are. I have recommended they try to put a word out to potential users and warn them about this issue as it's Moodle's name that is being used to sell a product that doesn't work.

@Ahmed You should look into doing the same and contact the bank. Good luck!

Viewing all 46820 articles
Browse latest View live


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