vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB4 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=251)
-   -   Why Disapperar New Posts after Reading (https://vborg.vbsupport.ru/showthread.php?t=327058)

tbellik 01-28-2019 06:43 AM

Why Disapperar New Posts after Reading
 
Hi.

When I click new posts and read the posts, then I again click new posts , the posts is disapperar which is I read.
I dont want to disapper it, and always want to see that, it is like activity.

Is it possible to do this ?

https://vborg.vbsupport.ru/external/2019/01/4.png

MarkFL 01-28-2019 04:59 PM

What version of vB are you using?

iA1 01-28-2019 05:46 PM

Those threads disappear after opening them because they no longer remain "new". New post search is only meant for those posts that are unread.

If you want to see those threads again in the search result, use Today's Posts search instead of New Posts search.

MarkFL 01-28-2019 06:37 PM

Quote:

Originally Posted by iA1 (Post 2598269)
Those threads disappear after opening them because they no longer remain "new". New post search is only meant for those posts that are unread.

If you want to see those threads again in the search result, use Today's Posts search instead of New Posts search.

Older versions of vB 4 (before 4.2.5) have the option to either use a cookie based thread marking system or a database based system. Those using the cookie based system will still see the read threads, only not in bold, in the "New Posts" query.

I much prefer the database marking system, and have been using it since vB 4.2.1. It does cause some confusion to people who have been using the cookie based system, and then upgrade to vB 4.2.5 and find the "New Posts" query suddenly behaves differently.

I think the best advantage to the database system is that it is device/browser independent. Once you've read a thread, the system kows you've read it even if you change to another browser or device.

tbellik 01-30-2019 05:02 PM

Quote:

Originally Posted by MarkFL (Post 2598270)
Older versions of vB 4 (before 4.2.5) have the option to either use a cookie based thread marking system or a database based system. Those using the cookie based system will still see the read threads, only not in bold, in the "New Posts" query.

I much prefer the database marking system, and have been using it since vB 4.2.1. It does cause some confusion to people who have been using the cookie based system, and then upgrade to vB 4.2.5 and find the "New Posts" query suddenly behaves differently.

I think the best advantage to the database system is that it is device/browser independent. Once you've read a thread, the system kows you've read it even if you change to another browser or device.

I just want to see topic there bold or not bold not important.

I upgraded my forum from 4.2.3 to 4.2.5 and started this problem.

Could you please define me how can I make this settings?

MarkFL 01-30-2019 06:27 PM

One big issue I have with vB sites who use the older cookie based thread marking is that threads disappear from the list even when I didn't read them. With the databse based marking this doesn't happen until after the number of days specified, and I use 10 days as the limit on the sites I admin.

Once you've read a thread, it is no longer new and shouldn't be included in the "New Posts" query. Doesn't that make perfect sense to you? When I click "New Posts" I only want to see threads with posts in them that I haven't read yet.

You can always use the "Today's Posts" query, or create a query for "This Week's Posts" and add it to your navbar if you wish to see all threads with recent posts in them.

There is no way I know of to revert back to the cookie-based thread read marking method once you upgrade to vB 4.2.5. I think once you get used to it, you will begin to understand how much better it is, and why the older method was discontinued. :)

tbellik 01-30-2019 06:43 PM

Quote:

Originally Posted by MarkFL (Post 2598301)
One big issue I have with vB sites who use the older cookie based thread marking is that threads disappear from the list even when I didn't read them. With the databse based marking this doesn't happen until after the number of days specified, and I use 10 days as the limit on the sites I admin.

Once you've read a thread, it is no longer new and shouldn't be included in the "New Posts" query. Doesn't that make perfect sense to you? When I click "New Posts" I only want to see threads with posts in them that I haven't read yet.

You can always use the "Today's Posts" query, or create a query for "This Week's Posts" and add it to your navbar if you wish to see all threads with recent posts in them.

There is no way I know of to revert back to the cookie-based thread read marking method once you upgrade to vB 4.2.5. I think once you get used to it, you will begin to understand how much better it is, and why the older method was discontinued. :)



Thanks for your answers. Is it posible to show last week, this week and last month messages ?

If yes, please which code just say me

MarkFL 01-30-2019 07:12 PM

For "This Week's Posts" I added a link under quick links in the Navigation Manager of the form:

Code:

search.php?{session.sessionurl}do=getdaily&days=7&contenttype=vBForum_Post

tbellik 01-31-2019 10:21 AM

Quote:

Originally Posted by MarkFL (Post 2598304)
For "This Week's Posts" I added a link under quick links in the Navigation Manager of the form:

Code:

search.php?{session.sessionurl}do=getdaily&days=7&contenttype=vBForum_Post

It was great news for me, thank you.

alfuzzy 02-01-2019 07:50 PM

Quote:

Originally Posted by MarkFL (Post 2598301)
Once you've read a thread, it is no longer new and shouldn't be included in the "New Posts" query. Doesn't that make perfect sense to you? When I click "New Posts" I only want to see threads with posts in them that I haven't read yet.

Hey Mark glad you mentioned this. I upgraded to 4.2.5 a few months ago...and I miss how the old system handled "New Posts". Usually they would go from bolded to non-bolded after reading them...and using the back button on the browser to get back to the new posts list.

Now when this is done with 4.2.5 (read a thread with new posts from the new posts list...then using the back button)...the post that was just read stays bolded even though its been read. Only if the refresh button is pressed does the new post that was just read go from bolded to non-bolded.

AND...the new post that was just read stays in the new post list (even after pressing the browser refresh button)...except it does go from bolded to non-bolded.


All times are GMT. The time now is 05:38 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01124 seconds
  • Memory Usage 1,743KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (2)bbcode_code_printable
  • (5)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete