Sticky Upgrade problems with K 1.x -> K 2.0.3 (and solution)

Well I'm confused :dry:

I just came back to post the results of my upgrade to 2.02 (from 1.07) and I saw my topic was gone and I was listed as being the last poster in this thread but when I clicked last post my post is nowhere to be seen ... in my original thread (which is gone) or this one.

Should I continue on in this thread or start a new one with my configuration report from 2.02 and some of the issues that have appeared?

Phoenix

With apologies to Phoenix who asked a question about upgrading from K 1.7.2 to K 2.0.1.

I was in the process of merging this person's question into this topic when, for some unexplainable reason, I inadvertently lost his message. These things occasionally happen and I apologise for this mistake.

Although my recollection of the information is not the best, the question related to a problem that the person was having with the upgrade from K 1.7.2 to K 2.0.1 because (as people will see in msg #1 of this topic) there is a suggestion that people need to go first to K 2.0.1 and then go from K 2.0.1 to K 2.0.3; that suggestion is half-true.

We do not recommend that people use K 2.0.1 as an intermediate path in upgrading to K 2.0.3 but, if you feel that you must use an interim/temporary workaround, it would be preferable to use K 2.0.2 instead.

There is also another mechanism for addressing the problems relating to the upgrade from K 1.x to K 2.0.3 and this is described in Kunena 2.0.3 known issues

Two remaining matters I would like to remind people about:

(1) K 1.7 became obsolete in August this year. We encourage all members of the community to subscribe to the category Official Announcements and News about Kunena so that you will not miss out on important notices that help you keep your site up-to-date and to avoid the problems of playing "software catch-up" later.

(2) There is no issue involving the upgrade from K 2.0.x to K 2.0.y but we also need to make it clear no versions before K 2.0.3 are supported and therefore any questions relating to K 2.0.1 (or K 2.0.2) will go unanswered.

The issue of difficulties involving the upgrade from K 1.x to K 2.0.3 has been resolved and will be fixed properly with the release of K 2.0.4.

Again, my sincere apology to Phoenix for losing their message.

Hi Sozzled,

The gist of my post was that I was having issues with 1.72 to 2.03 and had restored several Akeeba backups to try to resolve them in the upgrade process. I was also under pressure from my host provider who insists that K1.72 has serious security flaws with SQL injections and is attracting hackers who are looking for outdated software to exploit and causing CPU spikes. I had also posted my configuration report for 1.72 in case it would be helpful with my questions after the upgrade (which is now done) My "preliminary" question was ...

Is this a reasonable assertion or in any way factual? They have said they won't host it (or any software with known serious security flaws) because of the security issues and this has caused some real pressure as I was hoping to have it up for another few days until the upgrade issues I have encountered have been resolved (and hopefully sooner).

My second question is should I continue with posting my config report "post 2.02 upgrade" and ask my questions about what is now happening in this thread or start a new one?

Thanks for solving the mystery of the missing post

Phoenix

FWIW ... I just clicked recent posts on the forum and received this error ...

500 Internal Server Error
Fatal Error was detected!

Please contact the site owner.

Go back

The no replies tab is producing the same. All the other tabs are working.

Phoenix

Phoenix wrote: ... K 1.7.2 has serious security flaws with SQL injections and is attracting hackers who are looking for outdated software to exploit and causing CPU spikes.

The first part of that statement is true. I don't know about the affects of such exploits that lead to degraded CPU performance, however.

The situation is the same with K 2.0.2. There is a known XSS code-injection vulnerability that was addressed in K 2.0.3 (which is why K 2.0.3 is important). The team has also discovered two other XSS code-injection vuinerabilities in K 2.0.3 (which are also present in all previous versions of Kunena) which will likewise make it imperative for people to upgrade to K 2.0.4 at the earliest opportunity following its release. You will minimise the possibility of security issues by upgrading from K 1.7.2 to K 2.0.3 and that is the first step in the process to keep your site as clean as you can possibly make it (and not only for the benefit of getting your host provider off your back )

I haven't solved the mystery of the missing post - evidently there's an issue with the database that I would like get the developers to investigate - but thank you for your understanding.

As far as problems you're having with upgrading from K 1.7.x to K 2.0.2 are concerned, in a few words, what is the basic problem? Have you considered "plan B" (i.e. upgrade from K 1.7.2 to K 2.0.3 and then tweak the database in the manner indicated in Kunena 2.0.3 known issues )? Direct manipulation of the database is not recommended in all cases, especially if you lack confidence in understanding SQL or in site restoration.

Phoenix wrote: FWIW ... I just clicked recent posts on the forum and received this error ...

500 Internal Server Error
Fatal Error was detected!

Please contact the site owner.

Go back

The no replies tab is producing the same. All the other tabs are working.

Phoenix

It seems like you have issues with the Kunena menu. Is that what you are saying? Have you tried restoring the standard Kunena menu? Would you like help in showing you how to do that?