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

Re: Correct path to upgrade

$
0
0
by Ken Task.  

@Myrrh ...

The original poster of this thread did have Linux, so the information shared was for Linux.  Am not a Windows person, but the concept is the same.  From your other postings, sounds like you are remotely hosted so do it the way you've done it before (download, unzip, ftpupload, hit notifications of site), but ....

2.x is a massive change from all previous versions of Moodle.  It does more and requires more.  Matter of fact, some folks have found out the hard way their hosting provider cannot provide the supports needed for Moodle 2.  So *before* you try this make sure your hosting provider has the minimum for PHP and MySQL.  From the downloads page: 2.5.1+ Requires: PHP 5.3.3, MySQL 5.1.33.

If they don't have, seek another provider.

Either way you go, there will be a learning curve.  But, that shouldn't deter an educator - it called new learning!  We expect students to do this every day.  Why should educators be 'excused'?

You might consider a different path.  Others have chosen the following and they may have had some issues depending upon their 1.9 site/courses.  If, however, you have been using a 'stock' Moodle (no addons/no special themes, etc.) then the chance for issues are less.

Backup all of your courses in the 1.9.  Download those backup zips.

Install a fresh 2.5.1+ and get it up and running. 

Restore the backups.

This will not bring students accounts into the new site but one can still use bulk user upload.  Since no accounts, it's logical that restoring 1.9 backups will not include any student work ... ie, assignments they turned in or quiz/test they took, but the Assignments are there as well as the quizzes/test.  Therefore it's probably best to do this in between online sessions with students (end of semester/grading period, etc.).

Maybe there's a Windows person out here in Moodle land that can jump in here or provide a link with info.

'spirit of sharing', Ken

 


Re: Git pull question - commit or stash how to?

$
0
0
by Jerry Lau.  

I think I figured it out now ...

git commit -a -m 'merge branch first time'

then git pull

 

 

 

 

Re: How to upgrade from 1.9.13 to current stable version

$
0
0
by Rob Bright.  

Upgrading Moodle is a very easy and painless process if you have backed everything up.

First, back up the mysql database, via a mysql dump such as

mysqldump -u username -p password moodlebackup.sql < moodle

where the username is your mysql username and the password is the password of the mysql user. The database might be named something different but that is the general syntax.

Next, back up the moodledata folder, either by terminal with the syntax being

tar -xvcf moodledateMMDD.tar.gz /moodledata

where MM and DD are months and dates respectively.

Once you have done this, then rename the moodle installation by using

mv moodle moodle.backup

This will rename the current installation of Moodle, ensuring you have a back up just in case things go wrong.

Then, using filezilla, bring over the new Moodle installation you want, in this case 1.9.19, then move the config.php file over, either using FileZilla or terminal

cp moodle.backup/config.php moodle/

And it should be ok to go. This is a safer way then using the drag and drop of files as sometimes the code is different and get the bugs...

Re: How to upgrade from 1.9.13 to current stable version

$
0
0
by Guillermo Madero S..  

Hi Myrrh,

Yes, you can go directly to 1.9.19. The basic upgrade process is actually easy.

  1. Download the latest 1.9.x package.
  2. Check for non-standard plugins & filters in your current installation. If there's a new version for them (for the latest 1.9.x), download them too.
  3. Backup everything (database, and the moodledata and moodle directories). If you have phpMyAdmin installed, you can use it to create your database backup.
  4. Put your site in maintenance mode and log off.
  5. Rename your moodle installation folder (e.g. moodle-1913).
  6. Unpack the new version. This will create a "moodle" directory. If your original installation was named differently, rename the new directory with the original name.
  7. If you downloaded new versions plugins or filters, unpack them where they should be.
  8. Copy the config.php file from your original installation into the new one.
  9. Open your Internet browser and go to the address of your Moodle site. This will start the upgrade process. In principle, it should end without issues.
  10. Once it has finished, log in, disable maintenance mode and check that everything is working fine.
  11. I would recommend you to create a new full backup.

Eventhough I have briefly described the required steps, please check everything you do against the documentation page.

