Receiving an error trying to load up MAMP 4.5 after downgrading from version 5 to 4.5 because their serial number system is broke and no one in support is working.
This message comes up when trying to start, any thoughts?
Downloaded from the website under "older versions"
https://www.mamp.info/en/downloads/older-versions/
OS: Mac
I had to downgrade, as well; though in my case it's because mySQL will not upgrade my databases, but I was able to license it.
I was able to successfully downgrade by doing the following:
Backed up the /Applications/MAMP folder (just in case)
Deleted /Applications/MAMP and /Applications/MAMP Pro.app by moving them to the trash (these were created by MAMP Pro 5 installer)
Downloaded and installed MAMP Pro 4.5 from the link you posted above
I'm back up and running with MAMP Pro 4.5 at this point, so looks like everything worked out. Good luck! Depending on your setup, you might need to migrate stuff out of the /Applications/MAMP folder (definitely back that sucker up before you delete it).
Please note: For my original answer, I mis-read the MAMP Pro docs and incorrectly re-located the database directory in /Applications/MAMP/db to my user Library folder (~/Library). This apparently did nothing, because the databases were actually located in the root-level /Library folder. I highly recommend backing this folder up prior to upgrading or downgrading. The MAMP 5 installer automatically copies your mysql56 folder, but the problem I ran into is that evidently it didn't copy all of the database folders within it (which is presumably why the mySQL 5.7 upgrade logic was failing hard on my end). So a backup is a great idea, because the steps the MAMP installer takes to keep a historical backup don't actually work too well in my experience.
I need to update an old forum made in phpBB from version 3.0.11 to the new / stable version 3.2.2.
It is the first time that I put my hand at phpBB.
Making an update step by step is complicated: move from 3.0.11 to 3.0.14 ... from 3.0.14 to 3.1.x ... and from 3.1.x to 3.2.2.
So I thought: can I make a clean install of 3.2.2 and import everything I need (posts / forum / users / ALLINEED)?
Do you know any plugins that do this? maybe phpBB itself does it? Or maybe I just need to export the tables from mysql?
can you advise me something?
thank you
There is no plugin to do it, but there is a process to upgrade from 3.0 to 3.2. Your forum will be as clean as a fresh install.
The more secured solution is to begin by upgrading from 3.0.11 to 3.0.14 for security reasons.
When you can stop your forum during one or two hours, stop it and upgrade directly from 3.0 to 3.2. You don’t need to upgrade to 3.1 then to 3.2.
All explanations are provided in upgrade documentation from 3.0 to 3.2
Do not forget any step! After step3, I advise you to restore the 3.0.11 forum on a local machine or another server to be sure that your backup files are not corrupted. (Yes, it could happen during a download.)
I did it a lot of time. It works fine. One hour to do it cautiously and slowly (+ download and upload time).
I want to upgrade a moodle website currently on version 2.5 to the latest version.
I need to clarify that is it possible to upgrade Moodle 2.5 directly to Moodle 3.3.
OR
As mentioned in the moodle upgradation document
"Note: You can only upgrade to Moodle 3.0 from Moodle 2.2 or later. If upgrading from earlier versions, you must upgrade to 2.2 as a first step."
I can only upgrade to Moodle 3.0.
Please confirm.
Thanks in advance.
In order to upgrade Moodle 2.5 to 3.3, start by backing up your site. This includes:
The Moodle files.
The Moodledata files.
The Moodle database.
Make sure you have everything and that no errors occurred while you were backing it up. If you want to be extra sure, restore it to a different location, maybe even locally on your computer and get it working there. Don't forget to adjust the settings in the config.php file as well as running the Moodle Search and Replace tool (it is not in the Moodle menus). Once you are sure that everything is working, and you still have the original unmodified backup files, you are ready to move on to the next step.
Verify your web server environment
Make sure your web server meets the hardware requirements for Moodle 3.3. Note the changes, especially in memory requirements from 2.5 to 3.3. Also make sure your server meets the software requirements for Moodle 2.7. In fact, when upgrading, it is best to verify the software requirements for every version of Moodle you will be skipping in order to find out which system components you will need to be add before proceeding.
Also, before you get started, make sure any 3rd party plugin and themes added to your site will be compatible with Moodle 2.7 and Moodle 3.3. If not, you will need to upgrade these first. If they are not available for the newer releases of Moodle, check with the maintainer of the plugin/theme to see if there might be an updated version forthcoming. If not, you will either need to fix any problems in the code yourself that may come up, switch to another similar plugin that provides similar functionality or remove the plugin completely.
Re-creating .git
The easiest way to upgrade Moodle is using Git. If Moodle was not installed using the "git clone" command, your installation will likely be missing the .git directory. You can check this by using the "git status" command. If you already have a .git folder, you can skip this section and go straight to Upgrade to Moodle 2.7. Otherwise, here is how you can re-create it:
Take note of the build date for your current Moodle installation. You'll find this on its Notification page near the bottom of the page.
Re-create your .git folder using the following commands:
# git clone a new copy of Moodle into another location
git clone git://git.moodle.org/moodle.git
# Checkout Moodle 2.5 (the version of your current site).
cd moodle
git checkout MOODLE_25_STABLE
Look through the log for a weekly release that is dated the same as your build number. The build number is a date in the following format: YYYYMMDD. Take note of the related commit number.
Next, rollback the files to the commit number of the build. Replace "56e05fced" with the actual commit number.
git reset 56e05fced
Once this is done, copy the just the .git folder into the web root of your current Moodle site.
Upgrading to Moodle 2.7
Before you get started, make sure any 3rd party plugin and themes added to your site will be compatible with Moodle 2.7. If not, you will need to upgrade these first.
git checkout MOODLE_27_STABLE
Login to your website as an administrator. You should see prompts that will guide you through the process of upgrading Moodle.
IMPORTANT: Up to this point, you could just roll back the files and everything should be back to the way it was. Once you move beyond this point, the only way to revert your website will be to delete the whole site and restore the backups you made earlier of your site's files and database.
Follow the prompts to upgrade the database. Be prepared as you may need to upgrade some of the plugins as well or make some upgrades to your web server and/or database environment.
Once you have everything running again, it will be time to upgrade to Moodle 3.3.
Upgrading to Moodle 3.3
Have you upgraded to Moodle 2.7 yet? If not, go back and complete that step first. Don't forget to make sure your web server meets the hardware requirements for Moodle 3.3.
Make sure your server meets the software requirements for Moodle 3.3 in order to successfully complete the upgrade from Moodle 2.7.
Next, upgrade Moodle from 2.7 to 3.3:
# Enable version tracking so that it is easier to upgrade Moodle in the future.
git branch --track MOODLE_33_STABLE origin/MOODLE_33_STABLE
# Upgrade Moodle to version 3.3.
git checkout MOODLE_33_STABLE
As you did before for Moodle 2.7, Login to your website as an administrator. You should see prompts that your database is about to be upgraded. If not, go to the Notifications page under Site Administration. Follow the prompts again to upgrade the database. As before, be prepared as you may need to upgrade more plugins and themes, and will likely need to make some upgrades to your web server and/or database environment.
That's it. If you followed the above instructions, your Moodle 2.5 site should now be upgraded to Moodle 3.3. To get the most out of your upgraded site, be sure to at least read the New Features page for each version of Moodle from 2.6 to 3.3.
To upgrade your site to newer bug/security release of Moodle 3.3, you will need to repeat some of the instructions. Essentially it will involve:
Backing up your site files (moodle and moodledata) and database.
Using the "git pull" command from within your Moodle folder.
Logging in as an administrator and following the upgrade prompts from the Site Administration > Notification page.
Verifying that everything on your site still work as expected.
Bug and security fixes come out every week but are only officially release every 2 months.
Hope you find this information useful.
Best regards,
Michael Milette
Per the upgrade documentation for 3.3 it says "You can only upgrade to Moodle 3.3 from Moodle 2.7 or later." https://docs.moodle.org/33/en/Upgrading
So you must first do an upgrade to v2.7 before you can do an upgrade to v3.3
Also note in the v2.7 upgrade documentation it says "You can only upgrade to Moodle 2.7 from Moodle 2.2 or later." https://docs.moodle.org/27/en/Upgrading
Personally I have found less problems when I do upgrades in smaller jumps. So in your case 2.5 to 2.7.20 is a requirement. In theory you could then go from 2.7.20 all the way to 3.3 but you may want to consider 2.7.20 > 3.0.10 then 3.0.10 > 3.3
I can say that I have actually upgraded Moodle 2.3, and Moodle 2.5 successfully to 3.x, though not 3.3 specifically.
That being said, you have to also take the following considerations:
Are you up to the minimal PHP version? (5.6.something)
Do you have the new modules required by 3.x version (3.3 added a few I think)
Are your modules ready for 3.x?
If you aren't sure of any of these, I would go grab a Vagrant/VirtualBox/Docker setup of Moodle, stage your current site (i.e. install it with the same software you have installed on your production server), and upgrade it locally to ensure everything goes as planned.
First you backed up before any moodle 2.5 upgrade.
Then download new moodle 3.3
After then unzip folder
go to xampp->htdocs->your project
paste and override new folder
Copy your old config.php file back to the new Moodle directory
Sometimes, the environment may cause issues, sometimes the Moodle versions. I have faced both. But managed to upgrade. Last time for upgrade to 3.9.2 installed the old version to local server for reference and did a clean install on the cloud. I have upgraded Moodle 2.x to 3.2 for a couple of institutions. Please feel free to contact if needed.
Few steps to consider in this
Take backup of Moodle app, Moodledata and DataBase
You have to follow the upgrade process twice
First you need to upgrade from moodle 2.5 to moodle 3.0
Now you can upgrade you new moodle 3.0 to moodle 3.3
I am trying to upgrade my Xcart 4.6.2 to 4.7.5. I followed the documentioan exactly as mentioned here http://help.x-cart.com/index.php?title=X-Cart:Upgrading#Upgrading_from_version_4.7.0_or_later
However the software is updated and the db remains the same. I said because when I check http://wwww.example/VERSION it says 4.7.5 and when I check http://www.example.com/include/version.php it says X-Cart DB Version: 4.6.2 GOLD.
I did the following steps :
made a development copy of live site in server.
made a fresh installation of the xcart 4.6.2 and pointed the db to the development copy
Downloaded the 4.6.2-4.7.2 upgrade package, extracted it to the root and ran the upgrade from backend. No errors.
I checked http://wwww.example.com/VERSION it says 4.7.2 and http://www.example.com/include/version.php it says X-Cart DB Version: 4.6.2 GOLD
Do you guys faced such issue? Your advises are very much appreciated. Thanks in advance.
Most likely something goes wrong while applying the sql patch (upgrade/4.6.2-4.7.2/patch.sql) because
UPDATE xcart_config SET value = "4.7.2" WHERE name = "version";
is at the very end of it.
So, please, check the following logs for anything out of the ordinary:
var/upgrade/4.6.2-4.7.2/patch.log
var/log/x-errors_sql-.php
I was going through upgrade process of mysql server. It is mentioned that to upgrade from 4.1 to 5.5 we need to upgrade step by step like first to 5.0,5.1 ...5.4 and then 5.5.
I have some questions :
What if we directly upgrade from 4.1 to 5.5. What might get effected? functionality or problem related to upgrading
Chances to loose data ? Even though I'll take backup using 'mysqldump --all-data-base' option.
Lets say, I have two database. I'll take only two database backup. I'll install latest version of mysql 5.7 and load two database back. What are chances to loose data or get corrupted ?
I'm curious to know this. If anybody tried? Because I need to do upgrade in live server.
Is there any step by step document which tells exact steps to upgrade from 4.1 to 5.5 in linux server
Major new features added to MySQL 5.0 and 5.1 that may not work/won't work in 4.x can be located here:
MySQL 5.0 - http://dev.mysql.com/doc/refman/5.0/en/mysql-nutshell.html
MySQL 5.1 - http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html