[RRowley]

Change 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.

• This reply was modified 3 years, 11 months ago by RRowley.

[RRowley]

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.

• This reply was modified 3 years, 11 months ago by RRowley.

Attachments:

1. config.zip

[RRowley]

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.

[RRowley]

Please zip and attach your tmp/log/php.log file in a response to this message.

[RRowley]

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.

[RRowley]

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.

[RRowley]

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.

[RRowley]

Sounds like you have a definition of “fun” similar to mine. Good luck.

[RRowley]

Find the invoice in the si_invoices table and set the owing field to 799. That should correct this.

[RRowley]

I forgot to a a COMMIT; line at the end of the sql file. So I’ve attached an update version with this message.

Attachments:

1. foreignKeyConstraints-1.zip

[RRowley]

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         2

Basically 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.

Attachments:

1. foreignKeyConstraints.zip

[RRowley]

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.

[RRowley]

The file you included was named incorrectly. It should be custom.config.php rather than config.custom.php.

Once I corrected this, it converted correctly. I’ve attached the converted ini file in case you just want to use it.

Attachments:

1. custom.config.ini_.zip

[RRowley]

In the primary SI directory, there is a phpinfo.php file. Change the $secure = true; setting to false. Then run this by entering the same thing you do to run SI but add /phpinfo.php to the end of the line. For example:
https://localhost/simpleinvoices/phpinfo.php
This will list the settings in your php.ini file. At least then you will know what settings you have.

Be sure the change $secure = false setting back to true. This will prevent someone else from running this file on your site.

[RRowley]

Please make a copy of your custom.config.php file with any personal info (passwords, etc) changed to innocuous values. Then zip this file and attach it to this thread. I’m not sure why you got the error you did but want to test it myself.

[Author]

Posts