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 ] [ Horizontal ]

Viewing Issue Simple Details
ID	Category	Type	Reproducibility	Date Submitted	Last Update
0001144	[In-Portal CMS] Install / Upgrages	bug report	always	2011-10-17 07:49	2012-07-25 05:32

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

Summary	0001144: Checking Affiliate during installation cause sql error
Description	I've noticed, that since 5.1.3 version we've got 1 more error during installation: SELECT Affiliates.* ,(u.PortalUserId) AS `UserId`,(IF( LENGTH(u.Login), u.Login, '')) AS `UserName`,(ap.Name) AS `PlanName`,(Affiliates.LastPaymentDate) AS `LastPaymentDate_date`,(Affiliates.LastPaymentDate) AS `LastPaymentDate_time`,(Affiliates.LastOrderDate) AS `LastOrderDate_date`,(Affiliates.LastOrderDate) AS `LastOrderDate_time`,(Affiliates.CreatedOn) AS `CreatedOn_date`,(Affiliates.CreatedOn) AS `CreatedOn_time` FROM Affiliates LEFT JOIN PortalUser u ON Affiliates.PortalUserId = u.PortalUserId LEFT JOIN AffiliatePlans ap ON Affiliates.AffiliatePlanId = ap.AffiliatePlanId WHERE (`Affiliates`.PortalUserId = '-1') LIMIT 0,1 happening from OrdersEventHandler->isAffiliate method on "Modules to Install" step. This is because installation wizard now uses the same method for logging user in as Front-End code. That's why I propose to skip affiliate checks during installation.
Additional Information