Forum Replies Created
-
Posts
-
What is the version number and date for you installation?
Also, show the complete error from the error log. It will state with a display of the SQL statement that was being executed followed by the debug backtrace of the call stack,
Don’t ask me why, but there are several places where you need to change the language. The setting in custom.config.php controls the default locale that affects formatting of currency and other data fields.
You also need to change the language in the Settings -> SI Defaults which will change the language for most everything else.
Then there are language settings in the Settings -> Inv Pregs for each invoice type, etc.
When the changes are made, you should have the language changed across the board. If then you see values not translated, it is likely that that info in the lang/nl_NL/lang.php file has not been translated or is missing. If you fix this, it would be helpful if you could send me the updated file to put in the library.
Note that the way the lang files work, is that if wording is in the specified lang file, it is used. If not, the wording in the default lang file (lang/en_US/lang.php) is used.
For example, the $LANG[‘save_inventory_failure’] text exists in the lang/nl_NL/lang.php file but has not been translated. But the $LANG[‘help_company_logo’] text only exists in the lang/en_US/lang.php file, so it is used.
To fix this, you would simple translate the $LANG[‘save_inventory_failure’] text in the lang/nl_NL/lang.php file but need to copy the $LANG[‘help_company_logo’] message to the lang/nl_NL/lang.php file and then translate it. Doing this and providing me with the updated file, I can include it in the library so your changes are lost in future updates and will benefit others that want to use this file.
Note that the info in the lang.php file is alphabetized by the $LANG index value (which must remain as english for the code to work).
I’m not sure what your problem is. I assume you are NOT using the free hosting service on byethost as it has limitations on email.
Although difficult to find, I did locate the email setup instructions for premium host user on byethost. It is consistent with what you have. However, the same documentation only shows PHP versions up to 5.6x. You are definitely on 7.2x. So it is possible that the knowledge base doc is out of date and there is another email setup option that you can use; possibly using TLS.
I suggest you talk with your web host support team. They might be able to look at their logs and see why your connection is timing out.
Other than that, I’m at a loss as to why you are having an issue.
Have you verified the email settings in your config/custom.config.php file? Below is an example of what needs to be set. Your settings will likely vary and should be provided by your email provider.
email.host = <myemailhostname>
email.smtp_auth = true
email.username = <myusername>
email.password = ‘<mypassword>‘
email.smtpport = 26
email.secure = TLS
email.ack = false
email.use_local_sendmail = falseSounds to me like your attempt to send the email timed out. Make sure the email information in the custom.config.php file is correctly filled out. Make sure the vendor directory is current with what is in github for the project. You can also use the command window to run “composer update” from the SI directory.
Also, in the custom.config.php file, you can set the zend.logger_level to DEBUG and create a logging trail in the tmp/log/si.log file.
Need more info about what the “grey screen” is. Is this after selecting the email option for an invoice? Or after submitting the email for mailing? Is any error shown in the error log? What does the browser address line show?
Found error that prevented new table from being created. Restore your DB to what it was prior to loading this update, download new version of SI from github and run update process again. Let me know how this works for you.
Make sure you change the local.locale setting in the custom.config.php from en_US to your locale (ex: en_GB). This should make your currency symbol show correctly.
I suspect it is an issue that evolved for the dataset settings over time. Can’t see what table structure was originally but at some point field altered to be INT(11) and nullable. Recommend that you check the table structure to verify that it allows NULL and then change all 0 values to NULL.
The new master_2019.2.1_beta which implements foreign keys will eliminate this problem by tying the tax id fields to the id field in the si_tax table.
The essential data prompt occurs when a database exists and can be accessed but there is no data in the si_sql_patchmanager table. Check what you are importing and make sure the database tables are populated with data.
I recommend dropping all tables and then importing your backup.
You need to set up a custom invoice template. Refer to the “Invoice Templates & Styles” section on the menu to the left. Note that the menu link, “System Preferences,” has been renamed to “SI Defaults” to allow room for new menu options. I’ll update the web page to reflect this shortly.
Yes, having the create table statements is what the problem is. I thought that I had specified that you should not include the structure but in reviewing step 2 of the instructions, I didn’t spell this out. Sorry about that. The instructions and database structure I provided are for the master_2019.2.1_beta version and at this point, I would not use them per the following info.
At this point if you are up on master_2019 (version 2019.1.1) and want to get to the most current master_2019.2.1_beta version (version 2019.2.4), load the updated SI software and run it. In theory, it should update the database and run smoothly, especially with fixes I implemented per your previous load attempts.
Recent Comments