Skip to content

Latest commit

 

History

History
94 lines (69 loc) · 5.51 KB

UPGRADING.md

File metadata and controls

94 lines (69 loc) · 5.51 KB
Raw

Update using the web-based updater

Site administrators of an installation will see a Update-Box at the right side of the administration page of a consultation. The box indicates if an update is available. If so, you can switch the whole installation into Update mode. While the update mode is active, the whole site will not be available to other users.

Once the update mode is active, the /update.php script will be available to the site administrator. Here, the update can be performed in two to three steps:

  • Download the update file
  • Install the new files
  • Apply database updates (this is usually only necessary when upgrading to a new minor version, e.g. from 3.9 to 3.10.)

Before using the updater, it is generally a good idea to back up all files and especially the database.

If you encounter any problem using the web-based updater, please consult the Update Troubleshooting FAQ.

Updating a existing installation using the pre-bundled package

  • Download the latest package of Antragsgrün
  • Extract the files to your web folder, overwriting all existing files. The configuration (in config/config.json) will not be affected by this.
  • Remove the config/INSTALLING file

If you have shell access to the server

  • Execute ./yii migrate on the command line to apply database changes

If you don't have shell access to the server, e.g. using (S)FTP

If you don't have shell access to the server, installing major new versions (e.g. upgrading from 3.6 to 3.7) can be a tricky, as you will have to apply the database changes manually using phpMyAdmin or any other means of executing SQL commands.

Here is a list of SQL statements necessary to upgrade, starting with the upgrade from 3.6 to 3.7:

Upgrading from 3.8 to 4.0 (incomplete)

ALTER TABLE `consultationText` ADD `menuPosition` INT DEFAULT NULL AFTER `textId`;

Disable the addColumn line in m180609_095225_consultation_text_in_menu or mark the migration as done with ./yii migrate/mark m180609_095225_consultation_text_in_menu.

Upgrading from 3.7 to 3.8

ALTER TABLE `amendment` ADD `proposalStatus` TINYINT NULL DEFAULT NULL,
                        ADD `proposalReferenceId` INT NULL DEFAULT NULL,
                        ADD `proposalComment` TEXT NULL DEFAULT NULL,
                        ADD `votingStatus` TINYINT NULL DEFAULT NULL,
                        ADD `votingBlockId` INT NULL DEFAULT NULL,
                        ADD `proposalVisibleFrom` TIMESTAMP NULL DEFAULT NULL,
                        ADD `proposalNotification` TIMESTAMP NULL DEFAULT NULL,
                        ADD `proposalUserStatus` TINYINT NULL DEFAULT NULL,
                        ADD `proposalExplanation` TEXT NULL DEFAULT NULL,
                        ADD INDEX(`proposalReferenceId`),
                        ADD INDEX `ix_amendment_voting_block` (`votingBlockId`);

ALTER TABLE `motion` ADD `votingStatus` TINYINT NULL DEFAULT NULL AFTER `slug`,
                     ADD `votingBlockId` INT NULL DEFAULT NULL,
                     ADD `proposalStatus` TINYINT NULL DEFAULT NULL,
                     ADD `proposalReferenceId` INT NULL DEFAULT NULL,
                     ADD `proposalComment` TEXT NULL DEFAULT NULL,
                     ADD `proposalVisibleFrom` TIMESTAMP NULL DEFAULT NULL,
                     ADD `proposalNotification` TIMESTAMP NULL DEFAULT NULL,
                     ADD `proposalUserStatus` TINYINT NULL DEFAULT NULL,
                     ADD `proposalExplanation` TEXT NULL DEFAULT NULL,
                     ADD INDEX `motion_reference_am` (`proposalReferenceId`),
                     ADD INDEX `ix_motion_voting_block` (`votingBlockId`);

ALTER TABLE `consultationUserPrivilege` ADD `adminProposals` TINYINT NOT NULL DEFAULT '0' AFTER `adminScreen`;

CREATE TABLE `votingBlock` (
  `id` int(11) NOT NULL,
  `consultationId` int(11) NOT NULL,
  `title` varchar(150) NOT NULL,
  `votingStatus` tinyint(4) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
ALTER TABLE `votingBlock` ADD PRIMARY KEY (`id`);
ALTER TABLE `votingBlock` MODIFY `id` int(11) NOT NULL AUTO_INCREMENT;

ALTER TABLE `user` ADD `organizationIds` TEXT NOT NULL;

ALTER TABLE `votingBlock` ADD CONSTRAINT `fk_voting_block_consultation` FOREIGN KEY (`consultationId`) REFERENCES `consultation`(`id`) ON DELETE RESTRICT ON UPDATE RESTRICT;
ALTER TABLE `motion` ADD CONSTRAINT `fk_motion_voting_block` FOREIGN KEY (`votingBlockId`) REFERENCES `votingBlock`(`id`) ON DELETE RESTRICT ON UPDATE RESTRICT;
ALTER TABLE `motion` ADD CONSTRAINT `fk_motion_reference_am` FOREIGN KEY (`proposalReferenceId`) REFERENCES `motion`(`id`) ON DELETE RESTRICT ON UPDATE RESTRICT;
ALTER TABLE `amendment` ADD CONSTRAINT `fk_amendment_voting_block` FOREIGN KEY (`votingBlockId`) REFERENCES `votingBlock`(`id`) ON DELETE RESTRICT ON UPDATE RESTRICT;
ALTER TABLE `amendment` ADD CONSTRAINT `fk_amendment_reference_am` FOREIGN KEY (`proposalReferenceId`) REFERENCES `amendment`(`id`) ON DELETE RESTRICT ON UPDATE RESTRICT;

Upgrading from 3.6 to 3.7

ALTER TABLE `consultationMotionType` ADD `initiatorsCanMergeAmendments` TINYINT NOT NULL DEFAULT '0' AFTER `policySupportAmendments`;
DROP TABLE `consultationAdmin`;
ALTER TABLE `amendment` ADD `globalAlternative` TINYINT NOT NULL DEFAULT '0';
INSERT INTO `migration` (`version`, `apply_time`) VALUES ('m170226_134156_motionInitiatorsAmendmentMerging', 1489921851), ('m170419_182728_delete_consultation_admin', 1492626507), ('m170611_195343_global_alternatives', 1497211108);