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

Does this mean that the missing topics problem has also been fixed?

sozzled wrote: Does this mean that the missing topics problem has also been fixed?

Sorry, for the brief hope of victory there. I just meant it installed fine. I read the FAQ and saw the issues with upgrading. I used the recommended way and it worked.

There are no "Strict Standards" errors anymore on that site and I'm using the newest version of everything. K3.0.1 is installed. I'll check the admin control panel and see if there is any new tools or anything obvious that I can do.

On the live site www.funkyhousebeats.com I've enabled php 5.4 and the strict errors are there as expected. I'm updating what I can do remove the errors, however some of my fixes for these errors were done by others. I'm just looking at the files they changed to see what they have done. I want to understand. I'll do a diff on them first.

... only issue is kunena is one of the extensions that's throwing the error. If I upgrade that, I'm going to lose my front end data (or lose the connection/reference point to it)

Aaron

So ... I'm confused.

What is the situation on your K 3.0.1 test site? Do you have your topics intact now?

I am eager to see this topic - this "K 1.7.2 -> K 2.0.4: all my topics are missing" topic - resolved, closed and consigned to the archives.

Now that we are no longer discussing K 2.0.4 I think we're nearing the end of this story.

You can turn off the error reporting for PHP, those errors dont stop it from working, they just let you know something is not working perfectly. You have to alter the ini file for your server.

Are the forums all working correctly now?

I've said it 2 times above and it's like pulling teeth eh? I said sorry for the false hopes of victory and the message before that was in reference to the *upgrade*, not the display of topics/replies, if you can see what's the context of the message.

No, the topics are not displaying.

I'm sorry for whatever reason you and jim may seemed bothered by again.

I know about this. They still appear when I set the setting to "disabled". I didn't care to investigate the setting, the files got changed.