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

Re: Installing Moodle 3.7.1 on GoDaddy

$
0
0
by Rick Jerz.  

Good point, James. So I will add that my GoDaddy VPS is a Linux product, not Windows.

James, I seem to recall that you had worked with GoDaddy a little too, maybe in China. (I might be wrong, however.) But then I recall that you found a server company that worked for you in China. I cannot recall the details. Am I somewhat on target?

Re: moodle upgrade docs are stupid and broken

$
0
0
by Rick Jerz.  

Yes, Todd (to add a little to what Howard has already said), your method could be correct, and it might be one of a thousand ways to upgrade Moodle. But your upgrade method might depend upon the several thousand ways that you installed Moodle. (Moodle is not a PC or Mac installation, its a server installation.)

What I have noticed here on Moodle.org is that folks who manage their Moodle(s), with time, develop their own best practice for upgrading their Moodle based upon the general guideline provided in the Moodle docs. For example, I do not use the "GIT" technique.

I am a small-time Moodle person, <15 courses/yr and <500 students/year. I am not a server-admin. But I have learned much about running my own Moodle, with much help here on Moodle.org. The main thing that I have learned is that running and upgrading Moodle is not as simple as keeping my applications upgraded on my personal computer, and this originally shocked me. However, Linux (UNIX) is not like DOS either.

Problems after 3.6.4

$
0
0
by Barb Hall.  

Hello everyone,

I just recently updated to 3.6.4, and plan to migrate to 3.7.1.  After the upgrade to 3.6.4, I am getting several error messages regarding my email_message.php file.

I've attached pdfs that show the messages in the log, and a copy of my current email_message.php file from my moodle directory

I also have things I should "check", but have no idea how to fix them. Wanted to attach screenshots but am limited to 2 attachments.  

Can anyone suggest what I should do to correct these issues, or would the upgrade to 3.7.1 fix it?

I'm using moodle 3.6.4 Build 20190513

Thanks in advance,

Barb

Multiple Moodles, one WWW directory

$
0
0
by JC SD.  

For years I've been using separate web roots to host multiple Moodle sites and then upgrading and adding plugins separately. Is it possible to combine those into one Moodle directory with the already existing separate Moodle data and databases? Or does something like the caches get messed up? If you can do it, how do you do it? 

Re: moodle upgrade docs are stupid and broken

$
0
0
by Ken Task.  

Process and docs aside, maybe someone should ask ... so I will!   Responses do determine strategy/approach.

What version of Moodle are you currently running?

Have you run, System Admin menu -> Server -> Environment and updated the component (link to update in upper right of Environment panel).   Then use drop down pick list for higher versions of Moodle.  Any 'red' checks?

Server is hosted, but with what hosting service?

Is the account on a shared service/server?

Can you make full user backups of current courses successfully?

'SoS', Ken

Re: moodle upgrade docs are stupid and broken

$
0
0
by Emma Richardson.  

In addtion to the other comments, I would just like to point out that the people you complaining too are just moodle users trying to help each other. And the help docs are a wiki and have so many pages, it is hard for just the few people that work on them to keep up. Help is always appreciated. Git is a much easier way to upgrade once you are up and running. Ken is our resident Git expert and has got me to the point that I can just reference his emails when I get ready to upgrade again(!!) - thanks Ken, BTW.
I have always thought that one simple fix would be to have a custom folder like wordpress where all plugins install too - they we would not have to search through multiple folders to find all those plugins.
A couple of things I noticed - 1. Your moodledata folder should not be in your webroot - Moodle will get to the point of making you move that. 2. It does not matter what the folder is called that moodle is installed in - just change the name to your actual folder when following the docs. 3. Once you get git running, it is just a matter of a few commands to get upgraded and you do not need to mess with your folders etc... 4. Plugins are separate from the moodle code - they can be updated automatically from the plugin page. But you do need to copy all the plugins' folders over to the new moodle code if you are not using git.

Re: After upgrading from 3.5.1 to 3.7.1 cron is not working

$
0
0
by Ken Task.  

Not sure you mentioned this ... but will ask ..

How did you upgrade from 3.5.1 to 3.7.1?

https://docs.moodle.org/37/en/Upgrading#Cron

mdl_logstore_standard_log appears to be messed up!!!

While one could work on repairing that table that might result in discovery of other tables also having similar issue.

So ...

Can you make an sql dump of DB?
If so, do so.

Then create a new DB for your moodle:
character set utf8mb4 collate utf8mb4_general_ci;
Then import the SQL dump you made into the new DB.  Fingers crossed that will result in 'repairing' tables on the fly by creating new ones.

Put site in maintenance mode.

In config.php of code,
duplicate the DB name line.
on the duplicated line, change to new DB and comment out original DB name line
with // in front.

Do same for the DB collation line to set it to new collation used when creating the new DB.

No need to restart anything ... test
Run the php schedule_task.php --execute="\logstore_standard\task\cleanup_task" agin.

Now before doing above, will defer to whatever Howard might suggest.   Howard?

'SoS', Ken


Re: Can't sign in after server move

$
0
0
by Otaku Dude.  

Hi all!

Sorry for the delay in returning to this thread.

I have now managed to get admin access to all Moodles by setting up admin id 2 correctly in the database via MySql Workbook. I then set my 2 colleagues and myself up and ensured that we were all manual auth and siteadmins. Interestingly, we don't all have access to the 4 Moodles, some can log in, some can't. For set the config.php to .....auth='manual'; but it makes no difference for those who couldn't log in. I no longer get LDAP errors, just 'Invalid Login, please try again'. I assume the password stored in Moodle is the one that LDAP would use too?

