Project

General

Profile

Actions
Copy link

Bug #7967

open

Tab output doubles if rendered in 2 different positions

Bug #7967: Tab output doubles if rendered in 2 different positions

Added by krileon over 6 years ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Low
Assignee:
krileon
Target version:
CB 2.11.1
Start date:
29 April 2020
Due date:
% Done:

100%

Estimated time:

Description

If a tab is rendered in 1 position via substitution in a Custom HTML field then is also set to display normally in a visible tab position then the display of the tab is doubled when output in the visible tab position. This is reproducible by moving the User Status tab to Main Canvas Right on a site with CB Quickstart since the tab is inline output under About already.

https://www.joomlapolis.com/forum/153-professional-member-support/242433-cb2-4-5-user-status-is-doubled-in-tab-account#318166

Updated by krileon over 6 years ago Actions
Copy link
 #1

  • Priority changed from Normal to Low

This is due to the caching behavior in generateViewTabsContent. This bug has likely been present forever and just now discovered. Moving to low priority as it's extremely uncommon to even need to double output a tab.

Updated by beat over 6 years ago Actions
Copy link
 #2

Isn't that a desired behavior ? There are situation where you want to double the output of a field or of a tab....

Updated by beat about 6 years ago Actions
Copy link
 #3

  • Target version changed from CB 2.4.6 to CB 2.4.7

Updated by beat almost 6 years ago Actions
Copy link
 #4

  • Target version changed from CB 2.4.7 to CB 2.5.0

Updated by beat over 5 years ago Actions
Copy link
 #5

  • Target version changed from CB 2.5.0 to CB 2.6

Updated by beat over 5 years ago Actions
Copy link
 #6

  • Target version changed from CB 2.6 to CB 2.6.1

Updated by beat about 5 years ago Actions
Copy link
 #7

  • Target version changed from CB 2.6.1 to CB 2.7

Updated by beat over 4 years ago Actions
Copy link
 #8

  • Target version changed from CB 2.7 to CB 2.7.2

Updated by beat over 4 years ago Actions
Copy link
 #9

  • Target version changed from CB 2.7.2 to CB 2.7.3

Updated by beat about 4 years ago Actions
Copy link
 #10

  • Target version changed from CB 2.7.3 to CB 2.7.4

Updated by krileon almost 4 years ago Actions
Copy link
 #11

  • Target version changed from CB 2.7.4 to CB 2.8

Updated by beat over 3 years ago Actions
Copy link
 #12

  • Target version changed from CB 2.8 to CB 2.8.1

Updated by beat almost 3 years ago Actions
Copy link
 #13

  • Target version changed from CB 2.8.1 to CB 2.8.2

Updated by beat almost 3 years ago Actions
Copy link
 #14

  • Target version changed from CB 2.8.2 to CB 2.9.0

Updated by beat almost 3 years ago Actions
Copy link
 #15

  • Target version changed from CB 2.9.0 to CB 2.9.2

Updated by beat about 2 years ago Actions
Copy link
 #16

  • Target version changed from CB 2.9.2 to CB 2.9.3

Updated by beat almost 2 years ago Actions
Copy link
 #17

  • Target version changed from CB 2.9.3 to CB 2.10.0

Updated by beat over 1 year ago Actions
Copy link
 #18

  • Target version changed from CB 2.10.0 to CB 2.11.0

Updated by beat 10 months ago Actions
Copy link
 #19

  • Target version changed from CB 2.11.0 to CB 2.11.1

Updated by krileon about 2 months ago Actions
Copy link
 #20

This is caused by the tabsContents cache. It's strictly caching by id. The problem is the function response being cached includes $user, $output, $formatting, and $reason. All of which alter how the tab is going to actually display. So the caching is not accurate. Tab responses need proper cache keys.

Updated by krileon about 2 months ago Actions
Copy link
 #21

The double foreach loop was the bigger culprit. Removing that appears to solve the cache busting issues.

Updated by krileon about 2 months ago Actions
Copy link
 #22

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

Fixed in !2023

Actions
Copy link

Also available in: PDF Atom