I have a mediawiki version 1.21.2 (php 5.3.10, mysql 5.5.35, Apache/2.2.22, Ubuntu 12.04.4) and I want to move it to a new server with mediawiki version 1.29.1 (php 7.0.22, mysql 5.7.19, Apache/2.4.18, Ubuntu 16.04.3).
The old site is configured as a wiki-family with 5 associated wikis.
It seems the normal approach is to first upgrade the source site and then move the upgraded site to the target server.
The old site must remain active (read only) and as-is and will be turned off after the new site is in place.
I would like to try an approach with the following steps:
install version 1.29.1 on the target server
sql dump the datafiles from the source server
import the sql dump files into the target server database
run some update scripts to bring the source files into compliance with the target database
Of course I'll need to manage the media and extensions.
The target server already has php 7.0.22, mysql 5.7.19 (installed as part of default LAMP), so I suspect I'll have to downgrade components only to re-upgrade them. Maybe not.
Can anyone suggest the cleanest way to do this, please?
Upgrading the old server prior to moving the wiki is not really necessary.
You can follow your own steps:
Download your new MediaWiki version on the new server
Download/copy any additional extensions you need on the new server. Try to download new copies of extensions that match your MediaWiki version instead of copying them from the old server, since they may be incompatible with the new MediaWiki version
Copy your old media to the new server
Copy your LocalSettings.php from the old server to the new one and adapt it: you may need to change some settings or disable incompatible extensions.
Dump your database from the old server, and import it on the new server.
Run the update script.
You can do that even with the old wiki running, to test if the upgrade will work, and then redo it again putting the old wiki in read-only mode during the move.
Related
We're running a local server for database management, it's old software, but works. A replacement is incoming, but not ready yet.
I've had to learn to manage it all in pretty quick time, so I'm very much a beginner.
Overview:
The database is running in Sequel Pro 1.0.2 (MySQL 5.5.34).
The main interface is via a custom site in PHP.
The server is run via MAMP 3.0.5.
The system is Mac OS 10.10.5 as this is the last version of Mac Server with the VPN that we can use for remote access to the site.
I also have a cloned version of the system off-site for when the main office internet goes down and we still need access to the site/database, and the entire MAMP folder is being automatically backed up.
Problem
I've found all the database files in MAMP>db>mysql, however I've noticed that the .MYI and .MYD files are only modified when MAMP is stopped.
This means the backup files are always out of date.
If I manually create a new view directly within Sequel Pro, then the files get updated.
For example, in the Sequel Pro database, I can see the latest item created was on the 15th (today) at 09:13, but the .MYI/.MYD files show last modified yesterday at 08:47.
Is there a way I can get the database files to update automatically without needing to manually stop the MAMP server so that the backup is current?
Again, very much a beginner with this so any advice is appreciated.
Thanks!
I am running an old [release 1.22.6] version of mediawiki which I am finally being forced to upgrade or replace. I am considering creating a new subdomain using the 1.32.0 release of mediawiki. And then I intend to restore a backup of my old version databases and image files to the new version.
My main concern is about database changes between the versions. Will the backups be compatible with the new wiki version?
I also have the same concern about my modified LocalSettings.php file.
My mysql server version is 5.7.25
The database can be migrated to the new version, as described in the upgrading manual. The one somewhat-exception is the pageview data, check out the documentation for the HitCounters extension if you want to keep that.
LocalSettings.php might need to be updated, check the release logs or the documentation for the configuration variables you are modifying. It really depends on what you have in it.
I have a LAMP server on an EC2 instance. I downloaded phpMyAdmin using Amazon's guide here: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/install-LAMP.html.
On the phpMyAdmin page it says that:
"A newer version of phpMyAdmin is available and you should consider upgrading. The newest version is 4.6.5.2, released on 2016-12-05."
and I need to update it and also MySQL to use new features they put on the updates.
I'm accessing the EC2 instance from the terminal in my Mac laptop. I've tried a lot of things but I couldn't manage it. I've tried
sudo yum install -y phpMyAdmin
sudo yum install
I tried to manually download the latest version from phpmyadmin.net and change the files in the folder but I couldn't access the phpmyadmin folder in the first place.
Any help would be appreciated,
Thanks
You're using the version of phpMyAdmin maintained by your distribution (presumably Fedora, CentOS, or Red Hat); this means that basically you're not responsible for (or able to) upgrade the software that's under control of the package manager (aside from running the updates occasionally). If you wish to use a different version, you're certainly able to remove the package manager version then install it manually. I don't use EPEL, but I believe the highest version currently distributed is 4.4.15.9 (reference, which I think is because of the older versions of PHP and/or MySQL which are currently shipped. So you might not be able to upgrade due to your MySQL or PHP versions, but YMMV.
Basically, if you're using the package managed version, the whole point is so you don't have to worry about manual updates.
You can disable the notification by adding the directive $cfg['VersionCheck'] = false; to your config.inc.php (which may be in /etc/ or /etc/phpmyadmin, but I'm just guessing about how your distribution may handle it.).
I recently changed configurations on my web server and moved my MySQL databases to a remote server. Upon making the changes, I removed MySQL from my web server just to make it as minimal as possible. My WordPress site was working perfect with the remote SQL until I removed it on the local server. Then I got the error:
Your PHP installation appears to be missing the MySQL extension which is required by WordPress
I'm curious as to why WordPress forces you to have it installed even while using a remote connection? Is there a way to get around this?
Worst case scenario I guess I'll reinstall MySQL.
its not mySQL that is the issue you need to enable the mySQL extensions required by Wordpress in the php.ini file or install them if they don't exist.
When you removed MySQL it probably removed or diabled the extensions for it in PHP, atleast that is what it sounds like. You should be able to just install or enable the extensions back in without reinstalling all of mySQL
WAMP comes packaged with MySQL, Apache, and PHP. I already had a version of MySQL (downloaded from Oracle) installed to my machine with data in it. Is there any way I can make WAMP use the external MySQL rather than the one packaged with it?
For instance, if I click "Restart Services" in WAMP, it restarts the MySQL server packaged outside C:\wamp.
Copy MySQL installed (outside wamp) files to your wamp>bin>MySQL folder. Ensure you keep the MySQL folder name as such without renaming, in the wamp - only then wamp will be able to turn on its services since those values lie in registry.
For example, if folder structure in Wamp is bin>MySQL>MySQL5.5.8 then copy the files from the standalone installation and copy to MySQL5.5.8 folder. So ensure you dont rename MySQL5.5.8 folder.
Now all this wont give you the correct version in phpmyadmin which will require more configuration, it will still show the previous version number as of MySQL that came along with wampserver. But you can atleast be sure inside, in real u r using my damn new MySQL :)
Here is a related question, but dont have anymore info