Exponentcms Exponent CMS → 2.0.2

Comments and changes to this ticket

• 

  dleffler August 1st, 2011 @ 03:37 AM

  • Tag set to “subsystem”

  Would recommend beginning a simple conversion of the old subsystems. I could place a class wrapper and then refactor a name change across the project making them static calls (which seems to be the pattern for the 2.0 subsystem),

  e.g, in a general sense, subsystems/config.php would become framework/core/subsystems/expConfig.php and it would be wrapped in the expConfig class with the method names changing like exponent_config_parse becoming simply parse. Would be called as expConfig::parse().

  The intent is to migrate EVERYTHING in subsystems to the framework folder. Preferably without bringing over any unused stuff. However, might be better to bring it all over and then delete unused stuff rather than wait?

• 

  dleffler August 1st, 2011 @ 10:28 AM

  One positive change is the subsystems would now autoload instead of needing to check the constant is defined then doing an include_once/require_once.

• 

  dleffler August 2nd, 2011 @ 02:51 AM

  • Assigned user set to “dleffler”

  This list may help prioritize conversion/migration? (this is simply a starting draft):

  • Existing 2.0 subsystems w/ 1.0 subsystems (some 2.0 ones still use 1.0 calls)

    • expSession = sessions
    • expTheme = themes
    • expSorter = sort
    • expHistory = flow?
    • expJavascript = javascript
    • expLang = lang
    • expModule =? modules

  • 1.0 subsystems with no apparent 2.0 subsystem (@tt) & suggested 2.0 name?

    • autoloader -> expModule
    • backup??
    • config -> expConfiguration
    • core -> expCore??
    • database -> expDatabase
    • files -> expFilesystem
    • image -> expGraphics
    • forms -> expForms
    • permissions -> expSecurity
    • security -> expSecurity
    • users -> expUsers
    • template -> expTemplate
    • search -> expSearch??
    • info??
    • geo??
    • datetime -> expDateTime
• 

  dleffler August 2nd, 2011 @ 02:54 AM

  Actually users.php should migrate to usersController?

• 

  expNinja August 3rd, 2011 @ 03:32 AM

  (from [4447e09889164e7c33b7f633f99bbd39245f7821]) Moves the 1.0 (old school) subsystems out of root and into framework/core/subsystems-1, which is closer to where they'll be migrated in to. [#244 ] https://github.com/exponentcms/exponent-cms/commit/4447e09889164e7c...

