phpWebSite Content Management System / Patches / #100 DBPager::cacheQueries fix

#100 DBPager::cacheQueries fix

Milestone: Core Class

Status: closed-fixed

Owner:

Labels: Code/Logic (73)

Priority: 5

Updated: 2008-07-14

Created: 2008-07-13

Creator: Eloi George

Private: No

DBPager::cacheQueries is very nice. However, there is a problem if a user queries different pager objects using the same template.

Example: JoeBob pulls up a listing of topics in forum #1 on one browser window & a listing of forum #2 on another. If he leaves forum #1 to look at an item, then looks at page 2 on forum #2, then leaves the itemview in the first window to go back to forum #1, the cache will cause him to see page 2 of forum #1 (which he hasn't been to).

This patch adds a method (DBPager::setCacheIdentifier()) which will allow you to set unique identifiers for every type of pager view (ex: "forumview_1" & "forumview_2"). If an identifier is not set, it defaults back to the template name.

Discussion

Eloi George - 2008-07-13

Patch to /core/class/DBPager.php

DBPager.patch.txt

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2008-07-14

Logged In: YES
user_id=400519
Originator: NO

thanks for the patch. added to svn

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2008-07-14

status: open --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

DBPager::cacheQueries fix

Group

Searches

Help

#100 DBPager::cacheQueries fix

Discussion