Bug: 'rank's are not indexed consistently & ddrerank doesn't appear correclty in nested containers
Reported by dleffler | February 12th, 2013 @ 01:12 AM | in 2.2.0alpha2 (closed)
e.g., in expRecord we rank starting at '1', but most of the time (and in old school containermodule), we start at '0'.
Must determine the correct index start, then update all associated 'wrong' code.
Comments and changes to this ticket
-
expNinja February 13th, 2013 @ 01:43 AM
(from [a910b898785c1356374d5dcff4817ca7f0ceacca]) Reverses some recently introduced quirks regarding display of nested containers and container rank's[#917] https://github.com/exponentcms/exponent-cms/commit/a910b898785c1356...
-
expNinja February 13th, 2013 @ 04:58 AM
(from [b2e8503874120c24af9a3426494481faa424d5c1]) Should fix many of the quirks regarding display of nested containers and container rank's, including the upgrade script [#917] https://github.com/exponentcms/exponent-cms/commit/b2e8503874120c24...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS
People watching this ticket
Tags
Referenced by
- 909 Bug: container2 add module doesn't work as expected (from [cecd5e178a2f41a75ec6de42c315c377abc39eee]) Removes...
- 892 Feature request - Removed deprecated modules/files (from [cecd5e178a2f41a75ec6de42c315c377abc39eee]) Removes...
- 908 Bug: major database/table upgrades (from [cecd5e178a2f41a75ec6de42c315c377abc39eee]) Removes...