Forum Replies Created
The “to” field is set to the customer and/or the biller email depending on the option to send to either one or both in the recurrence record.
The error for the tax_id field is a bug in the code. I’ve attached new Email.zip file that contains updated Email.php and Invoice.php files. The first removes the debug statements I added in the previous change, but the Invoice.php contains a fix for the tax_id issue. Extract both of these to the Inc/Claz directory.
At this point, I’m not able to test that changes, so I ask that you do and let me know the result so I can hopefully at them to the next version of 2019.2
- This reply was modified 1 day, 23 hours ago by RRowley.
The email body is automatically set by the code. I don’t think that is the problem. However, I don’t know which field is empty. I’ve made a modified version of the Email.php file that will put info in the tmp/log/php.log (aka error log) file indicating which email field is empty.
Extract the Email.php file from the zip file and save it in your Inc/Claz folder over the version that is there. If you run cron, you can see what it puts in the error log and let me know.
Attachments:January 11, 2021 at 7:43 am in reply to: How to keep/save bill type as Invoice and qoute seperately #1308
See instructions in image file.
You need to make a custom template. The instructions I mentioned tell you how to initially set this up. You can copy the default directory to a new directory named for example, “mypdf”, and then modify line 35 of the template.tpl file and change
PDF’s are an exception to the rule. They contain their own code to display values and any changes you want to make require you to implement a customized version. Check out the directions for the Invoice Templates & Styles menu link to the left.
Check the tmp/log/php.log file for error detail. You likely have orphaned records that prevent foreign keys from being added. The error information will tell you what they are as well as provide an example of how to correct them. If zip the error log file and attach it here, I can look at it an advise what to do. Make sure there is not secret info in the error log before attaching it.
I’ve standardized the date format displayed on screens to the database format, yyyy-mm-dd. The value on the invoice, expense and payment view screens had been missed. The most recent update, Version: 2020.0.11, corrects this.
If you want a difference format for the printed invoice, you’ll need to develop a custom template.
Thanks. Fixes for this issue have been uploaded on github. Update to that version to get them plus other changes for datatables library security issue fix.
Please try the following:
In the templates/default/customers/create.tpl file, find the “SELECT” statement for the “parent_customer_id” field. Approximately line 125. Modify the line following the “SELECT” statement remove the value setting of blank, so it looks like this:
If that works for you, I’ll make it a permanent fix.
What version of SI are you on (check the About info on the banner line)?
Thank for finding the issue. I’ve fixed it for the next update I provide.
Check the setting in system_defaults for the record with name “delete”. It must have a value of 0 or 1.December 1, 2020 at 7:15 am in reply to: SqlPatchManager::runSqlPatch() error. See error log for more information. #1252
OK, better thought. What is the content of your si_index table? Typically, it will contain 1 record as follows:
The key here are the sub_node and sub_node_2 values. I suspect one of them, probably sub_node_2, is equal to blank and needs to be numeric.December 1, 2020 at 6:52 am in reply to: SqlPatchManager::runSqlPatch() error. See error log for more information. #1250
Make sure you have all the Requirements specified to the right set.
- This reply was modified 1 month, 2 weeks ago by RRowley.
You should always disable check foreign key constraints when importing or deleting database content. This only removed the test for the import or delete process. Once data is imported, the constraints are enforced.