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.
Related
I've got a client that's running a pretty ancient version of Mediawiki (1.17.0) on an internal corporate network. It's running on PHP5, but they're looking to upgrade to PHP7. This version has basically served its purpose well and whoever was in charge never messed with upgrading it. (I know) But it won't run under PHP 7.4 and the company is upgrading their PHP systems.
Obviously there have been a TON of revisions to MediaWiki in this time. I've got a few questions...
First, what's the earliest version of MediaWiki that is PHP7 compatible?
Second, what's the best approach to updating this system? It's got over 1000 pages and 1000 images. It's not huge, but it's obviously not small, and if there's any way to automate bringing this up to the most current version, I'm curious what my options are?
I'm trying to avoid doing incremental updates because upon investigating, it's a ton of them, and not all interim versions seem to be available.
Is it possible to install a new, fresh version and copy the database/images over?
Any advice is most appreciated!
As noted in https://www.mediawiki.org/wiki/Compatibility#Upgrade , you need to upgrade first to 1.35 and then to 1.38 (or 1.39 if you wait a little - 1.39 is an LTS release so probably worth it). See the manual on upgrading on how to do it - basically, update the files in MediaWiki core and all extensions, possibly run composer update depending on your distribution (tarballs tipically already include the files that Composer would download, git doesn't), and run the upgrade script wich will migrate the DB.
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.
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.).
Joomla 2.5 supports SQL Server, but I have an old site created in Joomla 1.5 that used Akeeba Backup 3.4.3 and MySQL.
When I navigate to the site for the first time, Akeeba Backup recognizes that the site needs to be installed, but it's not giving me the option of using MSSQL Server.
I tried dumping the newer Joomla 2.5 into the web directory, but that didn't help. Does anyone know how I can migrate a Joomla 1.5 site that used MySQL to Joomla 2.5 using SQL Server?
I got it working.
First, the old site had to be live with MySQL, so that I could upgrade it to joomla 2.5 with jUpgrade. jUpgrade Pro (beta software) would not work, FYI, so I had to use the original jUpgrade. The site upgraded smoothly to joomla 2.5.
Next, I had to get the latest version of the template I was using. When I tried to install the newer version of the YooTheme Phoenix template, it would not let me install it, saying there was already a template with that name. I simply deleted the existing "templates\yoo_phoenix" folder, then installed the new theme again and it worked. Afterwards, both templates (old and new) appeared in the template manager, but only the new one worked (name ending in " - Default". I then was able to uninstall the old one. At this point, the site was functioning perfectly.
With the new site up and running in joomla 2.5 on MySQL, I should be able to use akeeba backup to backup the site, then I restored the backup to a new site that was set up to use SQL Server. I will update this after I've successfully restored the site to SQL Server.
SubSonic 2.2 requires MySQL Connector 5.3.2.0. This is not included in the download package, nor is it any longer available from the MySQL download site.
I know I can build SubSonic again from source to get around this, but this is a pain.
Can someone on the SubSonic project please change the "Specific Version" flag on the MySQL assembly reference to "false"?
Change the "Specific Version" Attribute isn't a wise solution.
The linked version should have passed the subsonic unit tests, so it should be ok.
From my own experience I know that mysql sometimes changes the behaviour of the assembly (e.g. a returnvalue 0 or 1 suddenly changes to true/false) that's why we are stuck with an old 5.1.2.2 version (we have no unit test's ;( for our old core)
But if you "tweak" the download link:
http://dev.mysql.com/get/Downloads/Connector-Net/mysql-connector-net-5.2.3.zip/from/http://ftp.gwdg.de/pub/misc/mysql/
you should still be able to download the old connector. If not, you can drop me a line. I still have the msi and the binaries archived.