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

guys! it's straight forward.

I'm in Quality Assurance too, so I'm sure I've been detailed in what is wrong with my site when explaining it.

There are two parts to the site. A front-end and a back-end. Do we all understand that?

My backend looks good. All the records are there. I ran the queries and provided the output for you guys to see. I even said to Matias that I have exported those two tables he told me to check that would be empty, and THEY ARE NOT!

What I'm saying is when you (in the Victorian sense) go to the front-end... all the categories show up as blank (no posts nor no topics)

So, when I upgraded from 1.7.2 to 2.0.4, the backend seemed to have been upgraded successfully, but when a user goes to the forums it is empty.

Here (again) is my upgrade path with status updates at end.

J1.5 / Kunena 1.7.2 - no issues
install J2.5 - new instance - no issues
install Kunena v1.7.2_b5215 on J2.5 site - no data - expected - no issues
perform SPupgrade -> DB all Kunena tables from J1.5 -> J2.5 K1.7.2 - no issues

*** okay, it is important to understand now at this point, my new J2.5 site running kunena v.1.7.2_b215 is working fine

now in the J2.5 site, I do an upgrade from 1.7.2 to any version other than 3.0 and all front end articles, posts, and topics are missing. Only the high level categories are there and are empty.

That is what I'm trying to say. Then you guys give me stuff to try and I don't hear back. I've showed you all I can show you.

A bit of other information is that this is on my test site for the J2.5 site. Because it is not working 1.7.2 to 2.X, I haven't done this part on my live site because it doesn't work. Once I sort it out, then I'll do it again on the live 2.5 site

Right now there are 2x J2.5 sites. One I attempted the upgrade like 3 times, and on the live site I won't dare.

Let me know if this makes sense now?

and I've got a great idea (well not really)

Wouldn't it be nice to just go to my site in question and look at what I'm saying?? Wouldn't that take out the ambiguity?

Aaron

Please post your Kunena Configuration Report (UN-EDITED) so someone can take a look.

tokenring wrote: Wouldn't it be nice to just go to my site in question and look at what I'm saying?? Wouldn't that take out the ambiguity?

The ambiguity will be eliminated and we will be happy to visit your site when you meet our "quality assurance" standards which is to post your unedited configuration report. Thanks.

PHP Built On Linux infong 2.4 #1 SMP Wed May 15 13:26:15 CEST 2013 i686 GNU/Linux
Database Version 5.1.67-log
Database Collation utf8_general_ci
PHP Version 5.2.17
Web Server Apache
WebServer to PHP Interface cgi-fcgi
Joomla! Version Joomla! 2.5.11 Stable [ Ember ] 26-April-2013 14:00 GMT
Joomla! Platform Version Joomla Platform 11.4.0 Stable [ Brian Kernighan ] 03-Jan-2012 00:00 GMT
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/28.0.1500.71 Chrome/28.0.1500.71 Safari/537.36

This is not the Kunena configuration report we have sought.

You have repeatedly stated "Why can't someone visit my site to see the problem." Perhaps if we knew where your site was, what exact version of Kunena you are using, and other software that interacts with Kunena that you are using, we might be able to do that. All of this information is neatly formatted, summarised and contained in the Kunena configuration report which you have declined to give us. That's OK; you are within you rights to withhold the information we seek. We might have pinpointed the cause of this issue a couple of weeks ago instead of this matter being guessed at, as best we can, in the information void that we're working within.

Evidently you seem reluctant to post the information that we would like to see. There is not a lot more that we can do to help you, sorry.