Question Stuck on Installation (Creating version table)

There are a couple of defects in K 1.5.14 (see Installation of 1.5.14 in preparation for Agora conversion error ). It's never easy giving people bad news but I have some bad news for you. K 1.5.14 cannot be installed on clean J! 1.5 website. Even if you upgrade from an older version of Kunena, the upgrade installer has a small issue with the final stage of the K 1.5.14 upgrade. However, the upgrade seems to complete. I just don't know if it completes successfully.

I can understand that this causes a problem with new installations of Kunena and I am not enjoying writing those words at this time. I am fairly sure that these problems will be resolved in some way in the future but, for now, this leaves people who want to start to use Kunena with a very difficult choice. Should people wait for a newer version, K 1.5.15 (say), in order to be able to install on a new site; or should people use the version before K 1.5.14 (K 1.5.13), start with that, and be exposed to the security issues that were associated with that version?

For a long time we have urged people to not use K 1.5 for new site installs. For a long time we have urged people to start with K 1.6 in preference to using K 1.5. For a long time, too, many people have written that they are unable to use K 1.6 because they were "waiting" (for what, I don't know) or they had site templates (or other Joomla extensions) that included Javascript libraries that were incompatible with Mootools 1.2.4 .

If people feel helpless and stuck because of the choices they have made, if people are unable to resolve these Javascript library conflicts themselves, we can put people in contact with professional services that will overcome these issues. It must be remembered though that when I write "professional services" I am referring to services that people have to pay for.

But there are always alternatives and most of these alternatives involve no cost other than your patience and perseverance.

Use the current opportunity to move away from K 1.5. K 1.5 does not have a future. The future lies with K 1.6.

Even though the current problems with K 1.5.14 are only temporary, I expect, make the most of this opportunity to move forward and use K 1.6.3 instead. Yes, there may be issues, but do not shrink from the challenges of those issues. Those other issues can be solved quickly. Using K 1.5.14 is an issue that may not be solved quickly. Your decision should be based, largely, on how long you are prepared to wait.

You can also use this time as an opportunity to rid yourself of old and outdated software from your website and make sure that these kinds of issues never come back again.

As I mentioned earlier, I do not enjoy being the "bringer of bad news" but I hope that I have written something that will help you.

thanks for that, i went with 1.5.14 due to the fact that when ever I installed 1.6.3 all i would get is server 500 errors.

will explore this further.

thanks again

fats

I migrated to 1.6
Had the 1.5.11, have a server that meets all the technical criteria, but see what happened:

1. 1.5.11 < 1.6.2 or 1.6.3 was unsuccessful, the installer (migrator) got stuck after three tasks and the admin website was continuously refreshing.

2. 1.5.11 < 1.5.14 was partly successful, but saying that there was something wrong with my 1.5.11 installation, so I should downgrade. I tried several settings (of course had also plugins disabled etc.) but I could not find what was wrong. I saw the 1.5.14 worked ok (everything worked except the components main control panel), so I thought I try to do it and try to go on.

3. 1.5.14 (with partial error) < 1.6.3 was unsuccessful (got stuck after 10 tasks)

4. 1.5.14 < 1.6.2 partly successful (all the first migrate screen tasks completed, but the kunena cpanel reads: An incomplete installation of Kunena 1.6.2 build 3894 was found in your system. This means that the installation either failed or was interrupted.). I got all the content migrated into new jos_kunena tables.

5. I installed on my J. 16 site the fresh Kunena 1.6.3 (had problems with the menu item - had to delete it in MYSQL) and imported CATEGORIES table from my upgrade (1.5.14 < 1.6.2 partly successful) as well as replaced following whole tables (could not import them entirely* because INDEX of the table was different): messages, messages_text, ranks and users.

*for example from messages I could have imported only 356 from 995 rows, saying error - duplicate entry, although the table was entirely emptied by me before.

It seems that Kunena now runs ok, but I have three questions:

1. Is my installation now ok?
2. Why was my 1.5.11 installation broken?
3. What the hell is INDEX in MYSQL and why could I not import those rows from Kunena 1.6.2 to 1.6.3?

Thank you, thank you and thank you if anyone can assist by mi problems!!! :woohoo:

Ok, as I see you are not able to answer these questions. Are they to difficult or to stupid?

1. If you don't have anymore errors messages, so it's ok
2. Missing tables, duplicate entry, was it a clean installation or you had migrated from something ?
3. Because you have duplicaty entries, i don't know why

Thanks Xilly,

2. It was, I use FB from times immemorable
One time I tried out Agora, but it was separately. I did not touch the FB tables.

3. No, not duplicate - but other entries - in one table (where the upgrade did not complete) there are indexes:

Indeksi:

PRIMARY BTREE Da Ne id 318 A
thread BTREE Ne Ne thread 63 A YES
ip BTREE Ne Ne ip 159 A YES
userid BTREE Ne Ne userid 31 A
time BTREE Ne Ne time 318 A
locked BTREE Ne Ne locked 1 A
hold_time BTREE Ne Ne hold 1 A
time 318 A
parent_hits BTREE Ne Ne parent 159 A YES
hits 318 A YES
catid_parent BTREE Ne Ne catid 9 A
parent 159 A YES

in the table I have now it looks like that:

PRIMARY BTREE Da Ne id 995 A
thread BTREE Ne Ne thread 142 A YES
parent BTREE Ne Ne parent 497 A YES
catid BTREE Ne Ne catid 8 A
ip BTREE Ne Ne ip 497 A YES
userid BTREE Ne Ne userid 62 A
time BTREE Ne Ne time 995 A
locked BTREE Ne Ne locked 1 A
hold_time BTREE Ne Ne hold 1 A
time 995 A
parent_hits BTREE Ne Ne parent 497 A YES
hits 995 A YE

catid_parent
is now separated into two entries: catid parent
etc. Why was it different?