RRowley

Forum Replies Created

Viewing 15 posts - 286 through 300 (of 327 total)
  • Author
    Posts
  • in reply to: Debugging email #645
    RRowley
    Participant

    Oops. That should be $config->email->secure (not encryption).

    in reply to: Debugging email #644
    RRowley
    Participant

    The change to make is to use $config->email->encryption. I’ve been working with this set but haven’t finished testing. I’m still having some issues that I’m trying to track down.

    in reply to: Debugging email #640
    RRowley
    Participant

    The previous logic used Zend email logic. The version of Zend used by SI is no longer supported (Framework 1). So I have been trying to replace its functionality with other packages maintained via composer. Swiftmailer has good reviews and was easy to implement.

    in reply to: Error creating new invoice #639
    RRowley
    Participant

    The issue is that the value of the “id” field in the si_index table is not set correctly. It should be set to the value of the “index_id” of the last si_invoice record. The si_index table “id” plus 1 will be the value assigned to the next invoice.

    in reply to: Debugging email #636
    RRowley
    Participant

    I’ve been working with new ways to handle mail but have not had much success. All I can say for now is make sure your email parameters including the smtp_auth option are properly set.

    in reply to: Error creating new invoice #635
    RRowley
    Participant

    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,

    in reply to: Language #620
    RRowley
    Participant

    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).

    • This reply was modified 5 years, 4 months ago by fearless359.
    • This reply was modified 5 years, 4 months ago by fearless359.
    in reply to: Debugging email #619
    RRowley
    Participant

    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.

    in reply to: Debugging email #615
    RRowley
    Participant

    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 = false

    • This reply was modified 5 years, 4 months ago by RRowley.
    in reply to: Debugging email #613
    RRowley
    Participant

    Something I should have asked before, what version of PHP are you on?

    in reply to: Change currency symbol site wide #591
    RRowley
    Participant

    This was resolved in master_2019.2.1_beta.

    in reply to: Debugging email #590
    RRowley
    Participant

    Sounds 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.

    in reply to: Debugging email #586
    RRowley
    Participant

    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?

    in reply to: Debugging email #583
    RRowley
    Participant

    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.

    in reply to: Debugging email #581
    RRowley
    Participant

    Turns out to have been fixed in the master_2019.2.1_beta version. Maybe an incentive to update???

Viewing 15 posts - 286 through 300 (of 327 total)