DB Error after upgrade

[GhostRider2110]

SMF 1.1.11
TP upgraded from 1.0b4 to 1.0b5

After the upgrade my front page gives the following error:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IFNULL(mem.realName,art.author) as realName FROM smf_tp_articles AS art
LEFT ' at line 2
File: /home/usscalem/public_html/forums/Sources/TPortal.php
Line: 2115

Note: It appears that your database may require an upgrade. Your forum's files are currently at version SMF 1.1.11, while your database is at version 1.1.6. The above error might possibly go away if you execute the latest version of upgrade.php.

Wondering where I screwed up..

Thanks
--Mitch

[IchBin]

A search would reveal it's an error that has been reported and is currently under review by bloc for a fix in the next release.

[GhostRider2110]

Thanks IchBin... I did a search, but must not have hit the right thread...  Is there an easy way to get back to where I was without a full restore from backup?

--Mitch

[GhostRider2110]

Not sure if another datapoint would help, but this only occurs on the front page.  Forums and so far the other areas I have looked at are OK..

See-ya
Mitch

[IchBin]

I "think" you should be able to uninstall, and reinstall beta4. If you make a backup of everything before you do, you shouldn't have any problems.

[Skhilled]

FYI: whenever you see something like this:

Note: It appears that your database may require an upgrade. Your forum's files are currently at version SMF 1.1.11, while your database is at version 1.1.6. The above error might possibly go away if you execute the latest version of upgrade.php.

You'll need to upgrade your database. SMF has db upgrade issues with 1.1.x versions and you'll probably get that same error when installing other mods. SMF upgrades the files but the db is not upgraded if you upgrade via the link in the admin.

To upgrade the db only, download SMF 1.1.11 (or the version that you are currently using) and extract the upgrade files that are in the root folder:

upgrade.php
upgrade_1-0.sql
upgrade_1-1.sql

Upload them to your root forum directory and run this in a browser:

http:///yoursite.com/upgrade.php

This will upgrade your database only since you have not uploaded the rest of the files. This may or may not fix the problem you are having but will correct the database upgrade issue. If you get a smiley error while upgrading follow the instructions in this link and try it again:

http://docs.simplemachines.org/index.php?topic=1079.0

[GhostRider2110]

Thanks Skhilled, I had tried that with no luck...  I was finally able to get things back up.  Had to recover from backup Source, Theme, and the base index.php and couple others...

Will wait to seen what comes of the possible fixes... If I have time I will see if I can gather more info on what my problem was.

Thanks
--Mitch

[shane is my name]

Hi, i had the same problem..  I found the solution by coincidence...  Go into your TiNyportal Blocks section, and turn off all HTML javascript Blocks... then the error will go away.

I think there must be something up with those blocks not using the code correctly. The only html javascript bvlocks that I can get to work are simple ones, like a link, etc...

I'm still experimenting, but will post a question on thsi later if I am just totally unabel to use javascript blocks...

[Skhilled]

If you turn off one at a time you might be able to narrow it down to which ones are causing it and just disable those until they are fixed.

[shane is my name]

Yeah It seemed that all of them with code (except the simple link one) would cause it to make an error on the HOME page.  odd.  and these are normal blocks that I was using in earlier TP beta 4. most were directly taken from this site block codes. so i know it isnt a user error. just something wrong with the beta i guess. I saw that there was a similar issue with php blocks and parsing etc.. maybe when they fix that, this will fix too?

UPDATE: ZarPrime just confirmed in another thread that it is a known issue and that it will be fixed in the soon released update to TP.