Forum Replies Created
-
Posts
-
You have to load and successfully run the master_2019.2 update before you can load the master_2020 version. Please make sure that you process it in this order.
OK, lets just set the basics in the custom.config.ini file. Retype your lines to make sure there are no weird characters in them. Also, there is an updated Config.php file in the zip below. It checks for the false return that you are getting and shows a generic error rather stack dump.
[production] databaseAdapter = pdo_mysql databaseUtf8 = true databaseHost = yourhostsetting databaseUsername = yourdbusername databasePassword = "yourdbpassword" databaseDbname = yourdbname databasePort = 3306 authenticationEnabled = true authenticationHttp = exportSpreadsheet = xls exportWordProcessor = doc exportPdfDefaultFontSize = 12 exportPdfPaperSize = Letter exportPdfLeftMargin = 15 exportPdfRightMargin = 15 exportPdfTopMargin = 15 exportPdfBottomMargin = 15 versionName = 2020.0.12 versionUpdateDate = 20210128 localLocale = en_US localCurrencyCode = USD localPrecision = 2 emailHost = youremailsmtphost emailSmtpAuth = true emailUsername = youremailusername emailPassword = youremailpassword emailSmtpPort = yoursmtpport emailSecure = yoursecuresetting emailAck = youracksetting(true/false) emailUseLocalSendmail = youruserlocalsendmailsetting(true/false) encryptionDefaultKey = this_is_the_encryption_key_change_it nonceKey = this_should_be_random_and_secret_so_change_it nonceTimeLimit = 3600 debugLevel = All debugErrorReporting = E_ERROR phpSettingsDateTimezone = yourdatetimezonesetting phpSettingsDisplayStartupErrors = 1 phpSettingsDisplayErrors = 1 phpSettingsLogErrors = 1 phpSettingsErrorLog = tmp/log/php.log ; Logs in tmp/log/si.log. Set to the desired level for log detail. ; The lower the number, the more information will be logged. ; DEBUG(100),INFO(200),NOTICE(250),WARNING(300),ERROR(400),CRITICAL(500),ALERT(550),EMERGENCY(600) loggerLevel = DEBUG ; Explicitly confirm delete of line items from invoices? (yes/no) confirmDeleteLineItem = noChange line 45 and 46 of the Inc/Claz/Config.php file from:
$fooType = getType($config[$section]);
var_dump("gettype {$configFile}[{$section}]: {$fooType}");
to
$fooType = getType($config);
var_dump("gettype {$configFile}: {$fooType}");and run the test again.
Not sure what is happening. Your custom.config.ini parses correctly for me once I fill in valid database settings. So we need to troubleshoot to drill down to the problem. Attached is a zip file containing the Config.php file. Store this in your Inc/Claz folder over the existing version of the file. After doing this, do any action (display the login screen, etc.) and there will be information displayed at the top of the browser screen. Copy this information to a response to this this message. Show the info in a CODE section so nothing get misinterpreted.
Make a copy of your custom.config.ini file. Then obfuscate the passwords and personal info in the custom.config.ini file, and zip it. Attach the zip file to a response to this message.
The values I requested contain no secure or secret information. That is why I was so specific in what I asked for. You shouldn’t have any concern with sharing these on this forum.
While this inquiry is in process, copy the public/data.json file to zip and attach. Next, in phpMyAdmin, access the si_system_defauts table and export it to zip and attach. Then make a zip file with the data.json, exported si_system_detauls sql file and the templates/default/products/manage.tpl files. Attach the zip file to a response to this message.
Give me an export of the si_preferences file and the localLocale, localCurrencyCode and localPrecision settings from the custom.config.ini file. I’ll see if I can replicate your set up.
I forgot to a a
COMMIT;line at the end of the sql file. So I’ve attached an update version with this message.Sorry to tell you this, but you probably have a data base that does not have the proper foreign keys enabled. It will work, but you won’t be protected from orphaned records.
The 318 error you had is telling you that you have orphaned records in your database. This is what was in your log:
FOREIGN KEY TABLE COLUMN REFERENCE TABLE COLUMN INVALID VALUE ------------------------ ------------------ ----------------------- --------- ------------- user domain_id user_domain id 4 user domain_id user_domain id 3 user domain_id user_domain id 2Basically this is telling you that there are three records in the si_user table with the domain_id set to 2, 3 and 4 which do not have parent records for those domains in the si_user_domain table. The best solution is to create these records in the si_user_domain table and run the master_2019.2 installation again; assuming you can back up that far.
If you can load back to where you were prior to loading master_2020, this is what you should do. This way, the foreign key constraints implemented in patch 318 will succeed and every thing will be hunky dory.
Otherwise, you can make the fix above and import the sql file in the attach zip file which hopefully, will apply all the foreign key constraints to you master_2020 database.
Let me know how it turns out.
Typically you would have Set Aging enabled for your invoices. Otherwise, you won’t get any aging information in the Aging column. You might want to disable it on Quotes, Estimates, etc. because you aren’t looking for past due information on those invoices.
Were any errors reported to the tmp/log/php.log file? If so, I’d be interested in looking at that file. You would need to zip it in order to attach it.
I’d also be interested in knowing what happens if you set the Invoice INV PREFS record Set Aging field to Enabled.
Recent Comments