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
-
dleffler February 12th, 2013 @ 02:59 AM
- Assigned user set to “dleffler”
We also need to do better styling on the 'order' in chrome so it don't look like a button, but a menu item
-
dleffler February 12th, 2013 @ 03:00 AM
- Title changed from “Bug: 'rank's are not indexed consistently” to “Bug: 'rank's are not indexed consistently & ddrerank doesn't appear correclty in nested containers”
We also have a problem with the ddrerank and nested containers which disables the parent menu item and attaches the rerank panel to the child menu item
-
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...
-
dleffler February 13th, 2013 @ 02:18 AM
It would be best to have ranks begin at '1' as we've been doing in 2.0 stuff, so we'll need to adjust some of the container code, including the upgrade script to rerank everything beginning at 1...a general save rank = rank +1 would work once, but if you ran the script a 2nd (or more) times, it'd get weird
-
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...
-
dleffler February 13th, 2013 @ 04:58 AM
Still have an issue w/ ddrerank and we always rerank when adding/deleting a container (unlike in 0.9x)
-
dleffler February 13th, 2013 @ 02:23 PM
- State changed from “new” to “resolved”
Pretty sure this one is licked
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 new ticket
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
dleffler
expNinja
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...