[RRowley]

What errors are showing in your tmp/log/php.log file? If there are a bunch of old ones, delete the content of the file and run your inquiry again so only current errors are in the file. You can zip the file and attach to a response for me to review. Concerning a zoom, that is possible. Let’s try reviewing current errors first and if nothing there, do the zoom thing. As far as cost, I would leave that to you and ask that you post it via the GoFundMe link on the group page.

[RRowley]

Obviously the deleted items won’t appear in the si_invoice_item_tax any longer. So I’m wondering that items you are thinking of deleting from this table. I did run a test where I created an invoice with a tax item, then manually deleted it from the si_invoice_item_tax table. Although the si_invoices record still contained the total tax value in the record, when I displayed the invoice, it no longer showed the total tax. And when I went back to the database, the si_invoices tax_amount field was reset to zero (the correct value). So you should be able to reset the values by simply accessing the invoices.

By the way, how is your original issue? Everything displaying OK?

[RRowley]

You had me there for a second. You meant the Default Invoice Type which is a folder containing the template for the invoice that you want to use. I selected measurements and then did a print invoice on an existing invoice. The result was fine. I’ve attached a copy of what I got using this. Don’t mind the blanked out fields, the data was correct in them but the info more or less confidential.

Attachments:

1. 

   measurementInvoice.jpg
   

[RRowley]

The NumberFormatter class is part of the Intl extension. You need to uncomment this extension in the php.ini file and then restart your Apache server.

[RRowley]

Your issue will be setup related. For your setup, I suggest using port 26 for TLS. That is what I am using on my live system. If that doesn’t work, check your email provider to see what they recommend for TLS settings on SMTP server.

[RRowley]

The invoice number and date are set the same as if you generated a new invoice manually. The invoice is the next available and the data is the current system date.

[RRowley]

You are making progress. From what I find by googling his error, is that you exceeded the maximum number of SQL queries that are allowed within and hour. There are various solutions but before you try any of them, just try SI again and see if it completes; since an hour has passed since you got the error. If that doesn’t help, google the error and see the various solutions that those who have encountered this error have tried. This is what I googled:
User 'marvel_smp' has exceeded the 'max_questions' resource (current value: 150000)

[RRowley]

Turns out there are two duplicate entries in the cron log file. If you delete these, SI should run past this point. In the si_cron_log table, delete the records with id of 223 and 231.

[RRowley]

Not sure why you are getting this error, but have attached files to see if you can get past it using a database I generated from a fresh install. This database should be at the point where you will need to enter customer, biller and product. Then you can add invoices. Just delete all tables from your existing database, the upload the SQL file contained in the attached zip file. Let me know if this helps.

Attachments:

1. simple_invoices.zip

[RRowley]

Export the si_sql_patchmanager table structure and data. Zip the file and attach to your response. This table contains no secure information. It’s content is basically the same on all SI implementations and indicates what patches have been applied. Also, extract the si_cron_log table structure and include in the zip file. I just need to review its structure to confirm what the log is telling me. I think you already have patch 289 applied but there is not patch record for it. And you will just need to make the dummy patch record for it. But I need to review this information to confirm this.

[RRowley]

If SI allowed you to select install database, then any errors would be in the tmp/log/php.log file. If that file is empty, then you should be able to collect data in the tmp/log/si.log file. Make sure you enabled DEBUG level logging. This is found in the custom_confi.ini file. You don’t need to start from scratch. Just enable logging, delete the old log file if it exists. Then run SI for the install. Then zip to si.log file and attach to a new message. That should help me figure out what is going on.

[RRowley]

Not sure what you are starting with at this point. Are you running 2019.2 to upgrade your existing database, or are you working from a empty database, no data, no tables? If running 2019.2 to upgrade existing database, did you set zend.logger_level = DEBUG in the custom_config.php file? If using 2023 version, you would set, loggerLevel = DEBUG in the custom_config.ini file.

The delete the current tmp/log/si.log file. Also, delete the tmp/log/php.log file. Now run your test. After the test, zip both log files and provide them at attachments.

[RRowley]

So if you select the option to start using SI, it simply returns to this screen?

What is the greatest value for the sql_patch_ref number in the si_sql_patchmanager table? If essential data is installed, you should be able to select the start using option and SI will prompt you to enter biller, customer and product.

[RRowley]

In custom_config.php, use the following setting.

zend.logger_level = DEBUG

This will record the entire process in the tmp/log/si.log file. Run your process and see if this file contains meaningful info. That is if it shows what steps the process has gone through and where it stopped. You can zip this file and attach it to your next post. Check the tmp/log/php.log file. If it contains info, zip and attach it also. If it doesn’t have info in it, check where you default PHP log file is being stored. This is set in the PHP configuration file. That should be where PHP logs errors up to the point where the config init step is completed and SI sends errors to the tmp/log/php.log file.

[RRowley]

OK. I created a test on my development desktop. I have xampp installed with php version 8.2.12. This was set up with enabling of GD and INTL extensions. I downloaded the simpleinvoices-master_2023 version and extracted it into my xampp htdocs folder. For ease, I created a virtual host equating the simpleinvoices-master_2023 folder to master2023. I accessed master2023 from my browser and got the no database set up error. I then created an empty database. I already had a db user with full access, so I didn’t need to add this. I added the DB user, password and db name to my custom_config.ini file. I accessed the page from the browser again and got the create database screen. I accepted this and next got the essential data screen. I then chose to not install sample data and got the screen to create a biller, customer and product. I did this and was then able to create an invoice. This tells me that your issue is not with the clean install.

Can you tell me more about your directory structure; that your SI is installed underneath your document root directory, etc. The issues of not finding the non-abstract method error seems like a search path issue that your server is running into. Also, because SI is failing on the Config:init() method, the path for the application log file has not been established. This means the default log file is used. For my install, this is the C:\xampp\php\logs\php_error_log file. You should use phpinfo to determine what your default path is.

If you modify the $secure setting in the phpinfo.php file found in the root SI directory to be set to false, and then access this file from your browser, it will display all your php configuration info including the error log file path.

[Author]

Posts