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

I have just tested and I am able to Place new posts on the forum without any problems. It then upgrade my main forum in case I lose the 250,000+ posts that the domain over the years

sozzled wrote: Does your question fall into the areas covered by Upgrade problems with K 1.x -> K 2.0.3 (and solution) ?

Very strange, that's where I put it, I don't know what it's doing this category

Would you like me to give you a one paragraph explanation why I moved your topic to a different category or would you like to answer my question?

like I said, I don't know why my post is in here, I put it in the kunena installation & upgrade section, or that is where I thought it went.

Anyway, I have fixed the problem. For anyone else who has the same problem, visit this link

www.kunena.org/forum/K-2-0-Support/12599...a-2-0-3-known-issues

*** Topics merged ***

The K 2.0 Installation and Upgrade category is for topics that relate to questions about

1. How to install K 2.0 for the very first time;
2. How to go about the process of upgrading from an older version of Kunena to K 2.0 and what are the steps involved; and
3. Problems that arise during the upgrade procedure that prevent a successful installation/upgrade of K 2.0

If people have problems after installing/upgrading, it's at the moderator's discretion whether such topics belong in the K 2.0 Installation and Upgrade category or in another category.

When people ask "why has my topic been moved/merged/split?" these questions, however curious they may be, do not really get us closer to solving the actual problems that people may be having and they divert the moderators' attention from dealing efficiently and effectively with those actual problems.

Sometimes we don't always properly categorise topics and we can argue the case for which is the most appropriate category ad nauseam.

We're asked this "why have you move this" question a lot. I've answered this question a lot. No doubt I will be answering similar questions like this in future. This is one of the things that comes with the task of trying to moderate a forum. I hope the information (albeit entirely off-topic from the actual subject matter) helps.

I'm pleased to hear that you solved your problems.

Matias wrote: I found a fix for this issue (needs basic SQL skills):

1) Make backup

2) Go to phpMyAdmin or similar tool and run the code from below (change both #__ to your database prefix):

Code:

UPDATE #__kunena_topics AS tt INNER JOIN ( SELECT thread, MIN(hold) AS hold FROM #__kunena_messages WHERE hold IN (0,1) GROUP BY thread ) AS c ON tt.id=c.thread SET tt.hold = c.hold WHERE tt.moved_id=0

3) Go to Kunena backend >> Forum Tools >> Recount Statistics and run the action without changing any parameters.

PS. This bug is only present in Kunena 2.0.3 and can be avoided by upgrading first to Kunena 2.0.2.
PPS. It's already fixed and the fix will be in the next version.

Hello.

Does this code work in MySQL Data Base ?

Thanks a lot