Question K 1.7.2 -> K 2.0.4: all my topics are missing

kunena 1.7.2 (screenshot of category manager)
migrate from 1.7.2 to 2.0.3 (migration admin console)
kunena 2.0.3 (screenshot of category manager)
tools 2.0.3 (fixing messages)

You had made an upgrade from K 1.7 to 2.0.3? Maybe it is this error.
www.kunena.org/forum/K-2-0-Support/12599...-known-issues#137655

sozzled wrote:

tokenring wrote: Okay, just so I'm clear and you are too. Right now I am running J2.5.11 and Kunena 1.7.2. I am trying to upgrade from K1.7.2 to K.2.0.3 or K2.0.4.

Why don't you try upgrading from K 1.7.2 to K 3.0.0 instead?

That forces you to use higher than 5.2.17 (PHP). I'm not running that right now because of other modules/components in use.

Aaron

Kunena 1.7 and 2.0 use different way to store the topics. Messages are still the same, but there's a new table for each topic #__kunena_topics.

There are two possible reasons why the topics aren't seen:
1) #__kunena_topics table is empty
2) category permissions are wrong

@tokenring, I suspect that your issue is the first one: missing topics.

@quahfamili, your issue is that the category permissions are wrong or Kunena - Joomla Integration isn't turned on, at least according to the screen shots.

Hello Matias,

Thanks for replying.

SELECT *
FROM `keycd_kunena_categories`

Returns the proper records of all my categories.


SELECT *
FROM `keycd_kunena_topics`

Returns the proper records of all my topics.


I didn't attach the exports of the query in case I could email them to you or your support team. Please let me know which you prefer.

Aaron

Matias,

Can you please take access to my test site and take a look? This support is now taking a long time for something that is simple and for something the team should be working on fixing.

I did what you said and my tables are not empty... even the ones that you have listed. Please help me resolve this so I can continue to use one of the busiest parts of my site.

tokenring wrote: This support is now taking a long time for something that is simple and for something the team should be working on fixing.

Please be aware that all work on K 2.0 has ceased while the team focuses attention on the development of K 3.1 .

I do not know what dedicated, one-on-one support the team members can give you to assist with your current issues. Have you considered the possibility of using K 3.0?