Upgraded from UBB.classic 6.7.1 to UBB.threads 7.0.1 then 7.0.2.

We thought we lost one of the threads we were using as an informative sticky at the beginning of one of the forums. Clicking through each page of that forum and searching for that author did not reveal it (nor did a "Show User's Posts" - at least we didn't find it). But it wasn't important enough to worry about so we forgot about it.

Then I was reading the first post in that forum and clicked on "Next Topic". Lo and behold that thread was displayed. It was still a sticky but just not being listed in that forum. I unstickied it to see if that would get it listed in that forum. Nothing. So I restickied it and left it (and I can now find it by clicking "Next Topic" while in the first post of that forum).

Ideas?

I had a problem importing stickied threads a couple months ago... sorry to hear that it still might be an issue. What I did was un-sticky the threads, then start over. It was okay after that.. :/

You can do a database query to unsticky them all and they'll show up. Unfortunately you'd need to find them and resticky them afterwards. If you want to go this route you can run the following sql command:

update ubbt_TOPICS set TOPIC_IS_STICKY='0'

update ubbt_TOPICS set TOPIC_IS_STICKY='0' worked to unstick all of the sticky threads. When I viewed a listing of each forum the stickys were gone.

BUT, when I went back to re-sticky each of the topics I got this error message for each and every thread that was unstickyed with the SQL command:

Script: ../forums/scripts/stickpost.inc.php
Line#: 123
SQL Error: Duplicate entry '426-1' for key 1
SQL Error #: 1062
Query: INSERT INTO ubbt_ANNOUNCEMENTS VALUES ( 426 , 1 )

Please use your back button to return to the previous page.

[I shortened the directory. Also the '426-1' was different for each but I think all of them were the same SQL error 1062.]

ok, you'll need to clear out the announcements table as well by running this query:

DELETE FROM ubbt_ANOUNCEMENTS

Such an ugly term. -

Well, it appears to be working properly. Are there really duplicate entries in ubbt_ANNOUNCEMENTS VALUES or did it attempt to make duplicate entries and complain because it could not make the duplicate entry?

What happens if I don't do a DELETE FROM ubbt_ANOUNCEMENTS?

Also, doesn't a SQL command need to specifically delete something specific. That command has me worried!

Basically the announcements table keeps track of which topics are sticky. With the first command I gave you that set all topics to unsticky in the topics table, but didn't account for those in the announcements table. Those 2 commands go hand in hand. What's happening is those that you are trying to make sticky again are already in the announcements table and you're getting the error.

Thanks for the response. I realized as much.

What happens if I don't do a DELETE FROM ubbt_ANOUNCEMENTS?

Can I just leave it alone at this point or do I need to repeat the two commands?

If you have all of your stickies working as intended, then don't worry about running that command.