I see that plugin updates are available are available in Notifications, and I see a list of plugins that require updating, but I see only a 'download' link, no 'click to update' as I saw in m3.x. Am I missing something?
I can confirm that the site is officially registered and that the 'Available Plugins' page, which used to show an 'update plugins' button when plugins were available, is no longer showing this button. Instead, it lists the plugins which require an update and provides a 'download' link and a 'more info' link for each plugin.
Cron job/task running ok?
Check admin/settings.php?section=updatenotifications
Also check if there is a update available by going to Moodle plugins directly to see the most recent release of that plugin. Compare with version on your server.
Not saying there isn't a bug ... since we're talking 'latest/greatest' here! :|
I have a m4 highest and haven't needed any updates to any of the sparse plugins I have installed ...
'SoS', Ken
Using a moosh script to check your plugins (shortname),
Add-on listing:
mod_vpl
block_xp
theme_learnr
output of that script shows
Addon in que: mod_vpl
mod_vpl,2.3,2.4,2.5,2.6,2.7,2.8,2.9,3.0,3.10,3.1,3.11,3.2,3.3,3.4,3.5,3.6,3.7,3.8,3.9,4.0,https://moodle.org/plugins/download.php/26716/mod_vpl_moodle40_2022052312.zip
Addon in que: block_xp
block_xp,2.7,2.8,2.9,3.0,3.1,3.10,3.11,3.2,3.3,3.4,3.5,3.6,3.7,3.8,3.9,4.0,https://moodle.org/plugins/download.php/26715/block_xp_moodle40_2022052300.zip
Addon in que: theme_learnr
theme_learnr,4.0,https://moodle.org/plugins/download.php/26709/theme_learnr_moodle40_2022052100.zip
All show a 4.0 version ... even in the zip file name.
Suggest backing up code and DB first.
Then if you have command line, manually upgrading the files in proper locations.
cd mod
mv mod_vpl .mod_vpl - this hides the old code
Then
wget https://moodle.org/plugins/download.php/26716/mod_vpl_moodle40_2022052312.zip
That downloads the zip.
Unzip the zip
unzip https://moodle.org/plugins/download.php/26716/mod_vpl_moodle40_2022052312.zip
should result in a mod_vpl directory ... check ownerships/permissions on folder recursively.
Then install the upgrade via command line.
you are in mod of code so cd ../admin/cli/
Then php upgrade.php
Should see the new code for that mod and upgrades it.
Ditto for the other plugins.
Emma might be right ... if installed with git may not allow upgrad via GUI
'SoS', Ken
Thanks, both. No, they weren't installed with git. These plugins were installed in the previous 3.11.6 and when the upgrade to 4.0.1 took place I didn't do anything special... I'm assuming the upgrade ported these folders auto'magically'.
Thanks, I'm quite familiar with cli and even went so far as to recursively make folders/files 777 and still no joy in the 'plugins overview' page with the 'install update' button.
The eventual plan is to install 4.1 from scratch over summer break, but I still think it's odd that no install button is displayed (given the full permissions on the folders).
Thanks, I'm quite familiar with cli and even went so far as to recursively make folders/files 777 and still no joy in the 'plugins overview' page with the 'install update' button.
The eventual plan is to install 4.1 from scratch over summer break, but I still think it's odd that no install button is displayed (given the full permissions on the folders).
"assuming the upgrade ported these folders auto'magically'"
Uhhh, no ... upgrade is core code only ... no addons. Upgrades to addons moodle handles separately.
Got moosh installed?
Create in your code directory a file called 'addons.txt'
It consist of one-liners with the shortnames of the plugins - seen when viewing additional plugins via the GUI.
Looks like:
filter_wiris
local_mailtest
block_configurable_reports
block_quickmail
tool_userdebug
report_customsql
theme_adaptable
theme_moove
theme_fordson
Next create an executable bash shell script called 'checkaddons'.
Uses moosh to check addons in that list
Looks like:
#!/bin/bash
#
echo 'Add-on listing: ';
cat ./addons.txt;
echo '---------------------';
for i in `cat ./addons.txt`
do
echo "Addon in que: $i";
moosh -n plugin-list |grep $i
done
When run, displays info about those plugins like so:
Addon in que: theme_fordson
theme_fordson,3.10,3.11,3.2,3.3,3.4,3.5,3.6,3.7,3.8,3.9,https://moodle.org/plugins/download.php/24737/theme_fordson_moodle311_2021072100.zip
One can see if doing this with an m4 of moodle, the theme fordson doesn't have a 4.0 update.
'SoS', Ken
Thanks for the PM - have been reading through the cli class... Learned a few things - thanks! I will reference this in a few weeks when using git to install a clean M4.0.X
Back to the issue here, I decided to try to use the GUI (though I can use Cpanel/cli to manually install plugin updates) and so Site Admin -> Plugins -> Install Plugins -> Install Plugin From Zip File... Attempting to upload the latest 'Level Up XP' gives this empty screen (notice the missing 'Install' button). Now, I'm still guessing this is a perms issue (like I said, I even tried chmodding the dir to 777 and still no joy on the previous attempt) but surely this qualifies as a bug... I mean, this screen is a dead-end with no msg about how to continue...
@Garth
In your m4's moodledata/temp/ there is a tool_installation directory.
So see if temp ownerships/permissions are set rwx also assume you have php extension for zip ... php -m |grep zip
Got any web application firewall - WAF - or running mod_security? or running an OS that has seLinux? Is seLinux running as enforcing?
As is usual, might have to turn on debugging to see what else moodle might be complaining about.
'SoS', Ken
I appreciate the thoughts:
It's a strange situation because to my knowledge, the server has not been updated, and it's only when we moved to m40x (possibly automated by softaculous (argh)) that I no longer see the 'Install Update' buttons Though, it's possible a server update coincidentally occurred in the bg. In response to your questions above, on a VPS (I know...) cloudlinux instance:
- moodledata/temp/tool_installaddon is 777
- zip is present
- No WAF that I'm aware of though I am behind cloudflare (have been for years and haven't changed any settings over there)
- seLinux is not running
- mod_security not listed on php_info
- moodle debugging on FULL shows no hints of any issues on the plugin update page
*sigh* Thanks for the help!
'Sigh' is right ... more like ARGGGGG! then several expletive deleted's.
First, there is Softac. That's a commercial addon that your provider bought and is allowing it's customers to use. It is proprietary in that none but programmers of the module for Moodle can do anything about issues that arise from updating/upgrading (it appears to do ok on initial install, but many have found updates - if many hops away moodle version wise - and especially upgrade ... fails. So what Moodle version did you have prior to Softac upgrade to 4.0 (see, Softac can't keep pace ... 4 is now 4.0.1+. What you are experiencing isn't a bug, BTW, don't see that in my 4.0.1+ and there haven't been a bunch of folks saying 'me too!' :|
Question: in your Panel and the Softac initial screen, does it have a link to Softac support or does it have a link to these community forums? If latter, they are dodging - and to me, that's semi criminal.
https://www.softaculous.com/contact
CloudFlare is both content caching and Firewall now-a-days. Mention that because if it considers something to be malicious and blocks, you see ... or don't see ... things.
mod_security isn't a PHP thang, it's an addon to apache - it's a WAF.
Now questions ...
did you do a site backup before upgrading? Minimally, SQL dum of DB and archive of moodle code.
Does your cPanel have a Terminal icon? Does it have a 'Git' icon?
If you trust me, could get into your VPS for a look see - free of charge.
If interested, PM me the particulars ... like login to your cPanel with user/pass creds - offer good only if you have a Terminal icon and a Git icon!
'SoS', Ken
Talking of bugs, Softaculous is one pachyderm. See for yourself: "Re: Issues after Softaculous Moodle 4.0 Upgrade from 3.11.6" https://moodle.org/mod/forum/discuss.php?d=433917&parent=1751210 (came in an hour ago, from the President of Softaculous).
Short message: Why don't you ask in the Softaculous forums?
Which "dir" do you mean? Of course Moodle checks the permissions of $moodledata and refuses to continue if it is not writable or can not be created by the web server. You can break the permission later, which Moodle can't help.
I think you are talking of $moodle/mod/, theme/, etc. which have to be writable by the web server if Moodle to install a plug-in. One more reason not to go the Moodle GUI path to install plug-ins. I never do it on a production site. Always get the source manually, ideally with Git, failing that wget and unzip.
@Garth ... yeah, that would be nice .... but I would imagine difficult to include in Moodle. All resources of a server ... some providers, as an example, have an inode limit ... and busy/used Moodles can push over that limit.
Optimal config of DB server and the DB for moodle is another ... there are docs on the subject, but any investigation of such issues isn't done in moodle code.
'SoS', Ken
Just a follow-up here... I wish I could say what the issue was, but here's how it was resolved:
Using Cpanel's File Manager, I deleted m4.0.1 and the uploaded the latest m4.0.1; I did not re-copy folders for my plugins. When I navigated to myMoodleSite.xxx/admin I was greeted with the standard upgrade the DB menus where moodle discovered that I had DB entries for these plugins and no files. Moodle then asked to install (yes, the button was present) the plugin files and I clicked 'Install' and it worked without issue.
I'm still convinced it was a perms problem but have no idea really what occurred. Thanks all for your help... This summer I"ll install via git and maintain the install that way rolling forward.
Cheers!
~Garth
Using Cpanel's File Manager, I deleted m4.0.1 and the uploaded the latest m4.0.1; I did not re-copy folders for my plugins. When I navigated to myMoodleSite.xxx/admin I was greeted with the standard upgrade the DB menus where moodle discovered that I had DB entries for these plugins and no files. Moodle then asked to install (yes, the button was present) the plugin files and I clicked 'Install' and it worked without issue.
I'm still convinced it was a perms problem but have no idea really what occurred. Thanks all for your help... This summer I"ll install via git and maintain the install that way rolling forward.
Cheers!
~Garth
We have the same problem. When you click the continue button during the installation it just downloads a PHP file, it won't let you continue. We have tried it on Chrome, Opera, Firefox and Edge. We have used a tablet and 2 different PCs. It updated a few weeks ago fine and we have not installed any plugin since. I am wondering if it's an error in the installation part of moodle.
I don't know why there is not an update button for moodle and it updates it like most other systems and then you just install any extra plugins needed. it would be far easier.
We were very lucky in the fact that the upgrade had not happened so we could revert to the previous version but had we got halfway through, we would have been in trouble.
I don't know why there is not an update button for moodle and it updates it like most other systems and then you just install any extra plugins needed. it would be far easier.
We were very lucky in the fact that the upgrade had not happened so we could revert to the previous version but had we got halfway through, we would have been in trouble.
Hi,
I am from the Softaculous team. Did you upgrade your installation via Softaculous and then you started facing the issue ?
If yes please open a support ticket with us :
https://softaculous.deskuss.com/open.php
I am from the Softaculous team. Did you upgrade your installation via Softaculous and then you started facing the issue ?
If yes please open a support ticket with us :
https://softaculous.deskuss.com/open.php
Brijesh, I am wondering if it makes sense to add information about Softaculous in the Moodle documentation for "Upgrading," maybe on this Upgrading web page?
The Moodle community has had a fair amount of questions about problems upgrading via Softaculous.
It could read something like:
"Softaculous is a company that provides "auto-installers" and "auto-upgraders" for Moodle applications hosted on hosted servers and VPS. Softaculous is not the only company that provides automation. For example, another company is Installatron. You can seek help for Softaculous installations or upgrades by opening a support ticket at: https://softaculous.deskuss.com/open.php. However, make sure that you are using Softaculous and not a different product."
I would make this addition, but I thought that I would ask you (and others) about its content and whether this makes sense.
I see that would be at the bottom of that page ... lots to get frustrated about if one cannot get to the beef ASAP.
If one does that for Softac, only fair to do that for all ... Installertron, Direct Admin, some other off the wall product ... that list could be rather long.
I still don't see the need ... the initial screen Softac users see has info below the picklist ... have asked OP to check that out and change it so that first link goes to Softac ticket system. Second link to Community forums .... but, and I don't understand this at all ... OP says he can't do that with 351+ installs ... Huh? What? If there is a need to fix this proprietary non-open source application, how does OP accomplish that? And I do believe there is a need to fix it!!!!
Y'all can do what you want ... I, for one, will never recommend Softac usage for reasons already given ... more than once. But that's no biggy to anyone ... cept those who ask for help and Softac can't!
Again ... no SoS, Ken
The Moodle Docs are a Wiki - feel free to add it yourself...
+20 @Jon's suggestion ...
"Moodle Docs is a dynamic website.
Anyone with a moodle.org account may edit the contents.
As such, we cannot guarantee the accuracy of the documentation nor accept any responsibility for errors that it may contain. If you find an error, please fix it!"
Also see there is a talk page in the wiki (a who done it!)
https://docs.moodle.org/400/en/User_talk:Rick_Jertz
https://docs.moodle.org/400/en/User_talk:Brijesh_Kothari
Would be nice if there were a 'credits' icon next to any addition/edit or that pointed to the 'talk' info.
'SoS', Ken
Rick, did your text in https://moodle.org/mod/forum/discuss.php?d=434830#p1751275 find it way to the upgrading page https://docs.moodle.org/en/Upgrading, which one /XYZ/?