At this point you'll have covered one third of the way smile

---

Now it would be a good idea to check and prepare your new installation for the next upgrade:

  • Convert your database from myisam to innodb (browse to: http://yourdomain/admin/innodb.php).
  • Check that your database and tables are in UTF-8; convert them if not.
  • Enable password salting.

You could spend some time working with the new version, making sure that everything is working fine and getting familiar with the documentation pages to upgrade to Moodle 2.2: 

  1. Upgrade to 2.0.
  2. Upgrade to 2.1.
  3. Upgrade to 2.2.

Because eventhough you can go directly from 1.9.19 to 2.2, you need to be familiar with the different requirements of each intermediate version, speaking of which, the following are the minimum requirements for each Moodle version:

  • Moodle 1.9.19 -- PHP 4.3.0, MySQL 4.1.16
  • Moodle 2.2.11 --PHP 5.3.2, MySQL 5.0.25
  • Moodle 2.3.8 -- PHP 5.3.2, MySQL 5.1.33
  • Moodle 2.5.1 -- PHP 5.3.3, MySQL 5.1.33

Cheers!

Re: How to upgrade from 1.9.13 to current stable version

$
0
0
by Myrrh Lynn.  

Thank you for the step-by-step! I have successfully upgraded from 1.9.13 to 1.9.19. Easiest upgrade EVER!

In light of all of the other things that have to be done to upgrade to 2.4 or 2.5, would it be better to just start with a clean install with 2.5? I honestly do not know what some of the things are that you named. The idea of messing with the mysql or server databases is daunting to me.

What would happen if I started with a clean install? Is it possible to import the course and user information from 1.9 directly to 2.4 or 2.5?

Re: Git pull question - commit or stash how to?

$
0
0
by Tim Hunt.  

Well, before merging or committing anything, it would have been a good idea to find out what changed.

git status

git diff

would have shown you that. If the changes were trivial, you could have removed then (git checkout badges/lib/backpacklib.php) instead of committing them.

Anyway, you got your problem solved.

Re: How to upgrade from 1.9.13 to current stable version

$
0
0
by Guillermo Madero S..  

Hi Myrrh,

Congrats!! smile

Did you make a full backup of your new installation?

You could actually do a clean 2.5.1 install, however, there are still two problems with this:

  1. You cannot avoid dealing with the minimum environment requirements for Moodle, that is, having a new PHP and a new mySQL version installed.
  2. Backup user data from version 1.9 cannot still be restored into 2.5. Only course contents are restored.

I imagine that "the things I named" that worry you are those I listed after the three dashes? Well, we can work with each one a step at a time.

Can you find out what PHP and MySQL version do you have installed? It would be also good to know what web server (Apache, IIS) and what operating system (Windows, Linux, Mac?) do you have, and their version numbers, too.

One last question (for the time being smile), do you have phpMyAdmin installed?

--- edit

Sorry, I had forgotten about checking your profile to see about the environment you have installed...

Windows 7
Webhost server... ¿which one?
Php 5.3.14
MySQL 5.5.29

Well, good news (very good news, actually), you don't need to change/upgrade anything in your setup! Yes 

Re: FAILED Upgrade from 1.9.19 to 2.0.10

$
0
0
by Guillermo Madero S..  

Sure thing! I know the feeling when things do not look bright, but fear not smile

Good thing you took a break and went to run.

Before getting into the moodledata files, isn't there anything else you can download and delete?


Re: FAILED Upgrade from 1.9.19 to 2.0.10

$
0
0
by Guillermo Madero S..  

Hi Myrrh,

I'm opening a new branch here, as the other one is getting too narrow.

Instead of deleting files from the moodledata directory, you should download it via FTP.

Do you have a control panel where you can see the space used by:

  • the moodle directory
  • the moodledata directory
  • the other moodledata directory
  • the database

Knowing this would help a bit.

Re: FAILED Upgrade from 1.9.19 to 2.0.10

$
0
0
by Myrrh Lynn.  

Taking a look BRB.

Re: FAILED Upgrade from 1.9.19 to 2.0.10

$
0
0
by Myrrh Lynn.  

OK! Now I'm below the backup limit. (Will delete other stuff later)

Here is a screen shot of the files in the website.com file. All of the backup files have been moved to computer C:/

This is what I can see. Along with the phpMyAdmin dashboard, which I assume is standard for everyone. As for an anctual moodle control panel, I do not have such - that I am aware of.

 

 

 

Re: Username and Password issue after migration

Re: FAILED Upgrade from 1.9.19 to 2.0.10

$
0
0
by Guillermo Madero S..  

I've just noticed that the site and the moodle site are down.

Re: Changing URL / Move Moodle to a new site / Not sure what to ask

$
0
0
by Ken Task.  

The reason you might not be able to find an answer to this specific question is that it's not really a moodle migration, but a domain name change - if I understand you correctly ...

abcwebsite doesn't need to exist or be running anymore and you want the Moodle you have to be accessed by xyzwebsite, is that correct?

If that is correct, using what tools you have for domains/DNS, change it.

The only thing you'd have to do in Moodle then is to edit the config.php file replacing oldsite with newsite.

And then login to the Moodle and run the search and replace tool ... search for the FULL URL: http://oldsite/[moodle]/ (including trailing slash) and replace with FULL URL: http://newsite/[moodle]/

Include [moodle] above IF you ran your site in a moodle directory.

If I am in-correct, please describe/correct.

'spirit of sharing', Ken

2.0.10 upgrade message 'You are not logged in. (Login.)' Doesn't work

$
0
0
by Myrrh Lynn.  

(Click on my name for my environment and specs)

I'm trying to upgrade from 1.9.19 to 2.0.10.

Uploaded to server went back to my website and found this: The top 2 links do not work. I WAS logged into my website. Something with the upgrade unlogged me. I clicked on the Login link below, but it doesn't work. Should I click continue or is something going wrong?


Re: 2.0.10 upgrade message 'You are not logged in. (Login.)' Doesn't work

$
0
0
by Myrrh Lynn.  

I clicked continue anyway. The Login button still didn't work. Not sure if I have to be logged in to continue with the upgrade.

Now I am at the Plugins checklist. I have some non-standard plugins BUT I cannot find an upgrade for 4 of them. So I cannot upgrade them before continuing with the upgrade. What do I do?

Re: Changing URL / Move Moodle to a new site / Not sure what to ask

Re: Changing URL / Move Moodle to a new site / Not sure what to ask

$
0
0
par Ken Task.  

@Guillermo - yep, new information always throws another kink into it.  You weren't wrong nor in-correct.

@Joseph ...

If your system (yet to be disclosed) is such that you are in full control of everything (ie, have access to the apache config file and the virtual apaches you appear to be running), then your summation might be a little correct/incorrect.  If you upgrade the moodle at abcwebsite.com then there is no reason to 'install' a moodle at xyzwebsite.com, is there? One just needs to move that which has been upgraded into the domain space of the other and make edits to config.php.  Then decommission the other.

IF, however, you are remotely hosted on a shared system, the provider may have setup virtual apaches that are tied to a domain name ... ie, path might be something like /home/customerZZZ/abcswebsite.com/public_html/ and /home/customerZZZ/xyzwebsite.com/public_html/

While customerZZZ does have access to both web spaces, there is no tool to 'move' data folder/code folder for abcwebsite.com into the proper location for xyzwebsite.com AND rename them.  Not without having to archive them, download, then turn around and upload to the 'other' space.

Thus, it is 'sorta' a migration and would involve moving the data directory, moving or upgrading the code directory, importing the db from the export of the original site, changing the config.php file, and running search and replace on the DB for olddomain replacing with newdomain as well.

Think I'd pose the same question to the hosting provider and see what they say.

'spirit of sharing', Ken

Admin

$
0
0
par bulent ikinci.  

admin yönetimi pasif

Re: Admin

$
0
0
par Guillermo Madero S..  

admin "passive management"... in case anyone wonders...

Viewing all 47233 articles
Browse latest View live


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