TP 1.0 Beta 5-1 w/ SMF 1.1.11 database error

[Skhilled]

This error should be fixed in the next release.

[Greyhound]

I find it interesting that this isn't being considered a bug.  I installed SMF, changed a few images, installed TP, made one post, wrote one intro article and tried to create a category bloc on the left panel and it locked the DB up.

[ZarPrime]

Greyhound,

Was everything working fine until you tried to add the "category" block?  And was that the standard "Articles in a Category" TP Block, or are you referring to another type of block?

I don't think anyone came right out and said that is isn't being considered a bug.  It's just that, if you are the only person who experienced this problem, it is more likely a problem with your site than a genuine TP bug.

If everything was fine before adding the block, my suggestion at this point would be to go into your database via phpMYAdmin and remove the block manually in there and see if that fixes the issue.  Then try doing the same thing again but, before doing so, make sure that you actually have categories that contain articles that you can select.

ZarPrime

[Greyhound]

Yes, everything was working fine before I added the category block and yes it is the canned one in TP.   It was a brand new site before it happened.  I'll go to phpmyadmin and try to remove it.   I posted it in the bug tracker and was told it shouldn't be in there yet.  I understand if I posted the bug tracker ticket incorrectly. 

Right after I posted this thread someone responded that it happened to them so I don't think I'm the only person.

I just wanted to get this problem worked out before I moved forward the site so it doesn't happen again or cause me or anyone else to lose significant data.

[Greyhound]

For the record.  I went into phpmyadim like ZarPrime suggested and removed the category block there and it unlocked my site.  It must be trying to read something that is causing the error.  I'm going to try it again and see what happens.

[Greyhound]

Another update:

I tried to reinstall it.  I only clicked to show it on the front page.  Now the front page is giving me that error but the forums and other sections work.  Seems like wherever that block goes it locks up those pages.

When I turn it off, everything goes back to normal.

[Greyhound]

The actual name of the block that's giving me the problem is "Articles in a Category".

[ZarPrime]

Greyhound,

OK, well then, this may indeed be a bug but only when using TP 1.0 beta 5-1 with SMF 1.1.11, not with SMF 2.0 RC3.  An expanation ~ I haven't personally tested the "Article in Catagories" block yet with beta 5-1 on SMF 1.1.11, only on RC3.  My SMF 1.1.x test site is still using TP 1.0 beta 4 for now.  Perhaps later today I will go ahead and upgrade my SMF 1.1.x test site to beta 5-1 and then I can test this behavior.

In the meantime, if someone else tests this in SMF 1.1.11 with TP beta 5-1 and the same thing happens, please let us know here and then we can definitely call this a bug.

Greyhound, as far as posting to the bugtracker goes, that's what it's for, if a bug has been verified here in the Support Board.  If you post something here in Support and we test it and find out that the same thing is happening for us, then we will certainly ask you to post the bug in the BT, but we would prefer to verify that it is indeed a bug here before asking you to post it there.  Since I can't yet verify it, it's better to leave it here for now.

ZarPrime

[IchBin]

GreyHound, it's not that I didn't think it was a bug. I didn't know you had started this topic, and I hadn't seen anyone confirm this is a bug. It looks to me like this is related to the DB changes that Bloc has made. I'll see if I can get the same problem on my SMF1.1.x install.

[IchBin]

Open Sources/TPortal.php and find this on about line 2148

$request =  tp_query("SELECT art.id, art.subject, art.date, art.category, art.authorID, art.shortname

Add a comma to the end of that line so it looks like this:
$request =  tp_query("SELECT art.id, art.subject, art.date, art.category, art.authorID, art.shortname,

That should fix it.