Actions
Feature proposal #6392
openImplement more specific Itemid usage
Description
Currently all profile URLs use the same Itemid. The reason for this is checking for user specific usages would result in a query per user URL. So the Itemid functionality needs to be improved with some sort of batching support (maybe allow $additional to be an array?) to query for and cache all at once (done in the same CBUser notify in advance usage?).
Updated by krileon almost 8 years ago
- Subject changed from Implement profile URL specific Itemid usage to Implement more specific Itemid usage
Renamed as this should be applying to any and all usages as much as possible. For example GJ URLs should be checking for group id or category id as well. The problem is fallback behavior needs to be present. So the $additional usage maybe should be an array then construct the query from that to ensure only 1 query is every made instead of multiple for fallback behavior.
Updated by krileon over 6 years ago
- Target version changed from CB 2.2 to CB 2.8
Updated by beat almost 2 years ago
- Target version changed from CB 2.8 to CB 2.8.1
Updated by beat about 1 year ago
- Target version changed from CB 2.8.1 to CB 2.8.2
Updated by beat about 1 year ago
- Target version changed from CB 2.8.2 to CB 2.9.0
Updated by beat about 1 year ago
- Target version changed from CB 2.9.0 to CB 2.9.2
Actions