Forum Replies Created
-
Posts
-
I am at a loss as to why you would have an issue with a library file function that is used pervasively throughout this application. At this point, I would recommend you try reinstalling the SI application. First, following the Version Update Process on the left menu. This makes sure that everything is reinstalled. If that does not work, you might try installing a clean version of SI. This is in the Installation link on the left. Do this letting that application install the new database – you set up an empty database and SI loads the structure and required files. If this works and you can run the application, the issue likely lies in a difference in your database and its data structures. If this is the case, you should export a copy of your existing database structure, no data just structure, and the structure of the newly installed database that is working. I’ve had to do this in the past for other reasons and found that over time and updates, database field definitions have been changed but not reflected in my database. This shouldn’t happen, but it did. So the resolution was to manually alter the real database to match the structure of the test database. Once this is done, point the SI application to your live database and see if the issue is resolved.
What version of PHP are you using? This is a library error and not typically something that I can fix. You might make sure that you are using symphony libraries consistent with your PHP version.
For some reason, the PDO class in PHP is not being recognized. I have attached the following link to documentation that might help you determine what you need to do in your set up.
Use the class field to assign a user defined class. The in the style.css file add that class with the style adjustments you want.
You are inheriting CSS settings from the standard CSS file (css\main.css). Use the css file in the same directory as your template to override default settings. Basically, you’ll need to change the TH settings; which are generated by the print_if_not_null function. You should be able to control font size in the same manner.
This is likely due to the changes to use globalization for date, number, etc. formats. You need to make your own version of the template is you aren’t already. See the “Invoice Templates & Styles” topic on the left. Once you have your own template version, edit the template.tpl file to use the international date with the format of long. Here is an example of what this would look like:
field={$invoice.date_original|utilIntlDate:$invoice.locale:"long"}Is there a reason you can’t update to php 8.1 or greater thereby being able to load the current version of SI?
The issue is that the si_invoice_item_tax file has a foreign key set on the ID field of the si_invoice_items table. You need to make note of the foreign key settings and then delete the foreign key. Next add the auto increment to si_invoice_items ID field. Finally, add the foreign key back on the si_invoice_item_tax table.
The error appears to complain that there is an attempt to add and si_invoice_items record with a duplicate value of 0 for its primary key. The primary key is (should be) the ID field. This field could only be assigned 0 if it does not have the auto increment setting on. User phpMyAdmin to verify this. There are two issues to correct. One is that there is now a record in that table with a 0 value for its ID field. That is a problem. I suggest you find which invoice this is for and delete it. If you don’t find a record with a 0 ID value, it was probably created for the invoice you are adding, say for the first invoice item and then it got an error on the second. Once you’ve cleared up the 0 ID issue, you can set the auto increment setting on the table. This can be done in phpMyAdmin. If you had to delete and invoice, add it back now. Make note of the original invoice number to reference it to the new number assigned to it for your records. Once you’ve taken care of any deleted invoice, you can add the invoice you were trying to add when this error occurred. All should be OK at this point.
Concerning unable to apply foreign key changes error, the exception message tells you what the issue is. From your error log:
The records in the FOREIGN KEY TABLE are most likely invalid and should be deleted. FOREIGN KEY TABLE COLUMN REFERENCE TABLE COLUMN INVALID VALUE ———————— —————— ———————– ——— ————- invoice_item_tax invoice_item_id invoice_items id 10 invoice_item_tax invoice_item_id invoice_items id 11 invoice_item_tax invoice_item_id invoice_items id 12 invoice_item_tax invoice_item_id invoice_items id 13
This is saying that there are si_invoice_item_tax table records with an id of 10, 11, 12 and 13, containing invoice_item_id values that do not exist in the si_invoice_items table.
There are two ways to resolve this. One is to create si_invoice_itens records that contain these values. The other is to delete these records from the si_invoice_item_tax table. Since the orphaned records are likely left over from the deletion of si_invoice_items records that failed to delete associated tax records, the solution to delete the si_invoice_item_tax records with id values of 10, 11, 12 and 13 is likely the best solution.
Recent Comments