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

Re: upgrade to PHP 7 - Moodle 2.2 client issue

$
0
0

by David Le Blanc.  

Thank-you for your post Marina. I have put that particular Moodle back to PHP 5.6 and restarted the server. Unfortunately, I am still unable to login. I receive the same error. sad


Re: upgrade to PHP 7 - Moodle 2.2 client issue

$
0
0

by Rick Jerz.  

I am not an expert at these things, but I thought I would jump in and maybe jog a few ideas.

So, prior to updating to php 7, this one site worked.  Right?

Then you upgraded to php 7, got the error.

Then you went back to your previous php version, and still get the error.

I see a 404 website error.  This usually means that a webpage is not found.  If you go into ssh, have you verified that the file really is there?  Is moodle really there?

Have you tried access other webpages at /~bol?

Re: 回應: Re: Upgrade 2.7 Antelope to Barracuda

$
0
0

by Stuart Mealor.  

First step would be pay attention to the first indicator - that the Maria Database is not at the required level.

It's very clear that you need to update that as your first step smile

Operation : Upgrade PHP

$
0
0

by John Pap.  

Hello,

I have Moodle 3.3.1 and I'd like to upgrade to 3.4.+

How to upgrade PHP with MAMP ? It requires at least PHP 7.

* What I made : copy - paste the old config.php file to new Moodle folder and I get the message to upgrade PHP, during the installation.

I can't find any easy way to do that. Any suggestions ?

Thanks

Re: Operation : Upgrade PHP

Re: Operation : Upgrade PHP

$
0
0

by John Pap.  

Thank you, I tried the steps but I get :

Fatal error: $CFG->dataroot is not configured properly, directory does not exist or is not accessible! Exiting.

Re: Operation : Upgrade PHP

$
0
0

by Howard Miller.  

Unfortunately, I've never used MAMP (even though I do use a Mac). I think there are others around here that have. 

How to setup moodle testing environment ?

$
0
0

by gurpreet singh.  

I am trying to develop Moodle plugin in github . I would like to know how to setup the testing in Moodle environment . It would be great help if you explain in steps . I have read about the PHPUnit and Behat but how I make it use in moodle plugin development ? 

Do I need to install plugin in every code changes ?  


Re: Operation : Upgrade PHP

$
0
0

by Ken Task.  

/Applications/MAMP/data/ is the location of moodledata directories

One could have multiple moodles available so the data directory you create manually might need to reflect the version of Moodle you are installing/working with.   Example as a user that could sudo and the version of Moodle is a 3.4:

cd /Applications/MAMP/data/

mkdir moodle34data

* might have have to use 'sudo' in front of command above depending upon how one is logged on.

Then, in the config.php file of the moodle34,

$CFG->dataroot  = '/Applications/MAMP/data/moodle34data';

Qualifications for this response ... don't use MAMP very often, but above should get you there or at least close. ;)

'spirit of sharing', Ken



Re: Operation : Upgrade PHP

$
0
0

by John Pap.  

Thanks Ken,

apologies but I don't have any folder 'data' in MAMP.

Should I create one ? If so, what to put inside ?

I did copy-paste the folders with names 'db' and 'htdocs' into the new MAMP folder, still get the error.


Re: How to setup moodle testing environment ?

Re: Operation : Upgrade PHP

$
0
0

by Dan Bennett.  

Do you have a $CFG->dataroot setting in your config.php currently? If so - what is it set to? This will be the directory Ken is talking about.

smile

Re: Operation : Upgrade PHP

$
0
0

by John Pap.  

Hi,

I tried many combinations, below it is the default configuration :


$CFG->dataroot = '/Applications/MAMP/data/moodle31';

* I tried moodle34 as well.


Re: Operation : Upgrade PHP

$
0
0

by Ken Task.  

So did you follow the blogs directions or not?

When you messed with the 'db' directory you were really getting what might have been an older version of MySQL with it's settings as well as the databases (including the DB for the moodle).   Would think, but not checked. the newer version of MAMP would have the require versions of PHP and MySQL both in the installer.

At this point, I'm not at all certain of what I tell you to 'fix it'. :\   Not capable of Vulcan Mind Melds!

If you put everything back, does MAMP launch?

How to change PHP versions:

At this page:

https://www.mamp.info/en/downloads/

