vBulletin 3.5.4

[gonaads]

Re: vBulletin 3.5 Beta

O.K.

I am NOT, I repeat NOT complaining. But I thought ya might wanna know that when ya click on "Quick Links" on the link bar at the top of the page, it does some weird ass shiit.


Hint... The link bar changes.


"Quick Links" disapears and "Mark Forums Read" and "Open Buddy List" takes it's place.

Now that ain't no bug, them's frickin gremlins man.

 

[Electronic Punk]

Re: vBulletin 3.5 Beta

Once again it could be down to cached functions?

 

[X-Istence]

Re: vBulletin 3.5 Beta

Works perfect here.

 

[gonaads]

Re: vBulletin 3.5 Beta

Seems to be a Firefox issue. It also manifests itself with DeerPark Alpha 1. And this is at home and at work. Mozilla has no such problem, neither does IE.

BTW, cache and cookies have been cleared on both machines.

 

[Xie]

Re: vBulletin 3.5 Beta

Can anything be done with the new post timeouts? Like for example a thread has more then 1 page. I go to read say pay 3 and upon opening notice that indeed I wanted page 2, BUT when clicking page 2 all posts already show as read as do the ones on page 3 now. Never use to do this till you moved on to another thread.

 

[Khayman]

Re: vBulletin 3.5 Beta

I thought one of the features of 3.5 was that posts and threads stayed unread until you actual read them (or marked them as read) and not after just viewing the titles for a while (such as a new posts search)

 

[Electronic Punk]

Re: vBulletin 3.5 Beta

that could make the database huge

 

[X-Istence]

Re: vBulletin 3.5 Beta

I thought one of the features of 3.5 was that posts and threads stayed unread until you actual read them (or marked them as read) and not after just viewing the titles for a while (such as a new posts search)

It does indeed not make them marked read. What Xie is complaining about is the fact that he goes to read the thread, stumbles onto Page 3 of a 3 Page thread, and notices he has not read all from Page 2. So he goes back to Page 2, and now all the posts he has never read are marked as read. This used to be otherwise, but they have changed how it works, i prefer the new way. I have a photographic memory, and can remember where i stopped reading in a thread .

Nothing can be done about it Xie.

Epunk: It was hopefully designed to be in a more than HUGE database way, if not, the database is going to be huge.

 

[Xie]

Re: vBulletin 3.5 Beta

Nothing can be done about it Xie.

Or can something be done? *waves hand like jedi*

 

[X-Istence]

Re: vBulletin 3.5 Beta

Or can something be done? *waves hand like jedi*

I HATE STAR WARS.

Nothing can be done.

 

[Xie]

Re: vBulletin 3.5 Beta

I HATE STAR WARS.

Nothing can be done.

True. You seem to have fallen to the dark side already.

 

[zeke_mo]

Re: vBulletin 3.5 Beta

Did anybody notice that you can double click to edit your posts?

I like

 

[Tittles]

Re: vBulletin 3.5 Beta

Did anybody notice that you can double click to edit your posts?

I like

Yes we did :lick:

 

[zeke_mo]

Re: vBulletin 3.5 Beta

 

[gonaads]

Re: vBulletin 3.5 Beta

hahahaha... oooops

 

[Xie]

Re: vBulletin 3.5 Beta

I made an interesting observation. If say a thread had 4 pages and I accidently clicked page 2 instead of 4, when I went to page 4 new posts would still show as new like normal. So I guess you just have to play it safe in active threads w/ multiple pages now as if you go a page more then you've read and go back all those new posts will show as read already.

 

[Electronic Punk]

Re: vBulletin 3.5 Beta

I thought one of the features of 3.5 was that posts and threads stayed unread until you actual read them (or marked them as read) and not after just viewing the titles for a while (such as a new posts search)

Thread/Forum Read Marking Type This option controls how threads and forums are marked as read.
Inactivity/Cookie Based - once a user has been inactive for a certain amount of time (the value of the cookie timeout option) all threads and forums are considered read. Individual threads are marked as read within a session via cookies.

This option is how all versions of vBulletin before 3.5 functioned.

Database (no automatic forum marking) - this option uses the database to store thread and forum read times. This allows accurate read markers to be kept indefinitely. However, in order for a forum to be marked read when all threads are read, the user must view the list of threads for that forum.

This option is more space and processor intensive than inactivity-based marking.

Database (automatic forum marking) - this option is the same as a previous option, but forums are automatically marked as read when the last new thread is read.

This is the most usable option for end users, but most processor intensive.

 

[Xie]

Re: vBulletin 3.5 Beta

Hey EP you mess with sigs code or did it change in new beta? Oh and typing this the new reply box is ... interesting.

 

[Electronic Punk]

Re: vBulletin 3.5 Beta

I had to revert alot of templates, got local copies.
will change it back

Edit (with ajax ... har): DONE

 

[~bk]

Re: vBulletin 3.5 Beta

The new quick reply box looks sweet.