• 

  expNinja August 3rd, 2011 @ 03:32 AM

  (from [3da0ec5a0ebb64dceb3b40c12489a4f9aac62880]) Deprecates all old school sort calls converting to expSorter::sort(), Adds a expSorter 'type' parameter now allowing index and key sorting [#244] https://github.com/exponentcms/exponent-cms/commit/3da0ec5a0ebb64dc...

• 

  dleffler August 3rd, 2011 @ 09:24 AM

  • State changed from “new” to “open”
  • Milestone set to “Stable”
  • Milestone order changed from “77” to “0”

  Now that the expSorter() is finished...I'll work on getting expTheme migrated (from theme.php) since it's seems to be used the most.

• 

  dleffler August 4th, 2011 @ 02:48 AM

  FWIW, the following have recently been deprecated by migrating the 1.0 functions/calls to a 2.0 subsystem:

  • theme = expTheme
  • sessions = expSession
  • security = expValidator
  • image = expFile
  • files = expFile

  And am testing the flow = expHistory update now

• 

  dleffler August 9th, 2011 @ 04:23 PM

  Update:

  • flow = expHistory
  • search = search (2.0 model)
  • info = fully deprecated
  • backup = brought back online awaiting migration, ticket #284
  • lang = work has begun, ticket #291
• 

  dleffler August 14th, 2011 @ 11:34 AM

  • Milestone changed from “Stable” to “2.0.1”
  • Milestone order changed from “5” to “0”

  Both lang & config (load/config) have been migratated/deprecated for stable release. Those 1.0 subsystems still remaining are:

  • backup was revived, but still needs migration
  • modules = expModules & expFramework
    • may move methods around/between expModules & expFramework to speed up page loading.
      
    • E.g., there doesn’t appear to be any legitimate reason for loading EVERY old-school module and 2.0 module & model, just to get a list of modules.
      
    • Might be better to revise the modstate table and update it similar to install_tables (expModuleController->manage()) and add them to the autoload function for handling. That could easily speed up ALL page loading.

  Those requiring a migration strategy before implementation can start are:

  • javascript = expJavascript
  • core = expCore?
  • database = expDatabase?
  • datetime = expDatetime?
  • forms = expForm?
  • geo??
  • permissions = expPermission?
  • template = expTemplate?
  • users = userController? Or user model?
• 

  expNinja August 20th, 2011 @ 02:34 AM

  (from [1b1080bc11a684cfd23e4b9b901729eb6d274fc2]) Migrate old 1.0 javascript subsystem to 2.0 expJavascript subsystem [#244 ] https://github.com/exponentcms/exponent-cms/commit/1b1080bc11a684cf...

• 

  expNinja September 5th, 2011 @ 10:01 PM

  (from [44ff35f3c6ca93581ce2186c11134ad019971ae4]) Deprecates 1.0 datetime subsystem to expDateTime 2.0 subsystem [#244] https://github.com/exponentcms/exponent-cms/commit/44ff35f3c6ca9358...

• 

  expNinja September 5th, 2011 @ 10:18 PM

  (from [e101331e0fc21e006c3554e7983415d1a9a4d3e0]) Missing (new) from administrationmodule & datetime subsystem deprecation [#244] https://github.com/exponentcms/exponent-cms/commit/e101331e0fc21e00...

• 

  expNinja September 5th, 2011 @ 10:19 PM

  (from [0efc364fae639c68ee03a05722fe01371296a1b3]) Deprecates 1.0 backupsubsystem to expFile model [#244] https://github.com/exponentcms/exponent-cms/commit/0efc364fae639c68...

• 

  expNinja September 5th, 2011 @ 10:20 PM

  (from [d17e2561e8799ea92a818bd12212e40423d40e44]) Removes calls to load old 1.0 backup subsystem [#244] https://github.com/exponentcms/exponent-cms/commit/d17e2561e8799ea9...

• 

  expNinja September 5th, 2011 @ 11:35 PM

  (from [bfb3fc71a6497229c9a9f0af946b6c6cb8b30cc6]) Almost deprecates 1.0 users subsystem moving calls into the user or group models. Calls still remain in disabled import usercsv method and expLDAP [#244] https://github.com/exponentcms/exponent-cms/commit/bfb3fc71a6497229...

• 

  dleffler September 7th, 2011 @ 12:38 AM

  As an update the following subsystems have also been deprecated and pushed to develop

  • backup
  • users
  • datetime

  Additionally, I have locally deprecated the following to be pushed up later this week:

  • geo
  • core
  • permissions
• 

  dleffler September 23rd, 2011 @ 06:09 PM

  • Milestone changed from “2.0.1” to “2.0.2”
  • Milestone order changed from “6” to “0”
• 

  dleffler September 24th, 2011 @ 09:08 PM

  • Title changed from “Migrate old school subsystems into framework/core/subsystems” to “Upgrade: Migrate old school subsystems into framework/core/subsystems”
• 

  dleffler September 30th, 2011 @ 04:48 PM

  As an update the only remaining 1.0 subsystems are:

  • database
  • forms
  • modules
  • template

  Though we also still have the theme compatibility layer in that folder. It will be removed once everything else is migrated?

  Database subsystem covered by separate ticket #198

• 

  dleffler October 1st, 2011 @ 01:13 AM

  More 1.0 subsystem migration working in the release/smarty3 branch:

  • forms -> all the forms & controls moved into 2.0 subsystems, still need to move the two methods in that subsystem, perhaps expFramework?
  • template -> expTemplate (each template class broken out into the forms folder)
• 

  expNinja October 11th, 2011 @ 03:15 PM

  • State changed from “open” to “resolved”

  (from [9dae0d187955c3ec4993ddbd5fe8a545dab0c741]) Deprecates old modules subsystem & moves controller function in expFramework into expModules [#244 state:resolved] https://github.com/exponentcms/exponent-cms/commit/9dae0d187955c3ec...