Posts made by Usman Asar

Ken, dont call it WAS, it is, and WILL be. The original author Julian is back, and together with Gareth, they'll cook some sauce.

Gareth though has worked with Adaptable theme as well, which as I type is most downloaded theme, BUT it may not strike you as a competent alternative of Essential, so why not have a look at the most downloaded plug-ins for the year (https://moodle.org/plugins/stats.php), 50% of these are themes and you and individually you can look into each to see which one suits you best.

Jennifer, please try to understand, the Apache is recommended by Moodle, only on *nix platform, if you're on windows platform IIS should be implemented as I mentioned to Ram too, I never did see Apache being used in Production environment on a Windows platform.

If accessing with www is the issue, then chrome automatically adds www before URL when typed in without www, FireFox/IE doesnt do that, so thing  should have worked there as well, but Ram said its the same.

first you have to go to your domain host and change DNS records, create A record for c-h.org.il and A record for www pointing to same IP (or you can use CNAME record for www as well, as long as @ record is pointing to the IP of your Apache server)

make sure your rewrite module in Apache is enabled

next open .htaccess file and type query, to route www traffic to non-www

RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
RewriteRule ^(.*)$ http://%1/$1 [R=301,L]



Sukru, I dont see any issue, other than making a backup copy of moodledata and database before installation (a recommended step before major installation)
rest process is straight forward.
just replace your moodle folder with new one (make a copy of moodle folder as well) and your installation will start.

here's what I would have done it:
1. making backup copies of all three (moodledata, database and moodle folder)
2. check for my PHP and database versions if they are compatible with newer moodle, if not then try upgrading to a version that is mutually compatible (refer to Visvanath's manual)
3. make list of all additional plug-ins and match their version numbers compatible with new moodle, although its not crucial as moodle detects and recommends downloading newer versions of plug-ins after install too.
4. put site in maintenance mood, add upgrade key to your config.php file so no one accidentally triggers upgrade process and/or get crucual details about your server.
5. after successful upgrade, keep backups for a day at least, test everything meanwhile for working then you can get rid of them easy.

if you're starting webserver as a brand new box, then setup hardware and move current moodle there to see web server's working first, before starting an upgrade.