In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

Dependency Graph

[ View Issue ] [ Relation Graph ] [ Vertical ]

Viewing Issue Simple Details
ID	Category	Type	Reproducibility	Date Submitted	Last Update
0000779	[In-Portal CMS] Install / Upgrages	bug report	always	2010-06-15 12:02	2010-07-22 15:07

Reporter	alex	View Status	public
Assigned To	alex
Priority	normal	Resolution	fixed
Status	closed

Summary	0000779: Upgrade from 4.3.9 to 5.1.0-RC1 of In-Portal fails
Description	I have all modules (even paid) installed and I was trying to upgrade from 4.3.9 to 5.1.0-RC1. This all failed with large SQL error, that LanguageId column was missing in Phrase table, when upgrade script was trying to set index on it. That's how we are performing upgrade through 2 or more versions now (e.g. from 5.0.0 to 5.0.2): 1. run "before" php upgrade script for 5.0.1 version 2. run "before" php upgrade script for 5.0.2 version 3. run sqls from 5.0.1 to 5.0.2 version 4. run "after" php upgrade script for 5.0.1 version 5. run "after" php upgrade script for 5.0.2 version This process is repeated for each upgradeable module. I thought at first, that wrapping version upgrade scripts (php + sql) together will solve the problem: 1. run "before" php upgrade script for 5.0.1 version 2. run 5.0.1 version sqls 3. run "after" php upgrade script for 5.0.1 version 4. run "before" php upgrade script for 5.0.2 version 5. run 5.0.2 version sqls 6. run "after" php upgrade script for 5.0.2 version But this wasn't helping. Because when 1st module upgrade scripts will delete column, that is used by 2nd module upgrade script, then we also got sql error. And so another idea approached my mind: you all know, that don't have problems, when we upgrade for 1 version only (e.g. from 5.0.0 to 5.0.1 or from 5.0.1 to 5.0.2). I've created dependency list for each module, where I've listed what "Core" module version is required to perform successful upgrade to each of given module versions.
Additional Information	What's in the patch: 1. upgrade system failure, when large version range is used for upgrade 2. sql error on 5.0.3-B1 upgrade of In-Portal 3. empty "Cache Handler" configuration variable dropdown after upgrade to 5.1.0-RC1 4. skin upgrade system 5. incomplete orders were not deleted, when In-Commerce 5.0.1 upgrade was made

Web Development by Intechnic

In-Portal Open Source CMS