
Bug: Upgrade scripts should run when versions are equal?
Reported by dleffler | February 29th, 2012 @ 09:42 PM | in 2.0.6 (closed)
If you are running develop code, later updates won't be applied when the final version is released. We should run upgrade scripts when the current version iteration is newer than the database (moving from develop to stable to patch, etc...
Comments and changes to this ticket
-
dleffler March 3rd, 2012 @ 01:51 PM
- State changed from open to resolved
This has been fixed by ensuring the $to_version is set to the version 'up to'...if the feature/issue is fixed in v2.0.6, the $to_version MUST be set to 2.0.6 to ensure the fix is applied to all variations.
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.