Been wresteling with Joomla for a customer. I installed an update from 2.5.19 to 3.2.2 and it crashed. Couldn't log into the backend anymore or anything.
After putting the backup files back on the server it still kept giving errors and leaving me unable to log in.
I now have re-installed Joomla 3.2.2 and want to restore just the content (articles, components and modules).
Does anyone know where I can find the files that I should put back on the server? If I import the entire administrator folder it crashes again..
By files you probably mean database entries, as joomla contents are stored in the database. If however you do mean files then just put them in the corresponding folders e.g. images in 2.5 to images in 3.2 etc. I also assume that you probably didn't follow the correct procedure for upgrading your installation. That said I suggest taking a look at the following:
Upgrading from an existing version
What are the major differences between 2.5 and 3?
Practical Guide Upgrade Joomla 2.5 to Joomla 3.x
Upgrade from Joomla 2.5 to Joomla 3
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'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.
My company has two web based project. Our main project (Starbooks) was built using xampp server and Codeigniter framework that installed in our Windows OS and the second project (Frontlearners) was built in Lamp server and moodle (LMS) framework with Postgres database that installed in ubuntu platform.
My goal is to collide this two projects into one by moving the second project (Frontlearners) into the main project (Starbooks) server which uses with xampp server windows platform.
My first attempt is to export the moodle Postgres database using PGAdmin then move the moodle project to the main project server on windows. But I don't know if this is the correct way or not because Postgres and mysql are different database type. I've searching across the internet hoping for the answer or tutorial related to my problem but the results are always fresh installation of moodle which is not related to my problem.
Anybody knows how to solve this problem, a tutorial link, or any article about this situation?
There is a database transfer tool in Moodle.
https://docs.moodle.org/311/en/Database_transfer
So you can convert the PostgreSQL database to MariaDB
First ensure MariaDB is installed on Ubuntu
Turn off cron and put the site in maintenance mode
Then go to Site administration > Development > Experimental > Database migration to convert the database.
Or direct to /admin/tool/dbtransfer/index.php
The tool will check the database structure matches the structures in the install.xml files. If there are any differences, then you will need to update the relevant install.xml file or database table before continuing.
If its a large database, then the UI will probably time out. So use the command line version instead:
php admin/tool/dbtransfer/cli/migrate.php --help
Having said all that, IMHO I would transfer the Windows project to Linux.
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.
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.