Community
Participate
Working Groups
Hello, in the Eclipse Jubula Forum (http://www.eclipse.org/forums/index.php/f/208/)we would like to have a sticky thread giving some general information about Jubula, the forum and where documentation can be found since this is an recurring issue in most of the threads. As far as I know you have to be a moderator to create a sticky thread. Since we do not know a moderator it would be very nice if someone could help us with creating a sticky thread or tell us how to do this. Best regards Oliver
Go ahead and write a message the way you want it to appear, then post a link to it here and we'll mark it as sticky and always at the top.
Hi, this is the thread we would like to be sticky: http://www.eclipse.org/forums/index.php/t/246492/ Thank you for your help! Best regards Oliver
OK, I marked that thread as Sticky and to be pegged to the top of the forum.
Hi, thank you very much for making our thread sticky but it seems that it does not stay always on top (first thread starting at the top) because now there are already two threads above it. Is it possible to edit the thread so it will always be the first thread starting at the top? Thank you for all your effort! Best regards Oliver
Strange, the message is configured to stay at the top, but that particular forum group doesn't seem to be respecting it. I've used this feature a bunch in the Newcomers group (http://www.eclipse.org/forums/index.php/f/89/) without any problems, so I'm at a loss. Webmasters, can you take a look in the FUD internals to see if you can determine why this one isn't staying at the top like the ones in Newcomers?
There was a database inconsistency for the thread sequence table for that forum. I've dumped the master over the slave, and it all looks good now.
Hi, unfortunately the sticky thread has somehow become "un-sticky" and does not remain on the top of the first page of the Jubula Forum. Can anyone help us with that? Thanks in advance and best regards Oliver
The message still had the "Make the topic always appear at the top of the topic listing" option set, but it was definitely NOT at the top. I removed and re-applied the sticky and "Make the topic always appear at the top of the topic listing" options for this message and now it appears at the top again. If it happens again I think one of the webmasters will have to investigate the forum database and/or code to see why those options aren't being respected.
It was at the top but now it moved again, something is wrong here.
It looks ok to me when I load the Jubula forum main page. Eric did you re-apply your changes? -M.
Right now, there is another topic ("SWT_AWT bridge") above the sticky one. I have not made any changes since comment 8.
Unfortunately the thread is still not sticky and moves to the bottom of the first page. Do you have new information on this issue? Regards Oliver
The sticky thread is now somewhere in middle of the first page so it´s very unlikely that this is going to be the thread that (new) members will read first. Is there any new information why this thread is moving? Thanks for your help. Regards Oliver
Hello, I hope you all had nice holidays. Unfortunately the "sticky" thread that is supposed to be an intro to the Jubula Forum is still not sticky and has moved to the second page of the forum. Could you please take a look at it because nothing really happened since middle of November? Thanks in advance. Best regards Oliver
This "may" have something to do with a single thread that may or may not have been deleted in the past. Here's the cause of this: on the master db, if I run this query, I get: mysql> SELECT seq FROM fud_tv_208 ORDER BY seq DESC LIMIT 1; +-----+ | seq | +-----+ | 234 | +-----+ However, on the slave, I get: mysql> SELECT seq FROM _fud_tv_208 ORDER BY seq DESC LIMIT 1; +-----+ | seq | +-----+ | 233 | +-----+ So it's "off-by-one". On the master, I simply dump and reload the table and all is well: $ mysqldump -u root -p fudforum --tables fud_tv_208 > fud.sql $ mysql -u root -p fudforum < fud.sql I'll close this as FIXED - if this happens again, please reopen and I'll see what's happening in our mysql binlogs that would explain the inconsistency.
Closing this.
