My problem is the same that this one: https://dba.stackexchange.com/questions/253777/is-it-possible-to-run-multiple-versions-of-mysql-workbench
I need to use mysql workbench 8 for mysql server version 8.0.27 and mysql workbench 6 for a version 5 mysql server.
The problem is that when installing workbench 8 it deletes existing workbench with lower version.
I've tried to install Workbench6 on a completely different location to see if the installation does not find it but I it finds it anyway.
Also tried to install a 32 bit version of workbench 6 but again, version 8 delete it when installing.
Found some comments saying to enable multiple instances in menu -> edit -> preferences -> others, but this is only to open multiple instances of the same version.
I've looked for a portable version of workbench 6 but had no luck.
I don't understand why this problem is not having an answer by MySQL, even the MySQL forum doesnt have a solution or even an explanation why this is not possible.
I use a Vm for that porpose. where an "old 5.7.xx is installed alongside a workbench 6.3that work with that well, because the newer version don't do.
You can use for that purpose also a linux server as vm not only windows
Found a portable version of Workbench 5.2.47. I've upload it to my github.
Although I use this software with no problems until now, this is not from my authorship, use it at your own risk.
Download latest zip archive (version 6.3.8 and earlier has it) from here: https://downloads.mysql.com/archives/workbench/
Look out because x64 archive wasn't working in my case but 32bit works fine.
Unzip to different folder and that's it.
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 have been using Sophos Anti-Virus on the Mac for several years now with good results. Recently when attempting to download the new MAMP Pro 4.x, I received a Sophos alert that the MAMP installer contains the Adminer Database Manager, which it identifies as known Adware and PUA.
Has anyone experienced a similar warning, and is there any reason for concern about this warning?
The only real information I can find about Adminer is this:
http://philipdowner.com/2012/01/using-adminer-with-mamp-on-mac-os-x/
This post indicates that Adminer is some type of script designed to be an alternative to PHPMyAdmin.
Can I just remove Adminer after installing?
-- Lee
I got the same warning and also Google Chrome flags the MAMP 4 PKG file as having a virus. It appears that the official download of Adminer throws the same warning by Sophos (from their website):
https://www.adminer.org/
So, this issue is NOT related to MAMP itself but rather the Adminer application. I think it's a false positive since from what I've seen Sophos is the only antivirus software that flags adminer.php, however you CAN remove the file Applications/MAMP/bin/adminer.php without affecting functionality of MAMP, since as you point out it is just a phpMyAdmin alternative. I simply deleted it for now.
That said, if you upgrade MAMP the file will likely be replaced.
My Bluestacsk2 installation does not pop-up after extracting. Just nothing happens after that window. I tried disabling antivirus programs and running it as administrator. My system fulfils the system requirements:
Windows 10 Pro, 4 GB Ram.
Version: BlueStacks2_native_8e68b6e001e5a05ff01c3f89c5790f9d
I also have the latest version of Directx and .NET framework. My graphic card is up to date and works very well.
This problem occurs only for the Bluestacks 2. I can setup the previous beta version. I tried both win7 and win10 versions for Bluestacks2 but they are not starting to install.
I figured out that I don't have enough space in C drive. But it was really annoying that Bluestacks does not warn me about this. I had several gigabytes in C, but I have been able to install it properly after I removed 10 gb of data from there. (I don't think you need to remove such big data)
I just downloaded and installed .net 4.5 and it went through the installer successfully, I got all the successful install messages, restarted my machine, and nothing.
My C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework was supposed to have a 4.5 folder in it now, and it doesn't. Also, I can't change any of my projects to 4.5 in visual studio, which I was supposedly able to do also. I followed Scott Hanselman's blog here and I'm not getting the same result.
Also, one of my interns did the same thing today and got the exact same result on his own machine.
Ultimately all I want to do is run EF 5 so I can get fricken enums! And I thought I had to have 4.5 to do that.
Thanks!