It shows a column on the right for PHP versions .... among them: 7.0.x's and 7.1.x's (BTW, think I'd stick to the highest 7.0.x rather than going to 7.1.highest right now.   That suggest one can keep the core MAMP in place and just upgrade the PHP.

BTW, the DB for your current moodle is actually in MAMP/db/[nameofdb] ... I have a older MAMP that has a moodle28 and a moodle29 ... those are the names of the DB's that match the separate code directories in MAMP/htdocs/ (a moodle28 and a moodle29).   The config files for those two point to their own respective data directories in MAMP/data/ I have a moodle28data and a moodle29data directory which is mapped via the datadir variable in the config.php file of the sites.

IF you going to copy files to move databases, do NOT use the DB directory ... just the folders containing the files for the moodle DB's.

Also check out the MAMP directory from the command line.   You should find a .sh script ... mine has a UpdateMoodle28.sh because I started with the 28 version.

That script can be edited using nano and actually upgrade the one Moodle to higher verisons of Moodle by 'side loading git acquired Moodle code' ... add a liine or two and one could backup the code, the data directory, and the DB just prior to upgrading.   The script runs moodlecode/admin/cli/upgrade.php so one could upgrade without ever having to use the apache interface.

'spirit of sharing', Ken



Re: Operation : Upgrade PHP

$
0
0

by Rick Jerz.  

John, I use MAMP quite frequently as my experimental moodle.  Ken is correct about the default place where the "moodledata" folder resides.  In my MAMP, my config.php points to:

'/Applications/MAMP/data/moodledata3';

But the moodledata folder could be almost anywhere.

Did you have MAMP working fine prior to upgrading php?  How did you upgrade?  I have found upgrading MAMP a little tricky (I am a novice at these things.)

If you can get to your moodle folder, look at what is in $CFG-dataroot.  Then see if you can find this fold using your Mac's Finder.



Re: Operation : Upgrade PHP

$
0
0

by William Stewart.  

Rick, Just wanted to add that in the past when upgrading MAMP, it has been notoriously bad sometimes and I've had to simply uninstall it completely, install a fresh MAMP, and then reload our Moodle site even when everything was "set up correctly" prior to and after the upgrade! I find great great value in the software, but the upgrading needs some work smile.

Re: Operation : Upgrade PHP

$
0
0

by Rick Jerz.  

Yep William, exactly what I did.  I might do this again now that I am running php7 and Moodle 3.4 on my production server.  My current MAMP is at php 5.6, and yep, do I struggle with upgrading it or just reinstall MAMP?

I really want php 7 and MariaDB on my local Mac.  But the last time I looked, MAMP doesn't provide MariaDB.  I also installed the latest XAMPP, but this didn't work because the intl php extension was missing.  What I might do is install a new MAMP, and see if the mySQLdatabase will import a MariaDB database from my production moodle.

I do have XAMPP running on a virtual PC, with php7.1, MariaDB, and Moodle 3.4, which mirrors my production moodle.  But I would prefer not to have to boot up a virtual PC.

Seems like I should be able to get everything working with MAMP, but I haven't had success.

Re: upgrade to PHP 7 - Moodle 2.2 client issue

$
0
0

by David Le Blanc.  

Thank you Rick. I think it may have something to do with the SSL certificate. I am afraid that I am little out of my depth. Everything is still there. In fact, after trying to connect and the aforementioned error page was displayed, I went to my browser's URL bar and removed the 's' from https I see the crippled version of the login page shown below. Of course, I am unable to login using http instead of https.

Here's a link to the URL: http://server2.time2evolve.net/~bol/moodle/login/index.php (opens in a new tab or window)


Re: upgrade to PHP 7 - Moodle 2.2 client issue

$
0
0

by Rick Jerz.  

When I click on the link, it looks to me like it is missing Boost's CSS.  Try switching the theme to More.  If this displays fine, then we need to ask more questions.  Also, try clearing the cache (Admin/Development/Purge Caches).  You might try clearing the cache even before trying More.

You might also have an SSL issue.  In your config.php file, is the site defined as https or http?

I too am not an expert with some of these issues, but maybe Ken, Howard, or others will see the problem.  The odd thing is that you say your other sites are working fine.  Are all of the sites running the same theme and add-ins?


No forum post get send as email ....

$
0
0

volgens werner cyrmon.  

I have 2 moodle 3.4 server with the latest updates. On both, messages posted in a forum can be seen only if logged in  a course, but will not be sent out as email to the users of the course.

If I start the correspondig cron job by hand (from the server part of the website configuration page) I get:

Execute scheduled task: E-Mail-Versand aus Foren (mod_forum\task\cron_task)
... started 09:55:51. Current memory use 6.8MB.
... used 3 dbqueries
... used 0.055963039398193 seconds
Scheduled task failed: E-Mail-Versand aus Foren (mod_forum\task\cron_task),Fehler in der Kodierung gefunden, den nur ein Programmierer korrigieren kann: Function cron_setup_user() cannot be used in normal requests!
So any ideas what could be wrong ? Outgoing mailserver is correctly configured and reachable ....

Regards

Viewing all 47362 articles
Browse latest View live


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