RRowley

Forum Replies Created

Viewing 15 posts - 166 through 180 (of 307 total)
  • Author
    Posts
  • in reply to: Class ‘NumberFormatter’ #1230
    RRowley
    Participant

    Make sure the intl extension is enabled in the php.ini file. Find the following line and uncomment it.

    extension=intl

    Then restart your apache (or whatever) server.

    in reply to: Problems upgrading to 2020 #1228
    RRowley
    Participant

    Not sure what you mean? The implementation of foreign key support some time back should fulfill this request. What am I missing?

    in reply to: PDF generation urlsafe/htmlsafe #1224
    RRowley
    Participant

    Sorry that edit is difficult. Not an issue for me.

    Anyway, wanted you to try something. Delete the tmp/pdf_tmp directory. Then generate a pdf. Should recreate the directory and set up new font data. Let me know how it works.

    • This reply was modified 4 years ago by RRowley.
    in reply to: PDF generation urlsafe/htmlsafe #1214
    RRowley
    Participant

    Couple of questions:

    1) In the INV PREFS currency sign field, did you set the sign by entering this code: & # 163; (spaces suppressed)?
    2) Are you using the eg-invoice template from the zip file?

    I’ve done both these, set same values as you in custom.config.ini and set en_GB as Language and Locale fields in the INV PREFS. Using this both the default and the eg-invoice templates work correctly.

    • This reply was modified 4 years ago by RRowley.
    • This reply was modified 4 years ago by RRowley.
    in reply to: PDF generation urlsafe/htmlsafe #1209
    RRowley
    Participant

    The templates.zip file is empty. Also, access the Inv Pref Invoice records in edit mode and give me that screen shot.

    in reply to: PDF generation urlsafe/htmlsafe #1204
    RRowley
    Participant

    Can you zip and attach the template directory? Then I can test what you have. I need an image of your INV PREFS for Invoice record and the custom.config.ini settings for: localLocale, localCurrencyCode & localPrecision.

    in reply to: PDF generation urlsafe/htmlsafe #1194
    RRowley
    Participant

    In tpl files use urlSafe and htmlSafe with this letter case.

    in reply to: master_2020 Product custom fields = templates error #1191
    RRowley
    Participant

    Fixed in latest update.

    in reply to: Updating to 2020 – can not connect to database #1187
    RRowley
    Participant

    Looked into it further and find this list of special characters to avoid with the associated explanation:

    Note that these special characters are must NOT be used in the key and have special meaning in the value: ?{}|&~!()^”

    in reply to: Updating to 2020 – can not connect to database #1186
    RRowley
    Participant

    Never tried a curly brace special character. I use a # and it works fine.

    in reply to: master_2020 can not create biller #1185
    RRowley
    Participant

    Fixed in latest update.

    in reply to: Database error #1179
    RRowley
    Participant

    This is a multi-use table. The value field in the database is varchar(60). The PHP function that retrieves the data returns a type int value. 0 or 1 meet this qualification. Or at least that is for my development and my production systems. My development system is Win 10 using xampp. My production is a hosted LAMP web service. Both are at the 7.4x PHP version.

    There is no strict_type declaration in SI, therefore as long as the value being returned begins with a number (at least as I understand it), the number will be converted per the type declaration. So if the value in the database is 0 or 1, or even “0 ” or “1 “, it should be converted to the correct int and no type error thrown.

    Bottom line, I am not sure why you are having an issue.

    in reply to: Icons path wrong on recurrence page #1177
    RRowley
    Participant

    Just upload changes to fix path references for images. Please download and let me know if it works OK.

    in reply to: Database error #1173
    RRowley
    Participant

    The si_system_defaults record with the NAME of “delete” should have a value of 1 or 0. I recommend you manually set it to 0 (aka false) before running the update. Then you can set it via SI after the update if you want to enable the ability to delete invoices from the database.

    in reply to: Updating to 2020 – can not connect to database #1171
    RRowley
    Participant

    Check the Version Update Process link on the left. It has specific instructions for update from master_2019.2 to master_2020. Your problem is like that you did not run the si2020Converter.php program to convert your custom.config.php to custom.config.ini. This would account for not being able to connect to the database.

    Please keep me informed of your progress and anything that you find unclear or confusing with this upgrade.

Viewing 15 posts - 166 through 180 (of 307 total)