[RRowley]

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.

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

Attachments:

1. si_fix1.zip

[RRowley]

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.

[RRowley]

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.

[RRowley]

Any reason you can’t update to the master_2020 version? Check out the “Version Update Process” topic on the left side menu.

[RRowley]

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.

[RRowley]

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.

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

[RRowley]

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.

[RRowley]

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.

[RRowley]

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.

[RRowley]

As a matter of fact, I used this scenario to help document how to make an extension. I’ve attached a zip file that contains the files for the module.

Download the zip file and extract it into extensions directory. Next go to the Settings tab and select the Customize menu option. On the Customize screen, select the Extensions option. You should see the cronInvoiceTotal extension. Select the leaf on the left to register the module. Then select the light switch on the left to enable the module. Now if you access the Recurrence screen, the invoice total should be present.

Let me know how this works.

Attachments:

1. cronInvoiceTotal.zip

[RRowley]

No, there isn’t. Making an API would likely be the best approach.

[RRowley]

You would need to create an extension, probably best for the module/cron/manage.php and the templates/default/cron/manage.tpl. In the php file, take the table retrieved from the Cron::manageTable(), loop through it making a new table. For each record you would use the invoice number to get the invoice record, take the total from it and add it to the manageTable() row, creating a new array of records to then store in the DataTable. Now you would have the value to display on the screen by adding it the the table heading and DataTable info in tpl file.

You do this as an extension so the code can be preserved when new SI updates are loaded.

[RRowley]

If you were on master_2019.2 and had data in your database, loading master_2020 should not show these messages. Rather it would show you messages concerning the application of patches to the database.

Use phpMyAdmin (or other tool you use to access databases directly) and verify the you have data in your database. It sounds as though you don’t.

Note that the instructions given un Version Update Process say to backup up the database but not to erase it. Then the si2020Converter.php program simply converts your old custom.config.php file into the new custom.config.ini file used by the update. Verify that all the information for your database base that is now in the custom.config.ini file is correct (the same as it is in the custom.config.php except the field name on the left will have been updated.

If your database content was somehow lost, you can DROP all the tables and import the SQL file backup of your database you made in step 2 of the update instructions.

Now you can access the database and you should see a screen that says there are patches that need to be applied. And you go forward from there.

[RRowley]

Got a quick response on this issue. Turns out that floating tables is not supported in the MPDF library. That means the template has to be rewritten to merge the right float ant the left positioned tables as a single table. I’ll work on that and let you know when I have a solution.

[RRowley]

This appears to be a bug in the MPDF library used to generate the PDF from HTML code. I’ve documented and reported it to the site that maintains this code. Hopefully they can find and fix it quickly but until then, I have no solution.

[Author]

Posts