-
Type: Bug Report
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 5.1.3
-
Fix Version/s: 5.2.0-B1
-
Component/s: Install / Upgrages
-
Labels:None
-
External issue URL:
-
Change Log Message:Fixed sql error during installation
-
External issue ID:1144
-
Copy Issue Key:
-
Patch Instructions:
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.
- mentioned in
-
Wiki Page Loading...