Skip to:
Content

bbPress.org

Changes between Version 1 and Version 2 of Ticket #1937, comment 5


Ignore:
Timestamp:
05/18/2014 11:12:43 AM (8 years ago)
Author:
nirgalo
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1937, comment 5

    v1 v2  
    1010
    1111Here is my take on 3. (performance) :
    12 * as the feature has a performance impact, it would need to be proposed as optional (off by default)
     12* as the feature has a performance impact, it would need to be proposed as optional (off by default).
    1313* we need to store either read flag or unread flag associated to user/topic. The most natural way is to store a read flag. To be more specific, we probably need to store a last_visited flag such as the bbp-unread-posts plugin is doing, so we can mark a previously read message as unread without deleting a record, by setting its last_visited date to less than the post_last_activity flag (or to 0 simply). So we'll have one DB record per user/topic/last_visited state. Since this obviously can grow with the user base and number of read messages, I would suggest the following:
    14   - do not use post_meta or user_meta to store the read flag, use a separate table, bbPress specific. The post_meta would sill be used to provide an entry into the separate table, but this would not be per user. Need to design this more precisely.
     14  - do not use post_meta or user_meta to store the read flag, use a separate table, bbPress specific (need to design this more precisely).
    1515  - in the admin options, let the admin do maintenance and clear the read flag of topics older than n months (say 12 months by default).
    1616