Merge locatonref table into sectionref table
Reported by dleffler | May 6th, 2011 @ 10:55 PM | in Release Candidate 1 (closed)
locationref seems to be a subset of the sectionref table and sometimes they don't get updated to compliment each other. Will attempt to see if we can do away with locationref table and just have everything use the sectonref table.
Comments and changes to this ticket
-
dleffler May 14th, 2011 @ 03:58 AM
- Milestone changed from “Stable” to “Release Candidate 2”
- Milestone order changed from “1” to “0”
-
dleffler June 4th, 2011 @ 05:33 PM
Still need to build an upgrade? script to 1) copy missing info from locationref into sectionref table, and 2) delete locationref table or set it for removal.
-
dleffler June 14th, 2011 @ 11:28 AM
- Milestone changed from “Release Candidate 2” to “Release Candidate 1”
- Milestone order changed from “2” to “0”
-
dleffler June 21st, 2011 @ 08:48 PM
- Title changed from “Investigate merging locatonref table into sectionref table” to “Merge locatonref table into sectionref table”
Running this as a test shows no problems (though none were expected.)
-
expNinja July 26th, 2011 @ 04:03 PM
- State changed from “open” to “resolved”
(from [1000a88c508e0b3fa3225920d6558c071687ba77]) Replaces all occurrences of locationref with sectionref. Should resolve some of the disconnects between the two tables, and locationref was redundant anyway. [#178 state:resolved milestone:'Release Candidate 1'] https://github.com/exponentcms/exponent-cms/commit/1000a88c508e0b3f...
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