Forum Replies Created
-
Posts
-
Refer to the Extensions topic on left menu. This should explain how to make changes to your local copy of code in such a way that future updates don’t load over them.
The field validation routine obviously doesn’t allow you to type in a negative value. You can create a product for the credit with a negative amount. This will set the field to the negative value when you select that product. This works for fixed value credits but not so much for credits that are arbitrary, set based on the particular situation.
For example, I have a product, “Labor”, that is $30.00 per hour and one for “Labor (Credit)” for -$30.00 per hour. This works for me because my labor cost is fixed and hence a credit is similarly fixed.
Let me know if this work around addresses your need not just for this circumstance but on going for future situations.
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.
Recent Comments