Ken - the cli was resolved after many hours of googling! It was clear that cli wasn't installed but all the yum install commands didn't seem to work until I tried 'yum install php72u-cli'

So now I can attack the issue from both ends. Is there anything obvious that need to change in the LDAP Moodle settings or configs when moving/archiving a Moodle install?

Many thanks again,

Nige.

Re: Can't sign in after server move

$
0
0
by Ken Task.  

php72u indicates your serve is using IUS repo ... https://ius.io/ for PHP.

yum repolist will show what repos you server will acquire updates from.

https://dl.iuscommunity.org/pub/ius/stable/CentOS/7/x86_64/repoview/

Why it's important you know that ... repos can provide an update that you don't want ... just yet.  Moodle code has not been tested with all latest/greatest yet ... like MySQL vr 8.

On your server it might be wise not to allow those repos to autoupdate.   Set of that beyond the scope of Moodle forums but do suggest you investigate your servers yum and repo setups.


"... the password stored in Moodle is the one that LDAP would use too?"

normally, remote authentications in moodle do NOT store password in moodle mdl_user tables or other authentication tables.  I use Google Oauth2 on several servers and I would not want Moodle to store password in moodle.

"Is there anything obvious that need to change in the LDAP Moodle settings or configs when moving/archiving a Moodle install?"

Networking comes before application ... so if LDAP server is protected by some setting as to what internet servers can access/use it for authentication, then your new moodle (new IP) may not be in an allowed list ... something like that.  LDAP/AD changes so a change to LDAP/AD might/would affect moodle's use of it.  LDAP/AD admins might make a change that inadvertently affects Moodle.  So make sure your LDAP/AD server admin is aware.

'SoS', Ken


Re: How to intergrate moodle with a pulic facing web hosting service like bluehost

$
0
0
by Emma Richardson.  

You can install themes from the plugin interface right through the gui. You then select the theme for the site and configure it how you want. This is all done through the moodle web interface. This does not change with regards to where you host.
So, it says you are using moodle 3.7 but want help installing? Is it installed or not? Can you be more specific?

Re: Can't sign in after server move

$
0
0
by Ken Task.  

Couple of more thought ... if you didn't have php72u-cli installed what about php72u-ldap?

The only reason for setting authentications via config.php was to get around issues with LDAP.   Comment out that line in config.php.  After that, whatever authentications are enabled come into play again.

LDAP authentications enabled? 

There is a CLI script in moodlecode/admin/cli/ called cfg.php.

Execute like : php cfg.php (now that you have CLI).

Look for settings related to authentications.

php cfg.php |grep auth

Your getting closer to resolution now! smile

'SoS', Ken

Re: Multiple Moodles, one WWW directory

$
0
0
by Howard Miller.  

Do you mean one code base for multiple Moodle installs?

It wouldn't be true to say it can't be done because I know it has. However, I think it's pointless complication. What you actually should be doing is maintaining your custom code base using Git. If you do that you just have to upgrade the first one - then commit and push. For all the others it's just 'git pull' and run the upgrade.

Re: Is it necessary to use maintenance mode for small updates?

$
0
0
by Przemek Kaszubski.  

Add something like like:

.maintenancewarning {
background-color:red;
color:white;
}
to /admin/settings.php?section=themesettingboost > Advanced settings > theme_boost | scss

and no user will miss it ;).

Re: Shared hosting for 3.6*

$
0
0
by Artur Fisher.  

Hi! I looked at your hosting comparison site and I think I will choose: BlueHost or FastComet for my tasks.

Re: Exception - Call to member function Moodle 3.7

$
0
0
by Trish Ryans-Taylor.  

Thank you Karina

I have found the plugin. Being new to Moodle not sure what will happen if I delete this. It is currently disabled on my software.

Did you just delete the plugin and were there any other issues after that?

Best regards

Trish



Re: Shared hosting for 3.6*

$
0
0
by James Steerpike.  

I would try a Digital Ocean Droplet rather than shared hosting.  The droplet is a VPS with complete control at root level. Install what you want.

Moodle 3.7.1+ Installation

$
0
0
by Lavanya Lav.  

I tried installing Moodle 3.7.1+ in different browsers (Mozilla, Chrome, Opera). I couldn't proceed with the installation due to the error as in the screenshot. Do anyone faced this technically, looking for your suggestions.

Moodle37


Installing a new theme.

$
0
0
by Minsu Kim.  

Hi everyone,

Please help me to figure out this server issue. 

I installed the latest version of Xampp(v3.2.4) and moodle(3.7) in Windows 10. When I install the enlightlite theme inside the theme folder and press upgrade the database. Then, showed the error message below. 

It was working well before I installed the new theme. 

I only configured a few things in php.ini when I installed the moodle on xampp. 

  • max_execution_time=600
  • http://php.net/xmlrpc-errors
  • extension=intl
  • extension=soap
  • opcache.enable=1
  • Zend-extension = "C:\xampp\php\ext\php_opcache.dll"

Re: Moodle 3.7.1+ Installation

$
0
0
by Howard Miller.  

How did you install Moodle (or... which instructions did you follow)?

Re: Moodle 3.7.1+ Installation

$
0
0
by Lavanya Lav.  

Downloaded the zip file by extracting to localhost. When I try to install from localhost (WAMP), it shows the error.
Viewing all 47119 articles
Browse latest View live


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