tyeung said

Mr Papa said

build 7392 does not include the fix for the odd js loading issue…  if you are not on svn or using the nightly builds, you will need to wait for our next beta update through the wp updater to see if it fixes it…  should be on Sunday…

Tried applying the latest build – 7468 – and now all the forums give me a “Invalid Database Query” error and a note that says “The requested forum does not exist” – even though I can see the list of forums.

this is what is in the error log from the simple press toolbox:  (gives same error no matter which forum I’m looking at, just the forum ID is different.)  My forum is essentially empty with exception of a few test posts but it’s happening in the empty forums as well as the one forum that has a couple posts in it.

So talk me through this. You updated via the wp updater – yes?
And then were sent through an upgrade of the forum process? Correct?
Did anything go wrong at this point?
The commands to create those new columns are in the upgrade script…

well, great news is, the new build allows for the upload function to work again!!!  WOOOOOHOO!!!

Now if I can just get the forums alive instead of causing the invalid database query errors – I’m golden!

Also, regret to report that trying to “edit” my post coughed up the following error just now when trying to edit my previous post to this topic:

Yellow Swordfish said

So talk me through this. You updated via the wp updater – yes?
And then were sent through an upgrade of the forum process? Correct?
Did anything go wrong at this point?
The commands to create those new columns are in the upgrade script…

Correct – went through the WP updater.

it completed the update with the yellow bar getting to 100% and reported “upgrade successful” or something to that effect – no errors anyway

then went to my forum and tried checking out one of the various forums, and that’s the error.

Not a HUGE deal as I can just blow them all away and recreate – but obviously don’t want it to happen when we start populating with content.

Huge deal for us though.

Can you check the /startup/install/sp-upgrade.php file.
Right near the bottom starting with the line:

$section = 7430;

should be 6 sql commands (4 ALTER tables a 2 UPDATEs)

Are they there? I will assume they are but the question is why did they not run on your database…

Just above those is a new table as well. Any chance you could check in with your database to see if that got created?

Yellow Swordfish said

Huge deal for us though.

Can you check the /startup/install/sp-upgrade.php file.
Right near the bottom starting with the line:

$section = 7430;

should be 6 sql commands (4 ALTER tables a 2 UPDATEs)

Are they there? I will assume they are but the question is why did they not run on your database…

Just above those is a new table as well. Any chance you could check in with your database to see if that got created?

Yep – the $section = 7430 stuff is all there.

and yes, the additional fields (post_id_held and post_count_held) within both SFFORUMS and SFTOPICS were in fact added…

I haven’t gone and deleted everything yet as I still need to copy and paste some of the data that was in there but I’ll try tonight when I get home and see if planets realign.

agh, forgot to mention one thing (and I can’t edit my post without it coughing up that fatal error)

When logged in as ADMIN, I can click the forums and I won’t get the “database query” error – although the sub forums do not show up.

If I am logged in as any standard user, if I click the forum, it gives the error.

the fix for the editing error has already been committed to svn…   thats what we get for making a change the night before we pushed out a build…

not sure what you mean… the error says the column does not exist, but you say it does?  can you clear the error log and then revisit the site and see if the same error shows up in the log?

are you running any db caching plugins?

Mr Papa said

the fix for the editing error has already been committed to svn…   thats what we get for making a change the night before we pushed out a build…

not sure what you mean… the error says the column does not exist, but you say it does?  can you clear the error log and then revisit the site and see if the same error shows up in the log?

are you running any db caching plugins?

I just completely blew away / deactivated & uninstalled SF and rebuilt the entire forum structure – I still get the database error!   The columns are definitely in the database but the error persists.

If I’m logged in as admin, everything is great – but a standard user gives the error…  I’m going to try assigning explicit permissions and see what happens…

Gentleman

Well, after a LOT of banging head on desk – I have discovered what the brain dead simple problem was – the forum didn’t have any topics posted in the parent forum (!).

Unless you are an admin, the forum coughs up that error mentioned above and will not display the list of subforums UNLESS there is at least ONE topic posted.

All I did was post a “welcome to the *whatever* forum” and refreshed, and voila, all the subforums show and there’s no errors.

Wow – thanks for tracking that down. I will get onto that this morning.

Yellow Swordfish said

Wow – thanks for tracking that down. I will get onto that this morning.

you bet… so far, things are working great !

keep up the great work guys!

thanks for the kind words!  great to hear now and then!

as expected, the number of beta testers has jumped with the formal release of wp 3.3, so the heat is up

Mr Papa said

thanks for the kind words!  great to hear now and then!

as expected, the number of beta testers has jumped with the formal release of wp 3.3, so the heat is up

no doubt! I hate filling your queue with so much stuff but I’m in the same boat with folks testing out the forum and “whining” at me  (can you do this, fix that, change this, yada yada yada)    😉 

np.  we were in alpha for several months… but no more issues were popping up so we went beta… its been pretty damn smooth but as more come on with different environments and different usage we still expect some issues…

and frankly, we want users using creating themes and plugins too in order to make sure that api is robust and sufficient…