Forum Replies Created
-
Posts
-
Recurrence by definition is the creation of a duplicate of a specified invoice. Since my recurring invoices are not always complete duplicates (may have additional charges, etc.). My approach is to set recurrence for the invoice that most closely resembles what I want. I turn OFF the option to email it to the customer but turn on the option to email it to the biller (aka, me). When the new invoice is generated, I can view it in my email to see if it is what I want. If not, I modify the new invoice and then send it to the client. If it is what I want, I typically forward it from my email scrubbing all indications it is being forwarded.
If you update the new invoice to be what you want and wish to have that be your future recurrence, you can edit the existing recurrence record and have it reference the new invoice. You do not need to update start date unless you want the day of recurrence to be other than an anniversary of that date. Logic exists to prevent a recurrence from being processed multiple times. So if your start date is 2022-04-16 and your recur period is 1 year, the next recurrence will be on 2023-04-16.
The current version is 2020.3.17. You can download the zip file for it from GitHub @ fearless359/simpleinvoices. The default version of master_2020 is what you want. Here is the path: https://github.com/fearless359/simpleinvoices
The setting to defer rendering of other than the first page is set. This allows first page to display one rendered, deferring the rendering of the remaining page until requested to computer overhead allows. Not sure how to improve on this short of changing the logic to only display x-months worth of data on initial load with an option like a flag up top to load remaining data. If people keep having trouble like this, that might be a solution to be pursued.
What version of SI are you on? Check the About link on the top menu line. Also, what version of PHP are you on? Verify that you are on a version of 7.4x.
Great news. The issue evolved around the last update required for master_2020 being 319 and that being the last update you had. Why this hasn’t happened before, I don’t know. But I’ll post the fix and it shouldn’t happen to others. Thanks for helping work this out.
I’ve attached a zip file with an update index.php file in it. Use this in place of the one you have in your root SI directory. Reset your database to what it was before the upgrade and run SI to see if this doesn’t resolved the issue. Let me know what happens, good or bad.
In your database, what is the greatest value of the sql_patch_ref field in the si_sql_patchmanager dataset. If the dataset is not empty, the greatest value should be 319. This is the greatest patch number applied in master_2019.2 and master_2020 begins it patch settings from there, starting at 320. If this dataset is empty, you are doing a fresh install an the essential data adds patches 319 through 326 (or greater when future patches added) to the dataset.
Things to also check:
1) In config/custom.config.ini, make sure the database settings are correct. I suspect they are because the code is acting as though it can access the database.
2) Check the tmp/log/php.log file and see if there is an error being reported. If you are unsure of the error info being from your last test, delete the content and save the empty file. Then access SI again to recheck the content of this file.
3) Delete the tmp/log/si.log file if there is one. Then in the config/custom.config.ini file set the loggerLevel to DEBUG. Run your access again and see what gets logged.
You can zip either the php.log or si.log file to this forum if you want me to look at them. Although, you should sanitize the confidential data in either file. There probably isn’t any in the php.log, but you will see database names and passwords and possibly email names and passwords in the sl.log file. Just replace these with x’s as nobody but you needs to see them.
Check the version of SI you are on. If master_2020, the config/custom.config.php is no longer used. The config/custom.config.ini is used and that is where you should make changes. If not on master_2020, you should update to it before reporting an issue.
Any reason you can’t update to the master_2020 version? Check out the “Version Update Process” topic on the left side menu.
I’m assuming that you have two tax boxes appear on the new/edit invoices screen and that you have a tax such as GST selected when you save it.
Also that you are running the most current version of SI master 2020 loaded. You should see “Version: 2020.3.13 — 20211104” in the About box. I ask specifically about this as I fixed this issue (not sure how long ago) where this was happening. So make sure your version is current.
Their are several settings that need to correspond. The Currency Sign recognizing that other than a $ sign needs to the html code for the currency. Then you have the Currency Code which for dollar is USD, England is GBP, euro is EUR, etc. Then you have the Locale which is en_US for the US, en_GB for Great Britain, etc.
Then you have the “locale” settings in the config/custom.config.ini file.
I’m assuming you are referring to the printed invoice and not the invoice maintenance screens. You can modify the printed invoice template but not the maintenance screens. If this is the printed invoice, which template are you using? You can find this in the SI Defaults settings.
Is there anything in the php.log file? Also, if you set the “loggerLevel” in the the config/custom_config.ini file to DEBUG and run the pdf generation again. Look in the si.log file (same directory as the php.log file). Search for ‘Pdf::generate() – pdfname’ and scroll down from there. You should see the actual pdf file generated as an html page. Scroll further down to the end of the html output and see where the PDF generation goes from there. You can zip the pdf part of the si.log file and attach it to a response to this message.
NOTE, be careful that you alter any passwords and personal information in this file before you copy to attach it here. The log contains security information and it is your responsibility to obscure it.
I tried rewriting the default template to not use floats. The logic got significantly convoluted when dealing with optional fields like various phone numbers and custom fields. If you can eliminate the fields you really don’t use so the logic doesn’t have to test if the field is empty and such, then the logic should be more straight forward. Other than that, I don’t have a lot of suggestions. I did got back to the SI 2011 and 2013 libraries and I’m not sure they supported floating tables in PDF. I might try to install an old version just to test and see.
Recent Comments