Feature request - Move core controllers in to modules/core
Reported by dleffler | September 3rd, 2012 @ 03:01 PM | in 2.1.1 (closed)
It would be more logical to move the core controllers into the same folder as their views assets (which can be a hassle when working on a core controller like expComments)...this could be accomplished in one of two ways with the most recent code that looks for assets in the same folder instead of assuming they are in the /framework/modules folder.
- Move all but expController & expRecord out of /framework/core into the /framework/modules/core folder
- or move the /framework/modules/core items into /framework/core, however this will create logically grouping situation since we already have all the system wide assets and views in those folders
It MUST be noted that we can't move expController (or expRecord?) into the /framework/modules folder since it is traversed looking for modules unless we rewrite that code also.
Comments and changes to this ticket
-
dleffler October 26th, 2012 @ 05:10 PM
This would be the controller/model/definition/content_modelName:
- expCat
- expComment
- expDefinableField
- expHTMLEditor
- expModule
- expNestedNode
- expRating
- ExpSimpleNote
- expTag
- expConfig (no controller)
- geoCountry/geoRegion/keywords
-
dleffler January 19th, 2013 @ 04:18 PM
- State changed from “new” to “resolved”
- Milestone set to “2.1.1”
We'll merge this with ticket #144 Upgrade: Migrate core modules to controllers
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
Referenced by
-
144
Upgrade: Migrate core modules to controllers
We'll go ahead and merge ticket #704 into
here, Feature r...