You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
By design f:cycle stores its state in a static property, which keeps it state for the whole php/rendering process. This means that when there are 2 modules using f:cycle on the page, the cycle never resets itself.
For example in a situation where 20 elements are being cycled:
I hope this is the right place to share this.
Problem
By design f:cycle stores its state in a static property, which keeps it state for the whole php/rendering process. This means that when there are 2 modules using f:cycle on the page, the cycle never resets itself.
For example in a situation where 20 elements are being cycled:
If a module on the page has 10 items, adding a 2nd module on the page starts the cycle at 11. Which might not be the desired outcome.
Suggestion
I would like to propose a
reset="1"
function where instead of saving the cycle state, it resets at every new implementation on the page.The text was updated successfully, but these errors were encountered: