Feature request - install/upgrade must be specifically envoked and upgrade requires admin login
Reported by dleffler | December 9th, 2011 @ 09:38 PM | in 2.0.4 (closed)
As a result of several discussions concerning ticket #417, the following is proposed for implementation:
- installer MUST be envoked by going to a specific url (install/index.php) just like we do now with logins.
- if there is no config or database connection, the site will appear to be down/in maintenance mode, but this is transitory and checked each page load (do NOT create the not_configured file)
- IF an upgrade condition exists, the admin user will will be notified (via flash message) that they should upgrade the site after logging in (page load) and given a link to launch the upgrade.
Drawbacks to this appraoch will be the 1) install/upgrade will no longer be semi-automated and 2) in some cases the site/page may crash if it is in an upgrade condition (system & database versions don't match) due to missing (new) database table fields
Comments and changes to this ticket
-
Richard Toohey December 12th, 2011 @ 07:52 AM
Thanks, guys, this sounds like a better approach.
Looking forward to 2.0.3.
-
dleffler December 13th, 2011 @ 06:20 PM
- Milestone changed from “2.0.3” to “2.0.4”
- State changed from “new” to “open”
- Milestone order changed from “28” to “0”
-
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...
-
dleffler December 24th, 2011 @ 04:48 AM
Now that the install/upgrade process in pre-release 2.0.4 must be explicitly called...
Do we need to create a routine to check if a user is logged on and an admin before we run the upgrade? -
dleffler January 6th, 2012 @ 02:41 AM
- State changed from “open” to “resolved”
-
dleffler February 2nd, 2012 @ 12:50 PM
- Tag changed from “installation, installer, upgrade” to “installer, upgrade”
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
People watching this ticket
dleffler
expNinja
Referenced by
-
417
If database down, Exponent 2.0.2 launches installer for upgrade
This has been moved to ticket #421
-
314
Feature request: Add update version checking (online)
Will be incorporated as a part of ticket #421, the
instal...
-
314
Feature request: Add update version checking (online)
(from [7a56c4d222a176d82bf3b507d4786ca3915b5dbe])
Better ...
-
314
Feature request: Add update version checking (online)
(from [12a81dda0896ddc865dbcc1dd732c214876954c3])
Revises...