Issue: Allow In-Place Upgrades

Issue Tools
- View Changes

September 9, 2013 3:22 PM

pegasus

VaultWiki Team

Allow In-Place Upgrades

Currently VaultWiki must be manually disabled via the platform's admin area before any upgrade steps are taken (especially uploading new files), or database or other fatal errors might occur.

Implement a system where VaultWiki automatically disables itself if it detects the file version doesn't match the installed version. This way, forgetting to disable VaultWiki before an upgrade won't result in the site crashing.

Issue Details

Issue Number 3323

Issue Type Feature

Project VaultWiki 4.x Series

Category Install / Upgrade

Status Implemented

Priority 2 - Fatal / Database Errors

Suggested Version 4.0.0 Beta 5

Implemented Version 4.0.0 Beta 6

Milestone VaultWiki 4 Beta X

Software DependencyAny

License TypePaid

Votes for this feature 0

Votes against this feature 0

Attachments 0

Assigned Users (none)

Tags (none)

September 10, 2013 1:46 PM

pegasus

VaultWiki Team

Implemented for the next release. Once the new files are uploaded, VaultWiki will consider itself as disabled and will prevent plugins from running, access to the wiki, and access to the admin panel. The only access is to the install/upgrade script.

Reply

+ Reply

All times are GMT -4. The time now is 10:53 AM.

This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.

Learn more… Accept Remind me later

Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

Issue: Allow In-Place Upgrades

Issue Tools