- Posts: 5
- Thank you received: 2
Kunena 7.1.0 Released
The Kunena team has announce the arrival of Kunena 7.1.0 [K 7.1.0] in stable which is now available for download as a native Joomla extension for J! 5.4.x/6.0.x./6.1.x./6.2.x This version addresses most of the issues that were discovered in K 6.2 / K 6.3 / K 6.4 / K7.0 and issues discovered during the last development stages of K 7.1
Just a reminder: K6.4.16 receives only securities fixes until end of 2026, so it's advised for users to upgrade to K7.1.
Question Move K1.7 from J1.5.23 to J.1.7
1. Make sure you are running Kunena 1.7 on your Joomla 1.523 site
2. Using phpMyAdmin or some other tool, export all your kunena_* tables from your Joomla 1.523 site database to somewhere on your desktop
3. Migrate your Joomla 1.523 site to a new Joomla 1.7 site using jUpgrade (a component). jUpgrade does all the work, downloading and installing a new Joomla 1.7 version of your site in a subdirectory of your 1.523 site, so you can test it before trashing your 1.523 site. In my case, it did not install Kunena on the Joomla 1.7 site.
4. Install Kunena 1.7 on your new Joomla 1.7 site (the site that is in a subdirectory of your 1.523 site). This will be a virgin Kunena install, with only the default starting info.
5. With the file you made in step 2 (the Kunena database tables), open a text editor on your computer and perform a find and replace to change the table prefixes to whatever your Joomla 1.7 site is using. In my case, I changed all instances of jos_ in the Kunena tables to j17_. Save the file with the changes.
6. Using phpMyAdmin, Drop (i.e. delete) the kunena_* tables in the Joomla 1.7 site's database.
7. Using phpMyAdmin, import the file you made in step 5 (the new database tables)
8. I haven't done this yet, but my next step will be to move my Joomla 1.5.23 site to a subdirectory (to keep until I'm sure I don't need it), and move the 1.7 site to the site root.
That was it. After all day pounding my head against the desk, I got things working. If that doen't solve your problem, maybe it will save somebody else the frustration I had today.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
For your database tables, you need an app that handles databases. Most hosting providers offer something like cPanel or something similar. Within cPanel are a suite of different options and apps. One of them is phpMyAdmin, and it is a database tool. In phpMyAdmin, you find the name of your database in the left margin, click it, and then a list of your tables shows up in the main window. You want to select all the ones that have "kunena" anywhere in the name (use SHIFT-click to select multiple ones at once), and then use the Export option at the bottom of the list to save them locally on your PC.
Before you do anything - backup! I actually exported a complete copy of my database, and imported those tables into a virgin database, and made my changes on the copy without messing with my original database. You can backup by either using the Backup feature in cPanel, or by exporting all of your tables using phpMyAdmin.
Please Log in or Create an account to join the conversation.
- etkritikonspoudon
-
- Offline
- Senior Member
-
- Posts: 110
- Thank you received: 7
One thing that seems crucial is to maintain the same ids. It seem JUpgrade does not do so...I have come across another extension, called SP Upgrade which claims to do exactly that and it's reviews are stellar...unfortunately, though, it is commercial...but it may be the way for me to go...
Using that extension what you need to do is
- Make a clean J1.7 installation
- install the extension, configure it and run it
- Clean install all your extensions, compatible version for J1.7
- Test, test, test.
- Then I guess copy old site to subfolder, and copy j17 site to root
Regarding the database for Kunena, seems like what -logically needs to be done is
- export kunena database entries from old site
- Install Kunena on new site
- Drop the newly created database entries for Kunena
- Import the database entries from previous site.
Haven't gone through the process yet, I haven't made my final decision to go with J1.7 that early (really don't want to run into serious bugs and beta test practically)
Please Log in or Create an account to join the conversation.
In the mean time I suggest that you downgrade back to K1.6.5 and use JUpgrade after that.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.