Exponentcms Exponent CMS → 2.0.4

Comments and changes to this ticket

• 

  expNinja August 24th, 2011 @ 08:30 PM

  (from [ab36dfd8f3bb10c1a387cfce1c2088c8870433b9]) Minor updates to expVersion to prepare for possible online version update check in the future. [#314] https://github.com/exponentcms/exponent-cms/commit/ab36dfd8f3bb10c1...

• 

  dleffler September 15th, 2011 @ 02:17 PM

  • Assigned user set to “dleffler”
• 

  dleffler September 23rd, 2011 @ 06:10 PM

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

  dleffler October 14th, 2011 @ 03:47 PM

  • Milestone cleared.
• 

  dleffler December 14th, 2011 @ 12:57 PM

  • Tag set to “installer”
  • Milestone set to “2.0.4”
  • State changed from “new” to “open”
  • Milestone order changed from “6” to “0”
• 

  dleffler December 14th, 2011 @ 02:09 PM

  Will be incorporated as a part of ticket #421, the install/upgrade process revision.
  

  • IF an update is found, the admin user will will be notified (via flash message) that they should update the site after logging in (page load) and given a link to launch the update.
• 

  expNinja December 15th, 2011 @ 10:17 PM

  (from [7a56c4d222a176d82bf3b507d4786ca3915b5dbe]) Better handling of situations where no database connection is present...now sends you to the maintenance screen with a note that the database is offline. Also updates version checking in preparation for online version checking and the new install/upgrade process for the next release version. Adds new method to expDateTime to format and return a date based on system settings [#314 #421] https://github.com/exponentcms/exponent-cms/commit/7a56c4d222a176d8...

• 

  expNinja December 24th, 2011 @ 04:03 AM

  (from [12a81dda0896ddc865dbcc1dd732c214876954c3]) Revises install/upgrade process to no longer be semi-automated. Now installation MUST be called explicitly and if an 'upgrade' condition exists, but the site is still configured, the admin user will be notified with a link to upgrade the site after logging in. Also contains the basics for doing an online version check displaying a notice once per session. Still need a location (or new method) to store the version check. [#421 #314] https://github.com/exponentcms/exponent-cms/commit/12a81dda0896ddc8...

• 

  expNinja December 24th, 2011 @ 04:33 AM

  (from [9eef6c36511bc643e42331b06e0d0a27a3b69915]) Cleaner version of json return software version. Now stand-alone with hard-coded version info. Exponent installation not required [#314] https://github.com/exponentcms/exponent-cms/commit/9eef6c36511bc643...

• 

  expNinja December 24th, 2011 @ 04:43 AM

  (from [c3e9e3de236b34cfd0fe6b3d3787b63261bfb2db]) Cleaner version of json return software version, now stand-alone with hard-coded version info; Exponent installation not required. includes sample version (2.0.5) to force situation. [#314] https://github.com/exponentcms/exponent-cms/commit/c3e9e3de236b34cf...

• 

  dleffler December 24th, 2011 @ 11:15 AM

  May consider adding a setting to site configuraton about the frequency of checks. this value would be added to the session variable to check for elapsed time before checking again.

• 

  expNinja December 24th, 2011 @ 11:38 AM

  (from [57ef0ba6e8830d079dfcbb22132047ea2688a555]) Online check fix to work locally as a test. includes sample version (2.0.5) to force situation. [#314] https://github.com/exponentcms/exponent-cms/commit/57ef0ba6e8830d07...

• 

  dleffler January 6th, 2012 @ 02:42 AM

  Do we need to add a setting to site config to set the 'version check url'?

• 

  dleffler January 25th, 2012 @ 02:03 AM

  • State changed from “open” to “resolved”

  This has already been added